Sweep 22 Sep 2026 · 15:52Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Reading a new release v2.1.280 Building the pages · 4/6 1043 findings $36.88 so far
One change · claude-code

Checkpointing changed

checkpointing

Nearest release: v2.1.269, published 3 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Recorded here
Lines+9added
Lines−3removed
From line 6 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits5to this page, all time

### Messages sent mid-turn not checkpointed

The whole hunk

from line 6, old and new numbered
/
lines
from line 6
66 
77## How checkpoints work
88 
9As you work with Claude, checkpointing automatically captures the state of your code before each user prompt.
9As you work with Claude, checkpointing automatically captures the state of your code before each prompt you send that starts a turn.
1010 
1111### Automatic tracking
1212 
1313Claude Code tracks all changes made by its file editing tools:
1414 
15* Every user prompt creates a new checkpoint
15* Every prompt you send that starts a turn creates a new checkpoint
1616* Claude Code keeps file snapshots for the 100 most recent checkpoints in a session. Discarding an older checkpoint deletes the snapshot files that no remaining checkpoint references, except each file's first snapshot, which the VS Code extension uses as the baseline for its session diffs.
1717* Claude Code saves checkpoints with the conversation, so you can still run `/rewind` after you resume a session
1818* Claude Code deletes a session's file snapshots in the [retention sweep](/docs/en/claude-directory#cleaned-up-automatically), by default about 30 days after the session last saved one. Rewinding to a checkpoint whose snapshots are gone can fail with [`No files were restored`](/docs/en/errors#no-files-were-restored). To keep snapshots longer, set [`cleanupPeriodDays`](/docs/en/settings-reference#cleanupperioddays).
from line 25
2525 If the prompt input contains text, double `Esc` clears it instead of opening the menu. The cleared text is saved to your input history, so press `Up` to recall it after you finish in the rewind menu.
2626</Note>
2727 
28The rewind menu lists each prompt you sent during the session. Select the point you want to act on, then choose an action:
28The rewind menu lists each prompt you sent during the session, except [messages that joined a running turn](#messages-sent-mid-turn-not-checkpointed). Select the point you want to act on, then choose an action:
2929 
3030* **Restore code and conversation**: revert both code and conversation to that point
3131* **Restore conversation**: rewind to that message while keeping current code
from line 85
8585### External changes not tracked
8686 
8787Checkpointing only tracks files that have been edited within the current session. Manual changes you make to files outside of Claude Code and edits from other concurrent sessions are normally not captured, unless they happen to modify the same files as the current session.
88 
89### Messages sent mid-turn not checkpointed
90 
91When a message you [queue while Claude works](/docs/en/interactive-mode#queue-messages-while-claude-works) reaches Claude within the running turn, it joins that turn instead of starting a new one. The message appears in the conversation, but Claude Code doesn't create a checkpoint for it, and the rewind menu doesn't list it. A queued message that Claude Code sends as its own turn gets a checkpoint as usual.
92 
93To remove such a message, or undo the edits Claude made after it, rewind to the prompt that started the turn. That rewinds the whole turn, including the work Claude did before your message arrived.
8894 
8995### Symlinked and hard-linked paths not restored
9096