{"version":"2.1.242","anchor":"artifact-comment-monitors-say-exactly-who-holds-them","canonical_anchor":"artifact-comment-monitors-say-exactly-who-holds-them","heading":"Artifact comment monitors say exactly who holds them","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/artifact-comment-monitors-say-exactly-who-holds-them","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Artifact comment monitors say exactly who holds them\n\nIf resuming can't take back Artifact comment replies, you now get a specific reason and advice instead of one vague message.\n\n**What**\n\nWhen you resume a session and it cannot take back automatic replies to comments on an Artifact, the single old \"held by a background session\" state is replaced by three specific reasons, each with concrete advice.\n\n**Details**\n\n- `held_by_live_session`: \"this conversation is also open in \u2026\", followed by advice to close those sessions or stop the agent.\n- `held_by_job`: \"they were last turned on from a background agent of this conversation, which keeps them while it runs (see `claude agents`)\".\n- `other_org`: \"this Artifact is in another of your organizations. Run \/login and sign in to that organization\".\n- Telemetry on `artifact_live_subscribe` reports matching reasons `resume_held_live`, `resume_held_job` and `resume_holder_unknown` plus holder counts.\n- Reachable by anyone resuming a session that had a live Artifact; no flag.\n\n**Evidence**\n\n`held_by_live_session`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}