memory-capture

You can save your current work session for later recovery by triggering compact mode, which generates a structured markdown snapshot of your execution plan and state, then persists it directly to core memory for durable retrieval.

The best way to capture quick ideas is using tips mode, which logs fast notes with specific tags and optional context links, then imports the structured text into core memory to prevent losing critical progress.

Session compaction prevents losing work context by creating a faithful, restorable snapshot of your current execution state without summarizing the details, ensuring seamless continuation during future work.

Yes, you can use CLI-style flags like --tag and --context to trigger knowledge capture modes, allowing the system to detect your intended mode and execute the exact phase needed for structured persistence.

No, the memory capture process does not summarize your session notes in compact mode; it generates faithful structured markdown that preserves the detailed execution plan and actionable state exactly as needed for recovery.

You need structured notes for session recovery when you want to prevent forcing repeated re-exploration of previous progress, enabling a recovery-oriented workflow that produces a recovery ID for later search-style retrieval.