# Notifications

> How an agent reaches you when you are not looking — which events notify, how to turn browser notifications on, and what to do when the browser has blocked them.

A **notification** is how an agent tells you something happened while you were somewhere else: a reply finished, a routine completed, a routine failed.

## When to use it

[Runs](/docs/work/runs/) keep going after you close the tab, and [routines](/docs/automate/routines/) run when nobody is watching. Notifications are the alternative to remembering to check the [Activity](/docs/work/activity/) board.

## What notifies you

| Event | Sent when |
| --- | --- |
| **Agent replies** | A run finishes while you are away from the conversation |
| **Routine completed** | A scheduled [routine](/docs/automate/routines/) run finishes |
| **Routine failed** | A routine run fails |
| **Routine skipped** | A routine run is skipped because a usage limit was reached |

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](/docs/work/questions/) or an [approval](/docs/work/approvals/) 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.

<Steps>

1. **Open Settings → General → Notifications.**

2. **Turn on Browser Notifications.** Your browser asks for permission the moment you do — not before.

3. **Allow it.** The toggle stays on and the four activity events above start arriving as browser notifications.

4. **Repeat on every browser and device you use.** A subscription belongs to one browser on one machine, not to your account.

</Steps>

Selecting a notification opens the conversation or project it came from.

<Aside type="caution" title="If the toggle will not turn on">
  The switch is disabled — with the reason written under it — when the browser
  cannot deliver notifications:

  - **Blocked for this site.** Permission can only be granted once. Open the lock
    icon in the address bar → Site settings → Notifications, allow them, then try
    the toggle again.
  - **iOS and iPadOS.** Web push works only after you add Endue to the Home Screen
    and open it from there.
  - **No secure connection.** Push requires HTTPS.
  - **Not available in this environment.** A server-side setting, not something you
    can fix from here.
</Aside>

## Choosing what you are told about

The same settings section lists the four 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 one switch, not four.** Turning them on covers the four activity events; turning an individual event off removes it from browser notifications too.
- **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 [routine](/docs/automate/routines/) side: a daily routine that produces one [output](/docs/capabilities/outputs/) is one notification, while one that reports every interim step is several.

## 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.

## Related

<CardGrid>
  <LinkCard
    title="Activity"
    href="/docs/work/activity/"
    description="Where blocked and finished work is visible without being told."
  />
  <LinkCard
    title="Routines"
    href="/docs/automate/routines/"
    description="Scheduled work — the main source of notifications."
  />
  <LinkCard
    title="Approvals"
    href="/docs/work/approvals/"
    description="What a waiting run is asking you to decide."
  />
  <LinkCard
    title="Runs"
    href="/docs/work/runs/"
    description="Why work continues after you close the app."
  />
</CardGrid>