Skip to main content
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: The in-app panel always receives notifications. Email, Slack DM, and mobile push are the channels you opt into per kind.
Slack DM toggles are only available once Slack is connected and direct messages are ready. Connect Slack under Settings → Connections.

​
Notification kinds

There are four kinds, each tied to a point in the task lifecycle:

​
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).
Open Settings → Notifications and flip the Email, Slack DM, or Mobile push switch for each kind.

​
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 — so you can answer an agent’s question or continue a task without leaving your inbox.
The reply address is bound to one task and signed, so each notification’s reply lands on the correct task.
See Notification preference endpoints for the programmatic surface.