{"version":"2.1.314","anchor":"self-hosted-runner-fresh-machine-per-session-and-runner-tok","canonical_anchor":"self-hosted-runner-fresh-machine-per-session-and-runner-tok","heading":"Self-hosted runners can renew their token and prepare a fresh machine per session","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/self-hosted-runner-fresh-machine-per-session-and-runner-tok","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Self-hosted runners can renew their token and prepare a fresh machine per session\n\nSelf-hosted runners can now renew an expiring runner token, and gain a fresh-machine-per-session option for single-session runners\n\n**Unclear.** It is not clear how `freshMachinePerSession` is turned on.\n\n**What**\n\nA self-hosted runner is a machine you run yourself that picks up Claude Code sessions to work on. Two things change:\n\n- The runner can now renew its runner token, the credential it uses to receive work, instead of only fetching it once.\n\n- 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.\n\nThe 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.\n\n**Why**\n\nLong-running self-hosted runners should no longer fail when their runner token expires.\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}