{"version":"2.1.302","anchor":"fork-guidance-in-the-main-system-prompt-drops-runs-in-the-b","canonical_anchor":"fork-guidance-in-the-main-system-prompt-drops-runs-in-the-b","heading":"Fork instructions no longer always say the fork runs in the background","tier":"internal","area":"Subagents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/fork-guidance-in-the-main-system-prompt-drops-runs-in-the-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Fork instructions no longer always say the fork runs in the background\n\nClaude's instructions now say a fork runs in the background only when that applies; otherwise they say it keeps tool output out of view\n\n**What**\n\nA fork is a copy of the current Claude that goes off to do a side task. Claude's built-in instructions explain forks. They used to always say a fork runs in the background so Claude can keep chatting with you.\n\nNow that part appears only when a certain check passes. Otherwise the instructions say only that the fork \"keeps its tool output out of your context\", meaning the results of its work do not fill up Claude's main conversation.\n\n**Why**\n\nThis suggests forks may sometimes run in the foreground, with the instructions worded to match.\n\n- Area: Subagents\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}