Answer: Checkpointing does not track or restore changes made by Bash commands to files Claude hasn't edited, subagent edits to other files, external/manual changes outside the session, messages sent mid-turn, and symlinked or hard-linked paths. Status: Check failed Entry: tool/claude-code/features/checkpoint-limitations Revision: 1 Digest: sha256:df9290093a61c611 (changes whenever the content changes) Timeline: Created: 2026-11-16T12:07:01Z Last changed: 2026-11-16T12:07:01Z Last verified: 2026-11-19T12:14:09Z Last attempt: 2026-11-20T12:18:27Z (failed) Next check: 2026-11-20T13:18:27Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Bash command changes | A file that only Bash commands changed isn't tracked and stays as it is. | [1] | 2026-11-19 Subagent edits | The subagent's edits to other files stay | [1] | 2026-11-19 External changes | Manual changes you make to files outside of Claude Code and edits from other concurrent sessions are normally not captured | [1] | 2026-11-19 Symlinked and hard-linked paths | Checkpointing doesn't rewind symlinked or hard-linked files. | [1] | 2026-11-19 Sources: [1] Anthropic. "Checkpointing". https://code.claude.com/docs/en/checkpointing.md Role: primary. Accessed: 2026-11-19T12:14:09Z Quote: "A file that only Bash commands changed isn't tracked and stays as it is." (Supports: Bash command changes) Quote: "The subagent's edits to other files stay, so use version control, such as Git, to revert them." (Supports: Subagent edits) Quote: "Manual changes you make to files outside of Claude Code and edits from other concurrent sessions are normally not captured" (Supports: External changes) Quote: "Checkpointing doesn't rewind symlinked or hard-linked files." (Supports: Symlinked and hard-linked paths) Published: 2026-11-19T10:35:13Z Snapshot SHA-256: f0f66aca749347801ad55fec8ee669c162152458eaf1e5f11f56dfe05d21d0e6 (captured 2026-11-14T12:14:09Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-16T12:07:01Z, so the values verified then were kept. Cross-check: not-available at 2026-11-19T12:14:09Z. No independent second source is configured for this entry Last successful check: 2026-11-19T12:14:09Z Last attempt: 2026-11-20T12:18:27Z (failed) Notes and limitations: Extracted automatically from a single official source (section "Limitations"). Related: https://latestn.com/tool/claude-code/features/checkpoint-retention-limit How many checkpoints does Claude Code keep for rewinding a session? https://latestn.com/tool/claude-code/features/checkpointing-limitations What are the limitations of Claude Code file checkpointing, such as Bash commands or subagent edits not being tracked? https://latestn.com/tool/claude-code/features/choose-extension-by-goal Which Claude Code extension should I use for a given goal, such as adding persistent context, connecting external services, or automating workflows? https://latestn.com/tool/claude-code/features/cache-lifetime-ttl How long does Claude Code's prompt cache last and can I choose the TTL? https://latestn.com/tool/claude-code/features/capabilities What can Claude Code do, like building features, fixing bugs, and automating tasks? https://latestn.com/tool/claude-code/features/check-plugin-usage How do I check whether a Claude Code plugin is still being used? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:18:27Z | check-failed | Extraction did not pass verification: answer does not contain any extracted value | — 2026-11-16T12:07:01Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/features/checkpoint-limitations/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/features/checkpoint-limitations POST: https://latestn.com/dispute/tool/claude-code/features/checkpoint-limitations with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/features/checkpoint-limitations?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What changes does Claude Code checkpointing not track or restore? Revision 1, last verified 2026-11-19T12:14:09Z. https://latestn.com/tool/claude-code/features/checkpoint-limitations (accessed 2026-11-21T09:53:07Z). @misc{LatestN_tool_claude_code_features_checkpoint_limitations_r1, title = {What changes does Claude Code checkpointing not track or restore?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/features/checkpoint-limitations}}, note = {Revision 1; digest sha256:df9290093a61c611; last verified 2026-11-19T12:14:09Z; accessed 2026-11-21T09:53:07Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/features/checkpoint-limitations