What problem does it solve?
ck keeps your project’s evolving notes, goals, decisions, and “where I left off” in persistent per-project memory so you don’t have to re-explain everything each time you start a Gemini session.
Core Features & Use Cases
- Persistent context per project: Registers a project once and stores structured session history in context.json, regenerating CONTEXT.md for readable guidance.
- Session lifecycle commands: Use /ck:resume for a full briefing and /ck:save to record your session outcomes (including decisions, next steps, and blockers) with optional goal syncing.
- Session start auto-injection: A session-start hook automatically injects a compact first-message briefing for the registered project (and a mini portfolio view for unregistered directories).
Use Case: You’re implementing a feature across multiple days; ck captures your decisions, blockers, and next steps at each session, then re-loads a bordered briefing so you can immediately continue work without losing context.
Quick Start
Ask your AI to run /ck:init to register the current project, then continue by saving your first session state with /ck:save after you finish what you were working on.