Agents can drop notifications in your notification feed when something happens that doesn't need a chat reply but you should still know about. A scheduled task finished, an app was deployed, a credential needs your approval, or the agent encountered something that requires your attention.

Where notifications show up

The bell icon in the top bar shows unread notifications. Click it to see the feed: most recent first, grouped by source. Each notification has:

• A title and body describing what happened
• A level (info, success, warning, error) that controls the icon and color
• A link that takes you to the relevant chat, task, or agent

Marking a notification as read just clears the badge. The entry stays in the feed.

What notifications are for

Source	Examples
Task	A scheduled task finished, a task failed, a delegated task is awaiting approval
App	An app was deployed, an app crashed, an app needs a credential rebind
Agent	An agent created a follow-up task, completed a long-running job, hit an unexpected error
System	Server restart, vault provider disconnected, a managed config changed
Security	A credential was accessed, a policy denied an action, an SSO login from a new device

Notifications are short and don't replace the chat. If there's a conversation to continue, the agent posts there first and adds a notification only when you might miss it.

Pausing the agent for input

Notifications are one-way. When an agent needs to ask you something or pause for your help, it uses a different mechanism: interactive prompts inside the chat.

• Questions. "Which format do you want, PDF, CSV, or Markdown?" Click an option and the agent continues.
• Approvals. App deploys and other irreversible actions surface as a Yes / No prompt before they run.
• Credential picks. A vault picker appears inline when the agent needs a secret.
• Browser takeover. When the agent hits a CAPTCHA or 2FA, it pauses and gives you a link to take over the browser session, then resumes when you're done.

These show up inline in the conversation (or as buttons / Reply YES or NO hints on the connected channel), not in the notification feed. See Chatting with Agents for what the interactive moments look like.

Tips

• Treat the feed as a passive log. If something needs immediate action, the agent will also send a chat message or pause for you.
• Read the level. error and warning deserve attention faster than info.
• Click through. Every notification links to the chat, task, or app it came from. Don't try to act on the notification alone.

Next steps

• Chatting with Agents. Where interactive prompts appear.
• Scheduling Recurring Work. The most common source of notifications.
• Building & Deploying Apps. Deploy events and approval flows.