{"version":"2.1.310","anchor":"background-exit-handoff-carries-wake-only-artifact-live-slug","canonical_anchor":"background-exit-handoff-carries-wake-only-artifact-live-slug","heading":"Backgrounded sessions can stay subscribed to artifact comments","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/background-exit-handoff-carries-wake-only-artifact-live-slug","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Backgrounded sessions can stay subscribed to artifact comments\n\nWhen a session goes to the background, it can now keep artifact subscriptions that wake it to react to comments\n\n**Unclear.** It is not stated what causes the built-in artifact tool to be hidden from MCP servers, so it is unclear which sessions this applies to.\n\n**What**\n\nWhen a session (one conversation with Claude) is moved to the background, Claude Code hands over a list of artifacts it is still watching. Previously that list held only artifacts being watched live. It can now also hold artifacts watched only so they can wake the session, and those subscriptions stay open.\n\nThis applies to sessions set up to react automatically to artifact activity, with a watch on that activity already armed, and only when the built-in artifact tool is hidden from MCP servers (outside programs that give Claude Code extra tools).\n\n**Why**\n\nIn practice, someone commenting on an artifact can wake a backgrounded session so it reacts, instead of the comment going unnoticed until you return.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}