Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.259 ·

Early hydrate prefetch for SDK/remote-control resume sessions

Starting with --sdk-url and --resume now warms session and history state in parallel with the rest of startup.

TierYou'll noticehow much it should matter to you
Useful3my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaSDKwhat it touches
KindImprovementsin v2.1.259,
You'll notice

Starting with --sdk-url and --resume now warms session and history state in parallel with the rest of startup.

When starting with --sdk-url and --resume, the CLI can now kick off an early hydrate-reads prefetch (startEarlyHydrateReads) concurrently with the rest of startup, to warm session/history state ahead of the SDK connection coming up. The result is threaded through as earlyHydrateReads in the prepared-session config.

Read from
Names in the bundle--resume
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Common workflows touched a line naming --resume after this was published. | [`/loop`](/docs/en/scheduled-tasks) | The current CLI session | Quick polling while a session is open. `--resume` and `--continue` restore unexpired fixed-interval loops. | common-workflows see the edit
Confirmed since Anthropic's documentation has since written up --resume, on Claude Code changelog. * Improved `--continue` / `--resume`: the conversation appears immediately instead of waiting for SessionStart hooks, and the first message no longer re-reads the whole transcript changelog see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up --resume, on Claude Code changelog.
Anthropic's release notes agreeFixed --resume failing (and --continue opening an empty conversation) when a saved session contains an attachment entry with no payload

See this entry in the whole of v2.1.259 →

Feedback