The memory dev namespace is meant to make the repository feel alive.
memory --db .memory.cpp/memory.db dev watch ./repo --workspace demo --onceThis wraps repo-friendly watch behavior and stores imported code/doc chunks as project memory.
dev watch respects .memoryignore and .gitignore, so secrets, build output, and bulky vendor folders can stay out of memory by default.
memory --db .memory.cpp/memory.db dev morning --workspace demoIt summarizes:
- yesterday's major changes
- recent decisions
- recent bugs and fixes
- open conflicts
- inbox items
- suggested next work
This is one of the best proof points for the product.
memory --db .memory.cpp/memory.db dev resume "MCP integration" --workspace demoIt reconstructs a recent workflow around the topic and produces a model-ready context block.
memory --db .memory.cpp/memory.db dev explain-repo . --workspace demoThis gives a compact onboarding summary:
- repo root
- top-level project shape
- recent decisions
- recent bugs and fixes
- recent git activity when available
memory --db .memory.cpp/memory.db dev next --workspace demoThis is the forward-looking companion to dev morning. It prioritizes:
- pending inbox review
- conflicts
- current task/decision threads
- bug/fix follow-up
- git refresh suggestions
doctor belongs next to the dev workflow because it answers the question: "is this environment launch-ready?"
memory --db .memory.cpp/memory.db doctor --workspace demoWhen you attach an agent through MCP, you can inspect local usage receipts:
memory --db .memory.cpp/memory.db audit-log --limit 20memory --db .memory.cpp/memory.db git summary --since 14d
memory --db .memory.cpp/memory.db git ingest --workspace demo --since 14d
memory --db .memory.cpp/memory.db extract . --workspace demo --dry-runThis makes the developer workflow feel less manual:
git summaryshows the recent project arcgit ingestturns commit history into memory candidates or direct stored memories when confidence is highextractturns docs, comments, and workflow notes into reviewable candidate memory