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 and flags where something changed that needs your attention. It isn't a full activity log; the full story stays on the corresponding issue.
Where to find it
The inbox is the first section of the Work panel, above Pinned, Views, and Projects. The unread count shows next to the section title and as a badge on Work in the app rail; right-click Work for Mark all as read.
The section lists one row per issue, newest first, read and unread alike. A row shows the issue's status, its title and time, and who did what; a dot marks it unread. Hover a row for a card with the full title, the comment, and Open, Mark as read, and Archive.
On a phone, the Work panel sits in the drawer. Its Inbox section ends with All notifications, which opens the Inbox page with its own list and filters.
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, priority, or dates change (on other people's issues, only key updates by default; see below);
- an issue you subscribe to changes status, once you turn on Status changes, which is off by default;
- 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;
- an issue is created in a project 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 row; 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.
With Status changes on, a sub-issue's status change also notifies subscribers of the parent issue. Sub-issue comments, priority, and date changes do not bubble up to the parent.
Other people's issues
On an issue assigned to someone else or to their agent, a subscription you picked up by creating, commenting on, or being mentioned in it brings only key updates by default: @-mentions, replies in threads you took part in, and, with Status changes on, statuses that need a person, such as in_review, blocked, or done. Routine comments and other changes stay on the issue. Issues you subscribed to yourself, issues you follow through their project, and issues assigned to you or your agents still bring every kind of notification you have turned on.
The issue page marks such a subscription Key updates only. Its menu offers Get all activity, which turns it into an explicit subscription to this issue; there's no way back to key updates for that issue afterwards, only unsubscribing. Change the default opens Settings → Notifications, where Other people's issues, at the top of Issues you subscribe to, switches all such issues to All activity.
Agents and the inbox
Inbox notifications belong to workspace members. An agent may read and change the runtime owner's notifications only when the server verifies that the owner is the upstream human who triggered the run. This identity follows agent delegation chains. The rule covers every inbox action: the active, archived and snoozed lists, unread counts, and every change. Runs triggered by another person or without a verifiable human, and cloud-node credentials without a task binding, are refused. An agent's unread counts cover only the workspace its run belongs to, never the owner's other workspaces. Only people can delete notifications. The server logs each change an agent makes, with the agent, the run and the person it acted for.
@-mentioning an agent in a comment, assigning an issue to it, or triggering an autopilot creates a run directly; no notification is left for the agent. @all notifies members only.
Manage from the CLI
Use your existing CLI login to read and handle your notifications. Listing never marks anything read:
multica inbox count
multica inbox list --unread --since 1d --output json
multica inbox list --issue MUL-123
multica inbox list --archived # or --snoozedEach row shows the notification ID, the issue key, the type, who it is from, the title and a short summary of the comment or change. --unread, --issue (an issue key or UUID), --since (an RFC 3339 time or a duration such as 2h, 1d, 1w), --project and --type filter the list. --archived reads the whole archive page by page, so an issue archived long ago can still be found and restored. --project accepts a full UUID or a unique ID prefix, including the short ID from multica project list; no match or an ambiguous prefix produces an error. The table also keeps the issue, comment and project IDs and cuts the summary short; --output json has the full summary.
Handle notifications by the IDs the list shows:
multica inbox read <id>... # unread <id>... reverses it
multica inbox read --issue MUL-123 # every notification on one issue
multica inbox archive <id>... # unarchive <id>... restores
multica inbox snooze <id>... --until tomorrow # RFC 3339, 30m, 3h, 1d, 1w; unsnooze <id>... ends itAs in the app, reading, archiving or snoozing a notification on an issue applies to the whole issue, while marking one unread changes only that notification. A failure on one ID doesn't stop the others; the command reports which failed and exits non-zero.
The bulk actions match the inbox menu: multica inbox read --all, and multica inbox archive with --all, --read (issues whose newest notification is read) or --completed (issues in a done or closed status). They need --yes, or a typed confirmation when run by hand, and leave snoozed issues alone, except --completed: as in the app, it also archives a done or closed issue while it's snoozed, ending the snooze. Every change reports how many notifications it actually changed, whole issues included; one already in that state counts 0. --output json returns the same count, with the result for each ID. Notifications can't be deleted from the CLI.
An authorized agent run uses its task credential for all of this; it never falls back to a person's login.
Handle notifications
Click a row to open its issue at the comment or app request the notification is about. The row stays lit while the issue is open, and clicking it again takes you back to that spot. Opening the issue marks the notification read, and the row stays in the list. Notifications without an issue, such as autopilot pauses and quick-create results, open on the Inbox page instead.
An issue opened from the inbox carries the inbox's actions in its header:
- Snooze (
H) takes the issue out of your inbox until a time you pick, and opens the next one. See Snooze an issue below. - Mark as done sets the issue to
done, archives the notification, and opens the next one. It archives the notification even when Archive issues you complete is off. It's offered while the issue isn't done or cancelled yet. - Archive (
E) archives the notification and opens the next one. Archiving doesn't modify or delete the issue. - Unsubscribe & archive (
⇧E) is offered on issues that aren't yours: not assigned to you or to an agent you own. It unsubscribes you from the issue, archives the notification and opens the next one. Ordinary updates stop reaching your inbox, while @mentions still do. On an issue with sub-issues you choose between this issue only and this issue with all its sub-issues. For this issue only, the confirmation offers Undo, which restores the subscription as it was. Leaving the sub-issues as well can't be undone there; subscribe again on the issue page instead. The same action is on the hover card and in a row's right-click menu.
The next one is the next row the section lists under its current filters, so you can work through the inbox without going back to the list.
The filter button in the section header narrows the list by notification type, when it was received, and who it is from, or by the issue's status and priority. A filtered section keeps the button visible, and Clear filters resets it.
The section's ⋯ menu holds View archived and the bulk actions:
- Mark all as read;
- Archive all read;
- Archive completed, for issues in the
doneorclosedcategory; - Archive all.
View archived opens the archived notifications. More records load as you scroll, and filters apply to the entire archive, including records that have not loaded yet. Archived notifications keep their read state, so Unarchive (or E) brings one back exactly as you left it.
Snooze an issue
Snooze takes an issue out of your inbox until a time you pick, then brings it back on top, unread. Snooze from the alarm-clock button in the issue header (or press H), from the button beside Archive when you hover a row, or from a row's hover card. Pick 1 hour, 3 hours, 1 day, 3 days or 1 week, or Pick a date and time… for any time within a year. A day or more keeps the current time of day, except that one chosen between 22:00 and 6:00 comes back at 9:00. The confirmation lets you undo; undoing a change of time puts back the previous one.
While an issue is snoozed:
- new notifications on it wait with it and don't count toward the unread badge. When it comes back, the row says Snooze ended and how many updates arrived meanwhile;
- it comes back early when someone mentions you by name, it is assigned to you, a run fails, an app asks for your action, or all its sub-issues finish.
@allmentions don't wake it; - Mark all as read and the archive-all actions leave it alone. Archiving it ends the snooze, and so does completing the issue yourself while Archive issues you complete is on;
- opening the issue from anywhere else doesn't read it or end the snooze. Its header shows when it comes back; open that to bring it back now (
H) or change the time.
Snooze is personal: it only changes your own inbox. Everything you've snoozed is in the Snoozed view under Views, also reachable from View snoozed in the inbox menu.
When a notification leaves the inbox
Reading a notification doesn't remove it. A row leaves the inbox only when:
- you archive it, from its row, the hover card, the issue header, or a bulk action;
- you snooze its issue. This one is temporary: the issue comes back at the time you picked, or earlier when something needs you. See Snooze an issue;
- you move its issue to any status in the
doneorclosedcategory yourself, while Archive issues you complete is on (it is by default). Only your own notifications on that issue are archived, read or not. When someone else or an agent completes an issue, its notifications stay in your inbox, so you still see the news; - it's a Run failed notification and its issue moves to a status that hands it back to a person:
in_review, a custom status in thestartedcategory, or any status in thedoneorclosedcategory. This archives everyone's Run failed notifications on the issue, whoever moved it, and doesn't depend on the setting above.blockedis the exception: it hands the issue over too, but the work is still stuck, so the earlier failures are still worth reading. - your inbox in the workspace goes past 2,000 notifications. It keeps the newest 2,000 and shortly afterwards archives the older ones, read or not. A notification that comes back from a snooze or that you restore from the archive counts from when it came back. Notifications on a snoozed issue don't count and are left alone.
Open windows drop an archived row right away, except the one you have open. When its notification leaves the inbox some other way (you set the issue to done from its status, another window archived it, or an edit took it out of the section's filters), the row stays lit where it was and the issue header says what happened. Undo brings the notification back, and Next (or E) opens the next row. The row leaves once you move on.
When you take the open row out yourself, from the issue header, its row, the hover card, or a bulk action that includes it, the next row opens instead. With nothing left to open, the issue stays open. Archiving, marking as done and the bulk actions confirm with Undo, which brings the notifications back and leaves the issue's status as it is.
A later notification on the issue lands in the inbox again.
Settings → Notifications → Leaving the Inbox has the Archive issues you complete switch and links to the archived notifications.
Display and notification types
The sliders button in the Inbox section header opens its display settings, which are saved on this device:
- Rows shown: 5, 10, or 20; a Show more row lists the rest.
- Compact rows: one line per row instead of two.
- Unread count: the number next to the section title.
- Unread badge on Work: the badge on Work in the app rail.
Below them, Notify me about turns each kind of notification on or off. These are the same switches as Settings → Notifications, which groups them by how they reach you:
| Group | Kinds |
|---|---|
| About you | Assignments, Mentions, Reactions |
| Issues you subscribe to | Status changes, Comments, Priority & Due date |
| Projects you subscribe to | New issues |
| Agents | Agent activity (failed runs, and app actions an agent asked for that are blocked or expire) |
Status changes starts off; every other kind starts on. A kind that's turned off creates no notification, and turning it back on doesn't bring back what you missed; the changes are still recorded on the issue. A few types, such as quick-create results and autopilot pauses, sit outside these 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.
Chat with agents
A one-to-one conversation with an agent that only you can see. The agent starts with no issue context and doesn't create issues on its own; when you explicitly ask, it acts with your workspace access.
Search, shortcuts, and preferences
Search and run commands with ⌘K, review and rebind keyboard shortcuts, find text inside an issue, and set personal preferences such as theme, language, and time zone.