{"version":"2.1.282","anchor":"new-session-inbox-kind-for-task-notifications","canonical_anchor":"new-session-inbox-kind-for-task-notifications","heading":"Task notifications from a session inbox get their own kind","tier":"internal","area":"Task Notifications","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/new-session-inbox-kind-for-task-notifications","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Task notifications from a session inbox get their own kind\n\nNotifications coming from a session inbox are now labelled as their own kind of task notification\n\n**Unclear.** It is not clear whether anything you can see depends on this new kind.\n\n**What**\n\nA task notification is a message Claude Code receives about background work. Notifications whose source is a session inbox are now classified as task notifications of the kind \"session-inbox\". Before, they had no kind of their own. The list of accepted kinds for incoming notifications now includes \"session-inbox\" alongside the existing ones.\n\nWhen a message's origin is recorded from one of these notifications, the \"session-inbox\" kind is left off, the same way \"projects-relay\" already was.\n\n**Why**\n\nClaude Code can now tell session-inbox notifications apart from other task notifications, which looks like groundwork for a session inbox feature.\n\n- Area: Task Notifications\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}