Answer: File checkpointing limitations include that rewinding doesn't undo Bash command changes except in files the main conversation had already edited with a tool such as Write or Edit, and subagent edits aren't tracked except a skill with `context: fork` running in the foreground. Checkpoints are also tied to the session that created them, creating/moving/deleting directories is not undone by rewinding, and remote or network files are not tracked. Status: Confirmed Entry: tool/claude-code/features/checkpointing-limitations Revision: 1 Digest: sha256:2945886bb0e1047f (changes whenever the content changes) Timeline: Created: 2026-11-13T03:02:43Z Last changed: 2026-11-13T03:02:43Z Last verified: 2026-11-20T12:16:36Z Next check: 2026-11-21T12:16:36Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Bash command changes | Rewinding doesn't undo changes a Bash command made, except in files the main conversation had already edited with a tool such as Write or Edit | [1] | 2026-11-20 Same session | Checkpoints are tied to the session that created them | [1] | 2026-11-20 File content only | Creating, moving, or deleting directories is not undone by rewinding | [1] | 2026-11-20 Local files | Remote or network files are not tracked | [1] | 2026-11-20 Sources: [1] Anthropic. "Rewind file changes with checkpointing". https://code.claude.com/docs/en/agent-sdk/file-checkpointing.md Role: primary. Accessed: 2026-11-20T12:16:36Z Quote: "Rewinding doesn't undo changes a Bash command made, except in files the main conversation had already edited with a tool such as Write or Edit" (Supports: Bash command changes) Quote: "Checkpoints are tied to the session that created them" (Supports: Same session) Quote: "Creating, moving, or deleting directories is not undone by rewinding" (Supports: File content only) Quote: "Remote or network files are not tracked" (Supports: Local files) Published: 2026-11-20T03:01:08Z Snapshot SHA-256: 004c69ad606b2e96872840ecf1a1bb63068e55c29a488d351ba2d38fba3ca760 (captured 2026-11-14T12:12: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-15T12:16:01Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:16:36Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:16:36Z Last attempt: 2026-11-20T12:16:36Z Notes and limitations: Extracted automatically from a single official source (section "Limitations"). Related: 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/choose-scan-effort How do I choose the scan effort level for a Claude Security scan in Claude Code? https://latestn.com/tool/claude-code/features/clean-up-worktrees How do I clean up worktrees that Claude Code created? 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/claude-code/features/checkpoint-limitations What changes does Claude Code checkpointing not track or restore? 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/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-15T12:16:01Z | recovered | Check succeeded again | — 2026-11-14T12:12:11Z | check-failed | Extraction did not pass verification: answer does not contain any extracted value | — 2026-11-13T03:02:43Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/features/checkpointing-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/checkpointing-limitations POST: https://latestn.com/dispute/tool/claude-code/features/checkpointing-limitations with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/features/checkpointing-limitations?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the limitations of Claude Code file checkpointing, such as Bash commands or subagent edits not being tracked? Revision 1, last verified 2026-11-20T12:16:36Z. https://latestn.com/tool/claude-code/features/checkpointing-limitations (accessed 2026-11-21T09:53:32Z). @misc{LatestN_tool_claude_code_features_checkpointing_limitations_r1, title = {What are the limitations of Claude Code file checkpointing, such as Bash commands or subagent edits not being tracked?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/features/checkpointing-limitations}}, note = {Revision 1; digest sha256:2945886bb0e1047f; last verified 2026-11-20T12:16:36Z; accessed 2026-11-21T09:53:32Z} } 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/checkpointing-limitations