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

Claude Code v2.1.224 ·

Self-hosted runner operator tools

Nine operator tools can inspect runners, sessions, secrets, health, metrics and logs, loaded only via --base-tools.

Use it now Notable No documentation found New Features
JSON All of v2.1.224
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
Self-Hosted RunnerArea: what it touches
New FeaturesKind: in v2.1.224,
What probably matters to youSection of the release
What

Nine new tools let an operator inspect and drive a self-hosted runner fleet: self_hosted_runner_get_pool, _list_runners, _list_sessions, _list_secrets, _spawn_local, _read_health, _read_metrics, _tail_log and _requeue_session. They load only when the CLI's --base-tools names one of them, and never when CLAUDE_CODE_REMOTE is set or the session kind is "bg". Auth reuses the operator's existing OAuth session, and tailed logs are redacted for secrets before reaching model context.

Details
  • The enabling latch is one-way in production: the internal helper that turns the operator tools back off is documented as test-only.
  • When a runner spawns a session, any tool name starting with self_hosted_runner_ is stripped from the server-supplied tools list before launch, so a spawned session cannot be handed fleet-operator tools.
  • If stripping empties the list, the --tools argument is dropped entirely and the default tool pool is used.
Evidence

[runner:session] Stripped self-hosted-runner operator tool names from the server-supplied tools arg, self_hosted_runner_spawn_local

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundleCLAUDE_CODE_REMOTE

See this entry in the whole of v2.1.224 →

Feedback