Notifications
A notification is how an agent tells you something happened while you were somewhere else: a reply finished, a schedule completed, a schedule failed.
When to use it
Runs keep going after you close the tab, and schedules run when nobody is watching. Notifications are the alternative to remembering to check the Activity board.
What notifies you
| Event | Sent when |
|---|---|
| Agent replies | A run finishes while you are away from the conversation |
| Schedule completed | A run started by a schedule finishes |
| Schedule failed | A scheduled run fails |
| Schedule skipped | A scheduled run is skipped because a usage limit was reached |
| Agent notice | An agent decides you need to know something during a run of a schedule set to Only when the agent notifies |
A schedule set to Only when the agent notifies does not send Schedule completed. It reaches you through agent notices instead, and still reports failures and skips.
Steps inside a run do not notify. Tool calls, intermediate results, and streamed text appear in the conversation, which is where you read them.
A run that stops for a question or an approval shows up on the Activity board under Waiting, and in the Needs review count in its header. That board is the reliable way to find blocked work.
Turning on browser notifications
Browser notifications reach you when the Endue tab is closed entirely.
-
Open Settings → General → Notifications.
-
Turn on Browser Notifications. Your browser asks for permission the moment you do — not before.
-
Allow it. The toggle stays on and the activity events above start arriving as browser notifications.
-
Repeat on every browser and device you use. A subscription belongs to one browser on one machine, not to your account.
Selecting a notification opens the conversation or project it came from.
Choosing what you are told about
The same settings section lists the activity events with a toggle each. Turning one off silences it everywhere, in the app and in the browser.
Two things worth knowing about the switches:
- Browser notifications are turned on once per browser, then tuned per event. Turning them on covers every activity event, agent notices included. While they are on, each event’s row also has a Push switch. Turn it off to keep that event in the app without a browser notification. The Push switch cannot be changed while the event’s own toggle is off.
- Email is not available yet. The row is there, marked as coming.
Keeping them useful
Notifications that always fire stop being read. The habit that keeps them signal is on the schedule side: a daily schedule that produces one output is one notification, while one that reports every interim step is several. A schedule that watches for a change can go further: set it to notify you only when the agent has something to tell you. See Schedules.
Limits
- Notifications tell you something happened; they are not where you act. Questions and approvals are answered in the conversation.
- Browser notifications are per browser. Turning them on at your desk does nothing for your phone.
- Revoking notification permission in the browser turns delivery off without changing the toggle’s own preference; the note under the switch explains the state.
- Notifications are per account, covering all your agents. There is no per-agent setting.
- Email notifications are not available yet.