Follow Discord
Sweep 30 Oct 2026 · 01:02Z Build v2.1.314 532 read Stable v2.1.308 Latest v2.1.314 Next v2.1.314 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.314 ·

Self-hosted runners can renew their token and prepare a fresh machine per session

Self-hosted runners can now renew an expiring runner token, and gain a fresh-machine-per-session option for single-session runners

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

Unclear It is not clear how freshMachinePerSession is turned on.

What

A self-hosted runner is a machine you run yourself that picks up Claude Code sessions to work on. Two things change:

  • The runner can now renew its runner token, the credential it uses to receive work, instead of only fetching it once.
  • Starting a session gains a freshMachinePerSession option. When it is set and the runner handles one session at a time, Claude Code starts the session with a different set of arguments.

The runner also drops its warmup report options. A new way to declare fresh-machine support through --runner-declares= is present but cannot take effect in this build, and the existing nested-repository declaration works as before.

Why

Long-running self-hosted runners should no longer fail when their runner token expires.

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 clear how `freshMachinePerSession` is turned on.

See this entry in the whole of v2.1.314 →

Feedback