{"version":"2.1.234","anchor":"explicit-artifact-watches-now-count-as-running-work","canonical_anchor":"explicit-artifact-watches-now-count-as-running-work","heading":"Explicit Artifact watches now count as running work","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/explicit-artifact-watches-now-count-as-running-work","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Explicit Artifact watches now count as running work\n\nFreshly armed artifact watchers now show as running work; quiet background ones stay hidden.\n\n**What**\n\nBackground Artifact watchers that Claude armed on its own used to never count as active work. Now a watcher counts as active if auto-react is enabled and it is still inside its freshness window, so explicitly requested or freshly armed live watches show up as running; quiet background ones stay invisible.\n\n**Details**\n\n- A separate list filter keeps automatically started watchers out of the visible task list unless the watch was marked as explicitly requested.\n- This depends on whether auto-react is enabled in the session, not on any build flag.\n\n**Evidence**\n\n`monitor_ws`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}