Claude CodeIntermediateClaude Code
Dump findings into a scratchpad during long investigations
Ask Claude to write its findings to a file; if the context degrades or you open another session, it reads the file instead of re-investigating.
In a long exploration the context fills up with tool output and older details get lost. A notes file keeps what matters: key classes, who calls what, limits of external APIs, migrations. In a new session you ask it to start by reading the file. This is a practice recommended by the guide, not a built-in Claude Code feature.
Example
Prompt: "While you explore the payments module, keep investigation-scratchpad.md with: key classes, who calls refund(), the external API's limits and relevant migrations. Update it after each finding." In the next session: "Read investigation-scratchpad.md and continue from there."