{"version":"2.1.295","anchor":"self-hosted-runner-new-self-hosted-runner-server-auto-mode","canonical_anchor":"self-hosted-runner-new-self-hosted-runner-server-auto-mode","heading":"Self-hosted runners can choose which server auto mode lists apply","tier":"use","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/self-hosted-runner-new-self-hosted-runner-server-auto-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Self-hosted runners can choose which server auto mode lists apply\n\nA new `SELF_HOSTED_RUNNER_SERVER_AUTO_MODE_LISTS` setting lets self-hosted runner operators limit which server-supplied auto mode lists sessions follow\n\n**Unclear.** Which of the three values the runner uses when the variable is not set is not stated.\n\n**What**\n\nA self-hosted runner is a machine you run yourself that starts Claude Code sessions on your behalf. In auto mode, Claude Code decides whether to allow an action using lists of allowed and restricted actions, and the server can supply some of those lists. A new environment variable, `SELF_HOSTED_RUNNER_SERVER_AUTO_MODE_LISTS`, sets which of the server's lists the runner's sessions apply. It accepts three values:\n\n- `all`: sessions apply the server's lists.\n\n- `no-allow`: a narrower setting that, as its name says, leaves out the server's allow lists.\n\n- `none`: sessions apply none of the server's auto mode lists, not even its soft_deny restrictions.\n\nAny other value is rejected with an error when the runner reads its configuration.\n\n**Why**\n\nRunner operators can now decide how much the server's own allow and deny lists shape what sessions on their machines may do. Be careful with `none`: it also drops the server's restrictions, not only its permissions.\n\n- Area: Self-Hosted Runners\n- Names: `SELF_HOSTED_RUNNER_SERVER_AUTO_MODE_LISTS`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}