save-context

To save task context before clearing your work session, use a command that captures decisions, open questions, and modified files into a timestamped markdown file. This snapshots your current working state to disk for future reloading.

A context snapshot is a markdown file recording your task summary, git branch, and open questions. You need to capture context before long breaks, when the working context grows too large, or before executing a clear command to reload it later.

Session memory tracking records your current git branch and last commit into a markdown file alongside task summaries and open questions. This ensures your version control state is preserved and can be reused to resume work later.

Yes, you can reload a previous context snapshot to resume work with minimal setup. The saved markdown file in the contexts subdirectory contains all necessary decisions and modified files to restore your working state.

The best way to track decisions and open questions during long breaks is saving a context snapshot to disk. This generates a timestamped markdown file that preserves your task summary and modified files for easy retrieval when returning.

No, decision-tracking to save context requires no external dependencies. The process writes directly to an auto memory contexts subdirectory as a markdown file, capturing metadata like labels, dates, and git branches natively.