https://github.com/tolitius/checkpoint 👆something that helps me with: context window size limit " /compact ": losing most of the intel " –resume ": losing the nuance and the session’s “connective tissue” when working on a complex task Claude Code builds up a rich understanding: file relationships, hypotheses about bugs, rejected approaches, half-formed theories. you step away. you come back. –resume replays the conversation log but the nuance is gone — compaction summarized it away, thinking traces evaporated, attention degrades on a bloated context. checkpoint captures in-flight understanding as structured files, so a fresh session can reload it and pick up where you left off what it captures knowledge graph — entities and relationships Claude discovered, structured as connections not prose open threads — hypotheses, hunches, “I noticed something weird on line 247 but haven’t investigated yet” decisions — what was tried, what worked, what failed and why key evidence — raw tool outputs that informed understanding (the actual grep results, not a summary) reload prompt — a pre-composed document structured for Claude’s attention patterns I use this approach for some time now, and it could take a minute or two to capture and store the checkpoint, but it’s really worth it if I need to clear the context / leave the session and came back / etc. submitted by /u/tolitius
Originally posted by u/tolitius on r/ClaudeCode
You must log in or # to comment.