napkin

You can track debugging mistakes and fixes across sessions by maintaining a per-repo napkin log that records errors, corrections, and working patterns. This ensures continuous learning by preserving knowledge of what works and what does not across different workflows.

A per-repo napkin log is a running note of mistakes, corrections, and patterns kept within a repository. It captures errors and their resulting fixes during debugging to build a persistent knowledge base for continuous session logging.

To start logging session notes and mistakes, open or create the napkin.md file inside the .agent/memory/ directory. Read the file at the start of each session and update it continuously as you work through debugging and interactions.

Yes, you can archive older session notes when the debugging log grows too large through automatic rotation. The system archives older notes by rotating them to a distilled.md file, keeping your workspace lean and focused on current patterns.

No, the per-repo session log does not require any external dependencies or components. It operates independently within your repository, storing all tracking data locally in markdown files inside the .agent/memory/ directory.