{"version":"2.1.295","anchor":"self-hosted-runner-remove-session-state-and-confine-rep","canonical_anchor":"self-hosted-runner-remove-session-state-and-confine-rep","heading":"Runner help warns about leftover session state and shows warn as default","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/self-hosted-runner-remove-session-state-and-confine-rep","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Runner help warns about leftover session state and shows warn as default\n\nSelf-hosted runner help now says session state stays on disk when cleanup is off, and marks warn as the default confinement mode\n\n**What**\n\nA self-hosted runner is a machine you run yourself that starts Claude Code sessions for jobs. Its help text has changed for two options:\n\n- `--remove-session-state`: the help now says that when this is off, session state is left on disk where later sessions can read it.\n\n- `--confine-repo-settings`: the help now lists three modes, `warn`, `enforce` and `off`, and marks `warn` as the default. Before, it listed only `enforce` and `off`. The same choice can be set with `SELF_HOSTED_RUNNER_CONFINE_REPO_SETTINGS`.\n\n**Why**\n\nOperators reading the help can now see that turning off cleanup leaves one session's data readable by the next, and that confinement only warns unless they choose `enforce`.\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}