{"version":"2.1.234","anchor":"background-task-notifications-arrive-inside-a-system-reminde","canonical_anchor":"background-task-notifications-arrive-inside-a-system-reminde","heading":"Background task notifications arrive inside a system-reminder","tier":"internal","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/background-task-notifications-arrive-inside-a-system-reminde","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Background task notifications arrive inside a system-reminder\n\nBackground task results can no longer fake harness messages by closing the reminder wrapper early.\n\n**What**\n\nAutomated background-task events delivered on your turn are now wrapped in a `<system-reminder>` envelope, and any closing tag inside the payload is escaped to `&lt;\/system-reminder&gt;` so content coming back from a task cannot close the reminder early and start speaking as the harness.\n\n**Details**\n\n- The escape is a case-insensitive global replace over the payload before wrapping.\n- The subagent prompt was updated to match: worker results arrive as user-role messages containing `<task-notification>` XML, delivered as harness input inside a reminder, and the model is told never to reproduce them in its own output.\n- The multi-agent example transcript now shows the nesting too.\n- Active on this build wherever task notifications are delivered.\n\n**Evidence**\n\n`Worker results arrive as **user-role messages** containing \\`<task-notification>\\` XML, delivered as harness input, normally inside a \\`<system-reminder>\\` that opens with`, `<task-notification>`\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}