{"version":"2.1.287","anchor":"background-artifact-thread-prompt-tells-the-model-not-to-res","canonical_anchor":"background-artifact-thread-prompt-tells-the-model-not-to-res","heading":"Background artifact threads are told not to pick up main-session work","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/background-artifact-thread-prompt-tells-the-model-not-to-res","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Background artifact threads are told not to pick up main-session work\n\nWhen an artifact thread is handled in the background, the model is now told to leave pending tasks, agents and next steps to the main session\n\n**What**\n\nClaude Code can handle an artifact thread in the background, as a separate piece of work alongside your main conversation. The instructions given to the model for that background work now include an extra rule. Anything that belongs to the main session stays with the main session, and the background thread must not resume, relaunch or check on it. That covers:\n\n- Pending tasks\n\n- Background agents (helper instances of Claude working on their own)\n\n- Monitors\n\n- Next steps listed in a summary\n\nThe background thread is told that the thread itself is its whole job.\n\n**Why**\n\nThis keeps the background thread focused on its own task, so it does not drift into work that your main session is already handling.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}