> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runaether.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Notifications

> Notification channels, the event kinds you can subscribe to, and replying by email.

Aether notifies you when an agent needs your input or finishes work. Every notification is one canonical row that can fan out to multiple channels. Configure delivery under **Settings → Notifications**.

## Channels

Notifications are delivered to four channels:

| Channel         | How it reaches you                                                                                                                                                                                                                   |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **In-app**      | The notifications panel in the web app. Every notification appears here — it is the canonical inbox and cannot be turned off.                                                                                                        |
| **Email**       | Sent to your profile email address. Toggle per notification kind.                                                                                                                                                                    |
| **Slack DM**    | A direct message in Slack. Requires a connected Slack workspace with DMs enabled; toggle per notification kind.                                                                                                                      |
| **Mobile push** | A push notification on registered devices. Server-side support is live and the toggle is available now; device registration arrives with an upcoming Aether mobile app update, and no pushes are delivered until a device registers. |

The in-app panel always receives notifications. Email, Slack DM, and mobile push are the channels you opt into per kind.

<Note>
  Slack DM toggles are only available once Slack is connected and direct messages are ready. Connect Slack under **Settings → Connections**.
</Note>

## Notification kinds

There are four kinds, each tied to a point in the [task lifecycle](/concepts/tasks-and-lifecycle):

| Kind                  | Fires when                                                                |
| --------------------- | ------------------------------------------------------------------------- |
| `question_requested`  | An agent pauses and asks for your input (`ask_user`).                     |
| `plan_requested`      | An agent needs you to approve or reject a proposed plan (`propose_plan`). |
| `task_response_ready` | An agent finishes a response and waits for your next message.             |
| `task_failed`         | An agent cannot complete the task automatically.                          |

## Per-kind preferences

Notification preferences are set per kind, per channel. On the Notifications page, each kind has an **Email** switch, a **Slack DM** switch, and a **Mobile push** switch. Turning a switch on lets that kind fan out beyond the in-app panel to that channel. The in-app panel is unaffected by these switches.

A toggle is disabled when its channel isn't available — for example, the Email switch is off-limits when no profile email is set, and the Slack DM switch is off-limits until Slack is connected with DMs ready. Mobile push can be toggled at any time; it delivers nothing until a device registers, which requires a mobile app version with push support (rolling out separately).

<Tabs>
  <Tab title="Web">
    Open **Settings → Notifications** and flip the Email, Slack DM, or Mobile push switch for each kind.
  </Tab>

  <Tab title="CLI">
    Manage delivery preferences with [`aether notification`](/cli/notification).
  </Tab>
</Tabs>

## Reply by email

Email notifications support replying directly. When an agent asks a question or waits on a response, the email's reply address is a signed, task-specific address of the form `reply+<token>@<domain>`. Replying to that email routes your message back to the task — the same as responding from the web app or [`aether task respond`](/cli/task) — so you can answer an agent's question or continue a task without leaving your inbox.

<Info>
  The reply address is bound to one task and signed, so each notification's reply lands on the correct task.
</Info>

See [Notification preference endpoints](/api-reference/account/notifications/get-user-notifications) for the programmatic surface.