Source Intelligence
Follow Discord

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.247 Home All releases ←olderv2.1.246 v2.1.248newer→
Claude Code v2.1.247

Cloud hook registrations go dormant while a machine is idle and re-register on the next turn

You'll notice
Useful2 Signal3
Cloud Sessions

Hook registrations for cloud sessions lapse while idle and re-register automatically on your next turn.

What

A machine that registered to run hooks for a cloud session no longer holds that registration open indefinitely while nothing happens. After a period with no use the registration is allowed to lapse, and the next message, turn or send registers it again automatically. Declining consent disarms the registration straight away rather than leaving it in limbo, and a lapsed registration is now treated as its own state rather than counted as a failure.

Details
  • The registration record carries a lapsesUnusedAt deadline; a record still marked as registered but past that deadline is now reported as dormant.
  • The deadline is cleared when the registration is renewed, unregistered or reset.
  • Dormancy follows from the session standing reported by the server, so there is no local flag, setting or environment variable that turns it on or off.
  • Declining consent now takes a branch that abandons the registration outright instead of continuing.
  • The registration tracker handles several outstanding instance leases at once rather than a single one.
  • Internal signals mark consent decided, turn started, turn ended and general activity; a further one waits, with a timeout, for an in-flight registration to complete before a send goes out.
  • Dormancy is recorded as its own telemetry outcome, together with whether the machine had registered before.
  • Users see the wording Hooks from this machine are idle for this cloud session: nothing has used it for a while, so their registration was allowed to lapse; it is made again when the session is next used., with separate wording for a registration that was never answered at all.
Evidence

lapsesUnusedAt, Hooks from this machine are idle for this cloud session: nothing has used it for a while, so their registration was allowed to lapse; it is made again when the session is next used., ensureRegistered

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.247 →