Notifications

A session asked a question or finished replying — you want to know about it without keeping Clauder open. The clients do this differently because they are built differently.

	Android	web UI	the app	Telegram
who holds the connection	the phone, a foreground service	the browser's push service	the Rust shell	the machine itself, long polling
needs https	no	yes (or localhost)	no	no
works with the client closed	yes	yes	yes, from the tray	yes

About everything on the machine

The event parsing is shared, so notifications arrive not only about chats started in Clauder: a question from claude in the terminal gets through the same way — provided hooks are connected.

A separate toggle sends a warning about the plan limits at 95% — both for the 5-hour window and for the weekly ones (overall, per model, per third-party app).

Web Push

The api creates the VAPID keys itself on the first request and keeps them in its database. You can set your own through VAPID_PUBLIC_KEY / VAPID_PRIVATE_KEY (npx web-push generate-vapid-keys) and VAPID_SUBJECT.

Without https there are no browser pushes

That is the browser's requirement, not Clauder's: in an insecure context neither a service worker nor PushManager works. The simple way to get https is a one-click tunnel. Over a local network without it you still have notifications on Android, in the app and in the bot.

Android

Held by a foreground service with its own SSE stream — no Firebase. Notifications come straight from your machine and depend on nobody's cloud; in return, the phone has to let the service live in the background.

The app

The shell's system notifications plus the tray: the agent's state as a dot and "do not disturb for an hour". A reply or a question that arrives while no window is in focus marks the tray and flashes the window in the taskbar.

Quiet

Notifications that ring at the wrong time get switched off entirely. To keep it from coming to that, there are two ways to stay silent.

On a schedule. A quiet window is two times, "from" and "to", by the device's own clock; a window across midnight works too. Browser pushes, the app, Android and the page's sound all have one. Inside the window the end of a reply and limits stay silent, while a question from the agent wakes you by default: a question means the work has stopped, it isn't news. The "for an hour" pause in the app's tray silences everything and ignores the schedule.

While you are at the computer. The phone has no reason to ring about the end of a reply that is already in front of you. The server considers you at the machine if a claude prompt was typed in a terminal within the last five minutes (hooks are needed for that) or Clauder is open on a computer — visible, focused and with input in the last few minutes. A tab forgotten on a monitor doesn't count, and the phone doesn't count at all. Then browser pushes and Android stay silent about the end of a reply and limits, the Telegram bot about the end of a reply; a question wakes you, as in the quiet window. Each channel has its own switch, on by default. If the phone can't reach the server to ask, it rings: an extra notification is better than a missed one.

A sound when a reply finishes

A push about a chat that is open on screen doesn't arrive — that is by design — and a window's system notification is easy to miss while working in the next one. So the page can chime by itself: "Settings → Notifications → Sound when a reply finishes", five signals, volume and a quiet window of its own.

It is a device setting: the laptop may chime and the phone not. It sounds for the end of a reply in any chat, including claude in the terminal, but not for the agent's question and not while a background task is running under the session. Several windows open — one of them sounds; without https the browser doesn't let them agree, and then every visible one chimes.

What to subscribe to

Besides the general toggles there is watching one particular session: "watch" in a chat — and its replies will be announced separately, even if the general notifications are off.