{"version":"2.1.295","anchor":"startup-timing-hides-time-origin-when-a-check-is-true","canonical_anchor":"startup-timing-hides-time-origin-when-a-check-is-true","heading":"Startup timing data can leave out the process start time","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/startup-timing-hides-time-origin-when-a-check-is-true","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Startup timing data can leave out the process start time\n\nStartup timing data now omits the process's absolute start time under one condition\n\n**What**\n\nIn remote sessions (where `CLAUDE_CODE_REMOTE` is set) and on hosts that set `CLAUDE_CODE_EMIT_STARTUP_TIMING`, Claude Code reports how long startup took. That report now leaves out the absolute time the process started under one condition. Before, it always included it.\n\n**Why**\n\nThis is a small change to timing data only and does not change how Claude Code behaves.\n\n- Area: Telemetry\n- Names: `CLAUDE_CODE_EMIT_STARTUP_TIMING`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}