{"version":"2.1.309","anchor":"self-hosted-runner-code-review-sessions-start-only-once-ne","canonical_anchor":"self-hosted-runner-code-review-sessions-start-only-once-ne","heading":"Self-hosted runners refuse to start a code review session twice","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/self-hosted-runner-code-review-sessions-start-only-once-ne","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Self-hosted runners refuse to start a code review session twice\n\nA self-hosted runner now refuses a code review session another worker has already taken, and its `--startup-timeout-min` help was reworded\n\n**What**\n\nA self-hosted runner is a program you run on your own machines to host Claude Code sessions. If a code review session has already been taken by a worker, the runner now refuses to start it again and reports an error, because a code review is started only once.\n\nThe help text around `--startup-timeout-min` has been rewrapped. It lists `SELF_HOSTED_RUNNER_SESSION_IDLE_MS` as the environment variable for the idle option.\n\n**Why**\n\nFor people running self-hosted runners, this stops one code review from being run twice by different workers.\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}