{"version":"2.1.227","anchor":"self-hosted-runner-setup-now-points-at-the-cloud-environment","canonical_anchor":"self-hosted-runner-setup-now-points-at-the-cloud-environment","heading":"Self-hosted runner setup now points at the Cloud environments admin page","tier":"notice","area":"Self-Hosted Runners","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/self-hosted-runner-setup-now-points-at-the-cloud-environment","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Self-hosted runner setup now points at the Cloud environments admin page\n\nSelf-hosted runner setup now sends you to Admin settings, Cloud environments.\n\n**What**\n\nThe guided setup for running Claude Code sessions on your own machines was rewritten for the new admin surface. It now sends operators to Admin settings, Cloud environments, rather than the Claude Code settings page.\n\n**Details**\n\n- Steps: turn on \"Allow self-hosted environments\", create the environment, copy the environment key, then read the Environment ID from the Configuration tab.\n- The tour of the interface was updated to match: the Activity tab now splits into Runners and Sessions views, keys are issued from Environment keys with \"Issue new key\", and diagnostic banners appear inside the environment view.\n- It warns that the older runner interface is still visible during the transition.\n\n**Evidence**\n\n`Allow self-hosted environments`\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}