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.238 Home All releases ←olderv2.1.237 v2.1.239newer→
Claude Code v2.1.238

Durable wake subscriptions now say why they failed

Use it now
Useful2 Signal3
Artifacts

Failed wake subscriptions now show a reason in artifact status plus a one-off notification.

status
What

Arming a durable wake subscription is tracked while in flight and settles to registered, stopped, pending or unregistered. Failures show up as a durable_wake line in the artifact status output and as a one-shot notification, with a reason instead of silence.

Details
  • New reasons: no_wake_minter, tool_not_offered, org_not_enabled, flag_off, aborted and watch_trigger_release_failed.
  • The organization case says plainly that retrying will not help while that holds.
  • The gating on whether a subscription is attempted at all is unchanged.
Evidence

Wake subscriptions are not enabled for the user's organization, so none was registered; retrying will not help while that holds.

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.238 →