Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.242 Home All releases olderv2.1.241 v2.1.243newer
Claude Code v2.1.242

Answers sent back to a cloud session are retried, and losses are reported

You'll notice
Useful4 Signal3
Cloud Sessions

Your answers to cloud-session prompts are retried with backoff, and you are told if one is lost.

What

When you answer a permission prompt, dialog or hook for a session running in the cloud, the answer is now kept if it cannot be delivered, re-posted with a 1s, 5s, 15s and 45s backoff, and re-sent on reconnect. If it is finally lost you get a message naming which kind of answer went missing and suggesting you interrupt and retry.

Details
  • Retention is behind the manager setting keepUndeliveredResponses; without it an answer is posted once and forgotten.
  • Hook answers have a separate "overtaken" path for when the cloud worker cancelled the request before the answer arrived.
  • Also here: hook callbacks forwarded from the cloud and answered on this machine, send gates that can hold or withdraw a queued message, and a withheld first prompt that is retried and reported through tengu_home_seed_prompt_resequenced.
Evidence

A permission answer you gave could not be delivered to the cloud session, which may still be waiting for it. If the session looks stuck, interrupt it and retry.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.242 →