{"version":"2.1.300","anchor":"self-hosted-runner-logging-reworked","canonical_anchor":"self-hosted-runner-logging-reworked","heading":"Self-hosted runner logs now carry a timestamp on every line","tier":"notice","area":"Self-Hosted Runner","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/self-hosted-runner-logging-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Self-hosted runner logs now carry a timestamp on every line\n\nOutput from the self-hosted runner now goes through one writer that stamps each line with the time, including stderr from the `git --version` check\n\n**What**\n\nA self-hosted runner is a machine you run yourself to carry out Claude Code work. Its output used to be printed directly to the terminal. It now goes through a single shared writer that puts a timestamp at the start of each line. The runner also logs a description of itself at debug level, a more detailed logging level that is usually hidden.\n\nThe error output from the `git --version` check the runner does is now captured and written through the same writer instead of going straight to the screen.\n\nClaude Code also has a new message saying that your rules don't apply on a self-hosted runner.\n\n**Why**\n\nPeople running the runner get logs where every line is stamped the same way, which makes them easier to read and match against events.\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}