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,
servedCallRequestsJumpQueueandurgentRequestIds(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_QUEUEenvironment variable, falling back to the feature gatetengu_valiant_rain(off by default). - In the client's event-writing pipeline,
control_request/control_cancel_requestevents are now routed into a separate 'urgent' queue and sent immediately ahead of the normal batch whenservedCallRequestsJumpQueue()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.
tengu_valiant_rain Off by default, switched on for this accountThe 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
Whether this behavior is active for a given reader cannot be determined here: the `tengu_valiant_rain` flag controlling it…
New in this build: tengu_valiant_rain