Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.284 ·

Promo eligibility status is cached on disk with a configurable max age

Promo eligibility is now saved per account and endpoint and reused for up to an hour, with a new statusMaxAgeSeconds setting controlling the age

Group of 2 Under the hood Internal Changes
JSON All of v2.1.284
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Usage & LimitsArea: what it touches
Internal ChangesKind: in v2.1.284,
Internal ChangesSection of the release

Unclear It is not clear which promotion this is or when the promotion check is switched on.

What

When Claude Code starts, it may check whether your account is eligible for a promotional credit and whether you have already claimed it. That answer used to be kept only in memory for the running program, so every startup asked the server again. Now:

  • promoStartupStatusCache saves the eligible and claimed status in the global config file, separately for each account and each server address (endpoint).
  • The saved answer is reused for up to 3600 seconds (one hour) instead of asking the server on every startup.
  • The status is asked again after /clear, the command that starts a new conversation.
  • The promo claim config gains statusMaxAgeSeconds (minimum 0, default 3600), which is passed as maxAgeSeconds to the status request.
  • When statusMaxAgeSeconds is not zero, the local cache is no longer rewritten from the fetched status. Before, it was updated whenever the eligible or claimed value differed.

Why

In practice Claude Code makes fewer network requests about promotions when it starts. If a promo's status changes on the server, it can take up to the configured max age before a new startup notices.

Read from
Names in the bundle/clear
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 Create custom subagents touched a line naming /clear after this was published. `SendMessage` checks that a name still refers to the same agent it reached earlier in the conversation. If a newer agent has taken the name, such as a re-spawned background agent that reused it, Claude Code refuses the send rather than del… sub-agents see the edit
Confirmed since Anthropic's documentation has since written up /clear, on Claude Code changelog. * Fixed a brief freeze (up to a second) partway through long sessions outside fullscreen mode, which came back after `/clear` or `/compact` changelog see the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which promotion this is or when the promotion check is switched on.
Anthropic's documentation agreesAnthropic's documentation has since written up /clear, on Claude Code changelog.

See this entry in the whole of v2.1.284 →

Feedback