Every Claude Code session starts fresh. You re-explain your project structure, build commands, and conventions. Every. Single. Time.

I built cck to solve this. Two modes:

*1. CLAUDE.md Generation* ```bash git clone https://github.com/takawasi/claude-context-keeper && cd claude-context-keeper && pip install . cck sync ``` Scans your codebase, generates CLAUDE.md. Claude reads it at session start.

*2. Per-Turn Context Injection (the real power)* ```bash cck setup --cb-style cck watch --with-history & cck hook install --use-history ``` This tracks every file change in SQLite and injects recent changes on every turn: ``` [CCK] Recent changes: 15:23:45 ~ src/main.py 15:22:30 + src/utils/helper.py 15:20:12 ~ tests/test_main.py ```

Claude sees exactly what you just edited. No more "I just changed X" explanations.

Built from 300+ Claude Code sessions. Zero AI calls, pure static analysis.

GitHub: https://github.com/takawasi/claude-context-keeper