{"version":"2.1.323","anchor":"self-hosted-runner-log-tool-gets-registry-id-and-whentouse","canonical_anchor":"self-hosted-runner-log-tool-gets-registry-id-and-whentouse","heading":"Claude is told when to use the self-hosted runner log and requeue tools","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/self-hosted-runner-log-tool-gets-registry-id-and-whentouse","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Claude is told when to use the self-hosted runner log and requeue tools\n\nThe runner log tool and the session requeue tool now carry hints telling Claude when to use them\n\n**What**\n\nSelf-hosted runners are machines you run yourself to host Claude Code sessions. Claude Code has a tool that shows the end of a runner's log file with secrets removed from the text. That tool now carries a hint for the model. The hint tells the model to use it instead of reading or tailing the log file directly.\n\nThe tool that moves a stuck self-hosted session onto another runner, called requeuing, also gets a hint. It tells the model to use that tool when a session is stuck and about to be requeued. Both tools also get an identifier in the tool registry.\n\n**Why**\n\nWhen Claude looks at runner logs, it is now steered toward the tool that strips secrets, so passwords and keys in the log are less likely to end up in the conversation.\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}