{"version":"2.1.227","anchor":"remote-startup-timing-accepts-numbers-supplied-by-the-runner","canonical_anchor":"remote-startup-timing-accepts-numbers-supplied-by-the-runner","heading":"Remote startup timing accepts numbers supplied by the runner","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/remote-startup-timing-accepts-numbers-supplied-by-the-runner","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Remote startup timing accepts numbers supplied by the runner\n\nOn remote runs, startup timings can be supplied by the runner through an environment variable.\n\n**What**\n\nOn remote runs, startup phase timing can merge a JSON blob from the `CCR_RUNNER_STARTUP_TIMING` environment variable into the reported figures, validating each field for type, range and pattern: names must be lowercase with underscores, and numbers and phase durations are capped. Prewarm, prefetch and delta-reset values from the environment are reported alongside. Nothing is reported unless `CLAUDE_CODE_REMOTE` is set.\n\n**Evidence**\n\n`CCR_RUNNER_STARTUP_TIMING`\n\n- Area: Sessions\n- Names: `CCR_RUNNER_STARTUP_TIMING`, `CLAUDE_CODE_REMOTE`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}