Files
memwalk/README.md
T
emilandClaude Opus 4.7 b873144b69 Initial v0.1: memwalk CLI on top of memba
- Config in ~/.memwalk/config.toml (typer init writes it)
- Sources: git log walker + bash history parser with secret/noise filters
- Ingest orchestrator feeds events into a memba Session and saves
  ~/.memwalk/current.memb via the rewritten Session.chat() that preserves
  loaded state (raw eval+sample, no KV-cache reset)
- Daily snapshot rotation under ~/.memwalk/snapshots/
- CLI commands: init, update, ask, standup, status, prune

Validated on Nemotron-3-Nano-4B Q4_K_M end-to-end: ingest 304 events
(303 commits + 1 shell session) in 2.8s on GPU, recall in fresh process
returns accurate per-project summaries.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-16 13:40:46 +03:00

2.0 KiB

memwalk

Walk through your work memory.

A local-first CLI that watches your git activity (and optionally your shell history) and feeds it into a Mamba-based LLM via persistent state. You can then ask in plain English what you were doing last week, why you started that branch, or generate a standup from yesterday's commits — without your data ever leaving the machine.

Built on memba for state persistence and NVIDIA Nemotron-3-Nano-4B (or any other GGUF SSM/hybrid model) for inference.

Status

v0.1 — alpha. Works end-to-end on Linux for the maintainer; APIs and on-disk format may change.

Install

# Until memba is on PyPI, install both editable from local clones:
pip install -e /path/to/Memba
pip install -e /path/to/memwalk

Make sure you have a GGUF Mamba-2 or hybrid model. Recommended:

hf download nvidia/NVIDIA-Nemotron-3-Nano-4B-GGUF \
    NVIDIA-Nemotron3-Nano-4B-Q4_K_M.gguf \
    --local-dir ~/.memwalk/models

Quickstart

memwalk init                                  # interactive setup
memwalk update                                # ingest last 30 days of git+bash
memwalk standup                               # auto-generate daily standup
memwalk ask "What was I working on last week?"
memwalk status

What it actually does

memwalk update walks your configured git repos and (optionally) your bash history, formats new events into a readable activity block, and feeds that into the SSM model. The model's hidden state — a fixed ~85 MB blob — is saved to ~/.memwalk/current.memb via memba.

memwalk ask and memwalk standup load that state and query it. The model recalls themes, projects, and trajectory across processes and reboots.

Layout

~/.memwalk/
├── config.toml
├── current.memb              ← rolling state
├── last_update.txt
└── snapshots/
    └── 2026-05-16.memb       ← daily snapshot before each update

License

MIT.