{"version":"2.1.309","anchor":"runner-env-var-and-session-token-handling","canonical_anchor":"runner-env-var-and-session-token-handling","heading":"Runners pass CLAUDE_RUNNER_ALIVE_EVERY_MS and can apply session tokens while running","tier":"use","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/runner-env-var-and-session-token-handling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Runners pass CLAUDE_RUNNER_ALIVE_EVERY_MS and can apply session tokens while running\n\nCLAUDE_RUNNER_ALIVE_EVERY_MS is now passed through, and session and OAuth tokens can be applied while running in a certain mode\n\n**Unclear.** It is not stated which mode lets tokens be applied while running.\n\n**What**\n\nTwo changes to how Claude Code handles environment variables, the named settings a program reads when it starts:\n\n- `CLAUDE_RUNNER_ALIVE_EVERY_MS` joins the list of environment variables allowed through.\n\n- In a certain mode, Claude Code can apply `CLAUDE_CODE_SESSION_ACCESS_TOKEN` and `CLAUDE_CODE_OAUTH_TOKEN` values while it is already running. The token variables it lists are `CLAUDE_CODE_SESSION_ACCESS_TOKEN` and `CLAUDE_SESSION_INGRESS_TOKEN_FILE`.\n\n**Why**\n\nToken handling in hosted or runner sessions may change, so watch for differences if you set these variables.\n\n- Area: Self-Hosted Runners\n- Names: `CLAUDE_RUNNER_ALIVE_EVERY_MS`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}