You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.269,
What probably matters to youSection of the release
What
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.
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.
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.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up CLAUDE_CODE_BG_TASKS_REPORT_RUNNING, on Environment variables.| `CLAUDE_CODE_BG_TASKS_REPORT_RUNNING` | Set to `0` to make a non-interactive session report an idle status to its host at every turn end, even while background work is still running. By default, the session keeps reporting a running stat…env-varssee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up CLAUDE_CODE_BG_TASKS_REPORT_RUNNING, on Environment variables.
Anthropic's release notes agreeFixed remote and headless sessions reporting "waiting for your input" while background agents were still running (set…
