Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.318 ·

Session spawns now carry a spawn reason into the runner's logs

Remote session spawns now pass a spawn_reason, and the self-hosted runner's spawn-hook log lines include it

Group of 2 You'll notice Improvements
JSON All of v2.1.318
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Self-Hosted RunnerArea: what it touches
ImprovementsKind: in v2.1.318,
ImprovementsSection of the release

What

To spawn a session is to start a new one. A spawn hook is a command run when that happens. The self-hosted runner, a machine you operate yourself that runs Claude Code sessions, now records why each session was started.

  • The spawn context now carries spawn_reason when it is text, and an empty string otherwise.
  • The runner's spawn-hook log lines now include reason= with that value, on both success (ok) and refusal (nack) lines. Before, they had no reason field.
  • A new onServerIdleLimit callback is connected to the fetch of remote configuration.

Why

If you operate a self-hosted runner, the logs now show why each session was started. That makes it easier to work out why a spawn succeeded or was refused.

Read from
Names in the bundlereason=

See this entry in the whole of v2.1.318 →

Feedback