Agent notifications

Agents can send notifications to you, and, when authorized, to other members of the workspace they run in. The in-chat tool-call card shows the title, message, audience, channels, and whether the send was deduped 🔔

Turn it on

Grant the agent notifications: write in the agent edit view. Without that permission the tool is not available to the agent at all.

What the agent can do

Send: to you, to specific workspace members, or to a named audience (all_members, admins, owner).
Attach a link: recipients tap the notification and land on the right chat, file, workspace, computer, or account page. When the agent attaches nothing, the link defaults to the current chat.
Read: only the agent's own caller inbox. It cannot read another person's notifications, even with broad permissions.

Links do not grant access. Recipients sign in as usual and the normal permissions apply to wherever the link points. Someone who cannot open the destination sees the usual permission screen. For the exact link kinds and delivery channels, see the Notifications API.

What the agent cannot override

Your channels: the agent asks for in-app, email, or web push, and idapt intersects that with each recipient's own settings.
Quiet hours: honored for everything except a small set of critical events.
The recipient list: anyone who is not a member of the active workspace is dropped.
Rate limits: up to 100 sends per 24 hours per sender, and no recipient receives more than 500 notifications an hour. A message to a whole audience counts as one send, not one per person.

Stop an agent from notifying you

To cut off future sends from a specific agent, open the agent's settings and remove its notifications permission. The tool disappears from that agent immediately.

Everything else is in your own hands: your channel preferences and quiet hours in your account settings apply to every agent at once, so you can quiet all of them without editing each one.

Good uses

A long-running job finished ("overnight analysis done").
Something failed and you need to act ("deploy aborted").
The agent reached a decision that needs you ("two candidate fixes, pick one").

Do not notify on routine chat output. Anything already visible in the chat is not a notification candidate.

Agent permissions and tools

Control what your agents can reach and which tools they can use.

Notifications

Your inbox, delivery channels, quiet hours, and how agents and the API notify you.

Notifications API

Send notifications to workspace members and manage your inbox programmatically.

Was this helpful?

What the agent can do

Send: to you, to specific workspace members, or to a named audience (all_members, admins, owner).

Attach a link: recipients tap the notification and land on the right chat, file, workspace, computer, or account page. When the agent attaches nothing, the link defaults to the current chat.

Read: only the agent's own caller inbox. It cannot read another person's notifications, even with broad permissions.

What the agent cannot override

Your channels: the agent asks for in-app, email, or web push, and idapt intersects that with each recipient's own settings.

Quiet hours: honored for everything except a small set of critical events.

The recipient list: anyone who is not a member of the active workspace is dropped.

Rate limits: up to 100 sends per 24 hours per sender, and no recipient receives more than 500 notifications an hour. A message to a whole audience counts as one send, not one per person.

Stop an agent from notifying you

To cut off future sends from a specific agent, open the agent's settings and remove its notifications permission. The tool disappears from that agent immediately.

Everything else is in your own hands: your channel preferences and quiet hours in your account settings apply to every agent at once, so you can quiet all of them without editing each one.