Inbox and subscriptions

One place for assignments, mentions, comments, and agent failures that need your follow-up.

The inbox collects the work activity that concerns you. It's not a full activity log — it flags where something changed that needs your attention; the full context stays on the corresponding issue.

What lands in the inbox

Common notifications include:

an issue is assigned to you, or moved away from you;
an issue you subscribe to gets a new comment, or its assignee, status, priority, or dates change;
someone @-mentions you in an issue description or comment;
an issue or comment you created gets a reaction;
an agent run fails on an issue you subscribe to;
creating an issue through an agent completes or fails;
an autopilot you subscribe to creates a new issue, or is paused after consecutive failures.

Your own actions don't notify you. Multiple notifications on the same issue merge into one entry; open it to see the issue's recent changes.

Sources of automatic subscription

These participants subscribe to an issue automatically:

the issue's creator;
a new assignee;
anyone who comments;
anyone newly @-mentioned in the issue description;
subscribers preconfigured in an autopilot.

Changing the assignee does not remove existing subscriptions. Subscribe or unsubscribe anytime on the issue page; after unsubscribing, ordinary updates stop reaching your inbox, while direct @-mentions still notify you individually.

When a sub-issue's status changes, subscribers of the parent issue are notified as well. Sub-issue comments, priority, and date changes do not bubble up to the parent.

Agents don't use the inbox

The inbox is only for workspace members. Even when an agent is the assignee or a subscriber, it never reads inbox notifications.

@-mentioning an agent in a comment, assigning an issue to it, or triggering an autopilot creates a run directly instead of leaving the agent a notification. @all notifies members only.

Handle notifications

Selecting a notification marks it as read. Archive it when you're done; archiving doesn't modify or delete the corresponding issue. Once an issue reaches in_review, done, or cancelled, its run-failure notifications archive automatically.

Right-click a notification for Mark as read / Mark as unread and Archive (Unarchive in the Archived view). Mark as unread is the "I looked, but I'm not done with this" action: the notification goes back to unread and raises the unread count again, and it stays unread even while you keep it open — opening it again later marks it read as usual. Archived notifications keep their read state, so restoring one brings it back exactly as you left it.

From the inbox menu you can also:

mark all as read;
archive all, or archive all read;
archive notifications for issues in done or cancelled;
open Archived and restore a notification.

Tune notification types

Open Settings → Notifications to toggle each group separately:

assignments;
status changes;
comments;
mentions;
priority and dates;
agent activity.

Turning a group off doesn't stop the changes from being recorded on the issue — it only stops the inbox notifications. A few types, such as reactions, quick-create results, and autopilot pauses, sit outside these six groups and are always delivered. System and browser notifications control desktop banners and don't change the inbox itself.

Next steps

Comments — replies, mentions, and discussion threads.
@-mention agents in comments — member notifications vs. agent runs.
Autopilots — configure automatic work creation and default subscribers.