Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.299entry #27

Claude Code v2.1.299 ·

Self-hosted runners can be told to use a separate host for tools

On self-hosted runners, the session token answer can name a tools host, which skips the remote setup fetch and keeps the token out of the environment

You'll notice Improvements
JSON All of v2.1.299
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Self-Hosted RunnerArea: what it touches
ImprovementsKind: in v2.1.299,
What probably matters to youSection of the release

Unclear It is not stated when the server includes a tools host in its answer.

What

A self-hosted runner is a machine you run yourself to carry out remote Claude Code sessions. When the runner asks the server for a session token, the answer may now also describe a tools host: where the session's tools are served from, an address for API calls and a working folder. When it does:

  • The runner skips fetching the usual /remote setup and uses a setup built from that answer.
  • The session token is not set as CLAUDE_CODE_SESSION_ACCESS_TOKEN.
  • The session keeps its tool-server settings in a separate folder.
  • If the tools host description cannot be read, the runner stops with an error saying the answer holds a tools host it cannot read.
Why

This prepares for sessions whose tools run in a separate hosted container. Scripts that rely on CLAUDE_CODE_SESSION_ACCESS_TOKEN will not find it in such sessions.

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 stated when the server includes a tools host in its answer.

See this entry in the whole of v2.1.299 →

Feedback