Notifications

Get a notification when an agent needs a decision from you, then tap it to open that task at the card. Everything else waits for you to look. Notifications are optional; everything works without them.

#Turn on notifications

Notifications need an HTTPS address, such as one from Access from your phone. On iPhone and iPad, first install the app to your Home Screen and open it from there.

  1. Connect to your server.
  2. Select Enable notifications and allow the browser or system prompt.

To stop them on one device, select Turn off notifications there.

#What you'll be notified about

Only decisions interrupt you:

EventNotification
A task asks a decision (ask_owner)Decision: TITLE (3 options), opening the task at its card
Claude asks you a questionClaude has a question, with the question
A task needs approvalApproval needed: TOOL
The agent needs you in its browserYour agent needs you
A message may not have reached the agent after a stop, and later messages wait for itA message is waiting for you: TASK, with the message
A task stalled or stopped unexpectedly and needs you to recover itStalled: TASK and the like, with what happened
A room hand-off or PR notice waits for youThe hand-off or notice
A new phone or browser is paired, directly or through the relayNew device paired, with its name, on your other devices. If you didn't pair it, remove it in Settings

Not notified, but in the app when you look: finished turns, failed tasks, PRs that are ready or merged, notes agents post to you in a room (under Updates), and tool approvals of workers a lead started (under Needs you; their lead oversees them).

  • Batched. Decisions asked within two minutes of a notification arrive together as one, such as 3 decisions need you. Decisions you answered meanwhile are left out.
  • Quiet hours, 22:00 to 08:00 by default, in the time zone of the device that most recently turned on notifications, hold decisions until morning. Then one notification lists those still open. A task can mark a decision urgent, with its reason on the card (for example "the backend is down"); only those arrive during quiet hours.
  • Not while you're using the app. While you're using the app on any device (you tapped, typed or scrolled in the last minute, in a window that has focus), nothing is sent; the card just appears. A window merely left open on your desk doesn't count. If you leave without answering, a notification follows three minutes later, as long as the decision is still open and you haven't opened its task since, so a question left on your Mac still reaches your phone. It waits for quiet hours and joins other decisions like any other notification.
  • The icon badge counts open decisions, the same number as Needs you.

The server's owner can change this with CCR_CLOUD_QUIET_HOURS (for example 23:00-07:00, or off), CCR_CLOUD_PUSH_FALLBACK_MIN (how long the follow-up to an unanswered decision waits, default 3; 0 turns it off), CCR_CLOUD_TIMEZONE (the time zone quiet hours are read in before any device has reported one, for example Asia/Shanghai; default UTC) and CCR_CLOUD_PUSH=all, which also sends finished turns, failures and other news as they happen. See Configuration.

#Answer from the notification

Where the platform shows notification buttons (Chrome on Android, and Chrome or Edge on desktop; not iPhone or iPad today), an approval notification has:

  • Deny, always.
  • Allow once, only for tools that just read files (Read, Grep, Glob, LS and NotebookRead), and only when every path they read is inside the task's workspace. A read of anything outside it, such as your home directory or /etc, and anything that runs commands, edits files or uses the network, has only Deny; tap the notification to review it in the app, where the exact input is shown.

A button answers exactly the request in that notification. If the request was already answered, cancelled or interrupted, or the notification is more than a day old, the button does nothing and the app opens instead, so an old notification can never approve something else.

A question notification has no buttons: tap it to answer in the app, so a notification can never pick an answer for you.

#How delivery works

Each uuBright Console server has its own push keys and sends notifications directly through your browser's push service. No uuBright service is involved. Push availability depends on the browser and platform; if a notification doesn't arrive, the app still shows everything.

To check delivery to every registered device, use the HTTP API's test route. Set CCR_CLOUD_PUSH_SUBJECT to your own mailto: or https: contact address; push services use it to reach whoever runs the server, and Apple rejects localhost addresses.

#Discord

For notifications in Discord instead, set up Discord control. It sends direct messages for the same events and lets you answer approvals there. Discord follows its own settings, not the quiet hours above.