Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.309 ·

Runner and remote-session setup failures now say what kind of failure it was

When a self-hosted runner or remote session fails to set up, the error now carries a failure kind such as filesystem error or repo settings rejected

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

What

A self-hosted runner is a machine you run yourself that starts Claude Code sessions for the web. When setting up such a session fails, the error is now tagged with a failure kind instead of being passed on unlabelled:

  • Failing to write the git proxy configuration is tagged SETUP_FAILURE_KIND_SOURCE_PREP_FAILED.
  • Failing to restore git hook stubs, or to clean up git state in the runner's home folder, is tagged SETUP_FAILURE_KIND_FILESYSTEM_ERROR.
  • Failures while confining the session to its folders or resolving real paths are tagged with kinds such as SETUP_FAILURE_KIND_REPO_SETTINGS_REJECTED and SETUP_FAILURE_KIND_FILESYSTEM_ERROR. Clone failures go through a similar wrapper.
  • The error result reported when runner setup fails now includes a setup_failure_kind field.

Other runner setup changes in the same code:

  • The disableAllHooks warning is skipped when a new flag is set.
  • The list of extra working folders takes an extra input.
  • In VM mode, host registration also passes along notes.

Why

Programs and people watching runner sessions can tell what kind of setup problem happened, such as a filesystem error or rejected repository settings, instead of seeing a generic setup error.

See this entry in the whole of v2.1.309 →

Feedback