{"version":"2.1.221","anchor":"queued-task-notifications-keep-their-origin-and-mode","canonical_anchor":"queued-task-notifications-keep-their-origin-and-mode","heading":"Queued task notifications keep their origin and mode","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/queued-task-notifications-keep-their-origin-and-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Queued task notifications keep their origin and mode\n\nMessages from task notifications remember where they came from, so artifact subscriptions re-arm instead of replaying.\n\n**What**\n\nMessages expanded from a task-notification now carry where they came from onto each resulting user message.\n\n**Details**\n\n- the origin records source and slug; prompt-mode notifications also set queueMode to \"prompt\"\n- the main loop reads that origin to decide whether to re-arm an artifact subscription instead of replaying the message\n\n**Evidence**\n\n`queueOrigin`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}