{"version":"2.1.247","anchor":"housekeeping-tasks-are-flagged-so-hosts-can-keep-them-out-of","canonical_anchor":"housekeeping-tasks-are-flagged-so-hosts-can-keep-them-out-of","heading":"Housekeeping tasks are flagged so hosts can keep them out of activity indicators","tier":"internal","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/housekeeping-tasks-are-flagged-so-hosts-can-keep-them-out-of","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Housekeeping tasks are flagged so hosts can keep them out of activity indicators\n\nHousekeeping tasks carry an ambient marker so hosts can keep them out of activity spinners.\n\n**What**\n\nTask events now carry an `ambient` marker for work Claude Code does not present as yours, and the SDK task shape exposes it. Hosts that show a spinner or activity light can filter these out.\n\n**Details**\n\n- Set for every task that skips the transcript, plus automatically started live-update watchers.\n- Emitted both on task telemetry and in the SDK schema, whose description tells hosts to exclude them.\n- Unconditional.\n\n**Evidence**\n\n`True for housekeeping tasks the CLI does not surface as user work (every skip_transcript task, plus auto-started live-update watchers); hosts should exclude them from activity indicators.`\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}