{"version":"2.1.242","anchor":"resuming-a-session-restores-artifact-watches-up-to-a-cap","canonical_anchor":"resuming-a-session-restores-artifact-watches-up-to-a-cap","heading":"Resuming a session restores Artifact watches up to a cap","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/resuming-a-session-restores-artifact-watches-up-to-a-cap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Resuming a session restores Artifact watches up to a cap\n\nResuming re-arms your recorded Artifact watches up to the session limit and names any it couldn't restore.\n\n**What**\n\nWhen you resume a session, Claude Code now re-arms the Artifact watches it had recorded instead of giving up as soon as one live watch exists. It restores as many as the per-session limit allows and tells you which ones it could not, either because the limit was reached or because the watch could not be proven still valid.\n\n**Details**\n\n- Cap message: \"this session can watch at most <N> Artifacts at once. Ask Claude to stop watching one, then publish one of these again, to turn its replies back on.\"\n- The other case asks you to have Claude watch the Artifact again or publish it again.\n- No flag gates this.\n\n**Evidence**\n\n`watch_cap`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}