{"version":"2.1.288","anchor":"startup-timing-now-records-flag-fetch-kick-new-ccs-backgrou","canonical_anchor":"startup-timing-now-records-flag-fetch-kick-new-ccs-backgrou","heading":"New startup timing and background-session diagnostics","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/startup-timing-now-records-flag-fetch-kick-new-ccs-backgrou","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### New startup timing and background-session diagnostics\n\nClaude Code now reports when it starts fetching settings at startup, and adds diagnostics about background work in cloud sessions\n\n**Unclear.** What triggers these events is not known.\n\n**What**\n\nClaude Code's startup timing report now includes when it starts fetching its server-side settings and when that was judged. New diagnostic events cover background work:\n\n- `ccs_background_budget_halt`, about background work being stopped by a budget\n\n- `ccs_background_lost_agents_notice`, about lost agents\n\n- `ccs_background_exit_flush`, about sending data on exit\n\n- `ccs_mcp_task_records`, about MCP task records\n\n**Why**\n\nThese suggest that background work in cloud sessions can be halted when it runs over a budget.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}