{"version":"2.1.292","anchor":"task-notification-messages-can-carry-a-runid","canonical_anchor":"task-notification-messages-can-carry-a-runid","heading":"Background task notifications can now carry a run identifier","tier":"internal","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/task-notification-messages-can-carry-a-runid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Background task notifications can now carry a run identifier\n\nNotifications about background tasks can now include a run identifier when they did not already have one\n\n**What**\n\nWhen a background task finishes or reports progress, Claude Code adds a notification message to the conversation. These notification messages can now carry a run identifier, a label that ties the notification to one specific run. It is added only when the notification did not already have one.\n\nTwo new labels for MCP calls also appear in the same area. MCP servers are outside programs that give Claude Code extra tools. One label is for an answer whose stream ended, and the other is for a call that was not sent again.\n\n**Why**\n\nIn practice, a notification can now be matched to the run it came from.\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}