---
title: Inbox and subscriptions
description: When Multica notifies you, and how to mute issues you don't care about.
---

import { Callout } from "fumadocs-ui/components/callout";

The inbox is where Multica **interrupts** you — [issues](/issues) assigned to you, [`@` mentions](/comments), and activity on issues you're subscribed to all land here.

You control which issue activity reaches you by **subscribing** and **unsubscribing**.

## 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](/tasks) you assigned fails**

## `@all` notifies the entire workspace

`@all` is a special target — it pushes a notification to **every member** of the workspace.

<Callout type="warning">
**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.
</Callout>

## 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-issues) — 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.

<Callout type="warning">
**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.
</Callout>

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 `multica 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](/comments) — how `@` mentions work and the gotchas
- [Assigning issues to agents](/assigning-issues) — how agents are triggered (and why they don't read the inbox)
