Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

Urgent control requests can now jump the upload queue

Certain control requests can now skip ahead of the normal upload queue when jump-queue mode is enabled

Group of 3 Use it now Improvements
JSON All of v2.1.280
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
TelemetryArea: what it touches
ImprovementsKind: in v2.1.280,
What probably matters to youSection of the release

What

Claude Code's remote-tools upload pipeline can now let certain requests jump ahead of the normal batch queue:

  • A session/worker class gained two new fields, servedCallRequestsJumpQueue and urgentRequestIds (a Set), alongside its existing heartbeat/upload-trim state.
  • Whether jump-queue behavior is active is decided by a helper that checks the CLAUDE_CODE_REMOTE_TOOLS_JUMP_QUEUE environment variable, falling back to the feature gate tengu_valiant_rain (off by default).
  • In the client's event-writing pipeline, control_request/control_cancel_request events are now routed into a separate 'urgent' queue and sent immediately ahead of the normal batch when servedCallRequestsJumpQueue() is true, with urgent request IDs tracked in a bounded set.

Why

This lets time-sensitive control requests, like cancellations, get delivered promptly instead of waiting behind a backlog of normal batched uploads.

Read from
Feature flag
tengu_valiant_rain Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

This account: on · anonymous baseline: on · compiled default in v2.1.280: off

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.280. It isn't a statement about your account. What a flag value here can and cannot tell you

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 doubtWhether this behavior is active for a given reader cannot be determined here: the `tengu_valiant_rain` flag controlling it…
The name it cites is new in this buildNew in this build: tengu_valiant_rain

See this entry in the whole of v2.1.280 →

Feedback