ck

To persist and reload project context between git coding sessions, register your repository with an init command and save session state. This stores summaries, next steps, and decisions into a versioned context.json file and regenerates a human-readable CONTEXT.md file for future reference.

Per-project session management is the process of saving one-sentence summaries, left-off points, and blockers into a versioned context.json. It automatically injects a compact briefing at session start, highlighting goals, recent git activity, and unsaved-session warnings without re-explaining state.

Yes, you need Node.js to execute the deterministic scripts that handle saving session state. The CLI commands run from your skills directory and require Node.js and filesystem access to update the v2 context.json and write native-memory markdown entries.

To migrate v1 context files to v2 context.json, run the dedicated migrate flow via CLI commands. This safe v1-to-v2 migration updates your session persistence format while preserving existing project memory and generated context documentation.

The best way to capture decisions and blockers in a local repository is using a session save command. This writes your ordered next steps and blockers into a versioned context.json and generates a human-readable CONTEXT.md, allowing you to resume work with a briefing later.

Yes, you can list multiple registered repositories and check their saved git history. A portfolio list command displays registered projects, while the resume briefing reads recent git history to highlight unsaved-session warnings and changes since your last save.