{"version":"2.1.248","anchor":"admin-tools-for-self-hosted-runners","canonical_anchor":"admin-tools-for-self-hosted-runners","heading":"Admin tools for self-hosted runners","tier":"soon","area":"Self-Hosted Runners","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/admin-tools-for-self-hosted-runners","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Admin tools for self-hosted runners\n\nTools exist for inspecting self-hosted runner pools, sessions, secrets and logs.\n\n**What**\n\nA group of tools for inspecting self-hosted runner setups now exists: read pool state, list runners, sessions and secrets, tail logs, start a local runner, and one write action that moves a session onto a different runner. Their descriptions state that secret values are never returned and that they authenticate with the operator's existing login. Whether these are reachable by ordinary users is not settled by the tool definitions themselves.\n\n**Evidence**\n\n`self_hosted_runner_requeue_session`\n\n- Area: Self-Hosted Runners\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}