{"version":"2.1.247","anchor":"background-task-notifications-stop-re-attaching-file-context","canonical_anchor":"background-task-notifications-stop-re-attaching-file-context","heading":"Background task notifications stop re-attaching file context","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/background-task-notifications-stop-re-attaching-file-context","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Background task notifications stop re-attaching file context\n\nBackground task completion notices no longer drag file attachments back into your turn.\n\n**What**\n\nNotifications that a background task finished, whether a local shell command, an auto-backgrounded MCP call or an MCP task poll, no longer pull file attachments into the turn.\n\n**Details**\n\n- The notification is enqueued with an attachments-skipping flag that the print loop now honours.\n- Adopted tasks no longer get an `[exited with code \u2026]` banner appended to their output.\n\n**Evidence**\n\n`skipAttachments: !0`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}