{"version":"2.1.269","anchor":"bg-tasks-report-running-telemetry-field-now-normalized-defa","canonical_anchor":"background-tasks-report-running-flag-now-defaults-to-on","heading":"Background-tasks 'report running' setting now defaults to on","tier":"notice","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/bg-tasks-report-running-telemetry-field-now-normalized-defa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Background-tasks 'report running' setting now defaults to on\n\nThe CLAUDE_CODE_BG_TASKS_REPORT_RUNNING setting now defaults to on, and its telemetry reflects that\n\n**What**\n\n- The helper that decides whether background task \/ pending-notification status gets reported now reads the `CLAUDE_CODE_BG_TASKS_REPORT_RUNNING` env var directly and treats it as on unless it is explicitly set to false, replacing a previous implementation tied to focus-request settling.\n\n- The `tengu_tool_cpu_by_phase` telemetry event's `bg_tasks_report_running` field now comes from that same normalized helper, instead of logging the raw (and possibly undefined) env var value.\n\n**Why** Background task status reporting now works by default without needing the env var set explicitly, and the telemetry that records this setting is now accurate instead of reflecting an unset raw value.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}