Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.277 ·

CCR worker requests can target a custom session URL

CCR worker requests can now target a custom session URL instead of the default endpoint

Under the hood No documentation found Internal Changes
JSON All of v2.1.277
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
CCRArea: what it touches
Internal ChangesKind: in v2.1.277,
Internal ChangesSection of the release

Unclear The finding does not say what CCR stands for or in what situation a custom ccrSessionUrl would be set.

What

The function that sends CCR worker requests to a Claude session now checks for a ccrSessionUrl() value from the host's launch options first. If one is set (with any trailing slashes removed), it's used as the base address for the /worker/... call; otherwise Claude Code falls back to the default .../v1/code/sessions/{id} URL. When a socket is used for the connection, the log now also notes "over ${socket path}" for extra context.

Why

This allows worker requests to be redirected to a non-default session endpoint, useful when a session isn't reachable at the standard URL.

Read from
Names in the bundleccrSessionUrl
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 doubtThe finding does not say what CCR stands for or in what situation a custom ccrSessionUrl would be set.

See this entry in the whole of v2.1.277 →

Feedback