Inbox and subscriptions
When Concierto notifies you, and how to mute issues you don't care about.
The inbox is where Concierto interrupts you. issues assigned to you, @ mentions, activity on issues you're subscribed to, and chat replies all land here.
You control which issue activity reaches you by subscribing and unsubscribing.
One bell, two registers
The inbox and Needs You share a single surface with two segmented tabs — Needs you | Inbox:
- Needs you (the default tab) holds structured decisions your agents paused to ask — answer them in place and the work resumes.
- Inbox holds everything else: mentions, assignments, subscription updates, and chat replies — awareness, not blockers.
Each tab wears its own badge: pending decision count on Needs you, unread count on Inbox. Both /inbox and /needs-you open the same page, and deep links land on the right tab automatically (a decision link opens Needs you with the card ringing; an issue link opens Inbox with the item selected).
What shows up in your inbox
The following events deliver a notification to your inbox:
- Issue assigned / unassigned / reassigned, you're notified when you're the new (or former) assignee
- Status, priority, or due date change on an issue you're subscribed to
- New comment on an issue you're subscribed to
- You're
@-mentioned in a comment, delivered whether or not you're subscribed - Someone reacts to your issue or comment
- An agent task you assigned fails
- An agent replied in chat — one live item per conversation; the newest reply replaces the previous item instead of stacking. Selecting it opens the chat, and opening the chat marks the item read
- An agent started a track from your chat — when a deliverable ask you made in chat is concerted into a staffed track, you get a "Started a track" item linking to it
@all notifies the entire workspace
@all is a special target, it pushes a notification to every member of the workspace.
Use @all sparingly. In a 50-person workspace, one @all comment produces 50 inbox notifications instantly. Reserve it for high-stakes events (production incidents, milestone announcements), not everyday discussion.
Agents never receive notifications
Agents never get inbox notifications. Not even when they're the assignee, creator, or @-mentioned in a comment.
This isn't a bug: agents don't read an inbox. They work by immediate trigger, assigning an issue or @-mentioning the agent in a comment kicks off a task for it right away. The inbox is a reminder mechanism for humans; it has no meaning for agents.
Subscription rules
You're auto-subscribed to an issue in four situations:
- You created it
- You were assigned to it
- You commented on it
- You were
@-mentioned on it or in one of its comments
Auto-subscription happens once, being both the creator and a mentionee doesn't subscribe you twice.
Reassignment doesn't auto-unsubscribe you. If you used to be the assignee and got replaced, you'll still receive updates on that issue, the auto-subscription stays in the database.
To stop getting notified, open the issue and unsubscribe manually.
You can also manually subscribe to any issue (even unrelated ones), or manually unsubscribe from any auto-subscription. In the UI, use the right panel on the issue page; in the CLI, use concierto issue subscriber add/remove.
Sub-issue status changes bubble up to the parent
When a sub-issue's status changes, subscribers of the parent issue are notified too, even if they haven't subscribed to the sub-issue.
This applies to status only: comment, priority, and due date changes on sub-issues do not bubble up.
Next
- Comments and mentions, how
@mentions work and the gotchas - Assigning issues to agents, how agents are triggered (and why they don't read the inbox)