Screens / The app around the agent

Notifications and the away digest

Tell people what happened while they were away, in the order they'd act on it, and let them choose what reaches them.

For: Everyone who isn't watching the product all day.

Markdown

3 ways to lay it out

1. Away digest on return

Pick it when: The default: when someone comes back, say what needs them first.

A summary at the top of the page: waiting on you, failed, finished, each a short group.

Away digestProWhat happened since you were last here: waiting on you, failed, finished.
Relative timeFreeWhen, as people say it.
InboxProThe full list behind each line.

Install away digest on return

Pro and Premium items need a licence key; free ones install as they are.

2. Bell and notification centre

Pick it when: Products used all day, where news arrives while the person is working.

A bell in the top bar opening a list of notices, newest first.

Notification centerProEverything that happened while you were away, behind a bell.
ToastProShort notices in the corner: polite for successes, assertive for errors.
Task trayProBackground work as one pill.

Install bell and notification centre

Pro and Premium items need a licence key; free ones install as they are.

3. Preferences and email

Pick it when: People ask to turn things down, or you send email about runs.

A grid of event kinds by channel, with a preview of the email beside it.

Notification preferencesProWhat reaches you, and where: one row per kind of event, one column per channel.
Channel setupProWhere agents can reach the team outside the app.
Email layoutProThe email shell: one next step, and why you got it.

Install preferences and email

Pro and Premium items need a licence key; free ones install as they are.

Rules that matter most here

Unknown stays unknown
"Nothing happened" is said only when the service knows nothing did; if it couldn't check, it says so.
Motion never says something false
A notice announcing a failure is assertive and stays until dismissed; a success is polite and goes.
The agent is always named, by the app
Each line names the agent, from your records.

Brief for a coding agent

Paste this into the agent that builds the screen. The docs MCP server returns the same text from get_screen.

Build notifications with Candor UI: AwayDigest on return, NotificationCenter behind a bell, Toaster for live notices.
Order the digest by what the person would act on: waiting on you, then failed, then finished.
Successes are polite toasts that go; errors are assertive and stay until dismissed.
Name the agent on each line from your records. Say "nothing happened" only when the service knows nothing did.
Let people choose what reaches them with NotificationPreferences (kind by channel) and ChannelSetup.
Emails use EmailLayout: one next step, and why the person got it.

Start from the "Away digest on return" layout: A summary at the top of the page: waiting on you, failed, finished, each a short group.
Candor items: away-digest (https://candor.themethodic.com/docs/away-digest.md), relative-time (https://candor.themethodic.com/docs/relative-time.md), inbox (https://candor.themethodic.com/docs/inbox.md).
Install: npx candor-ui add away-digest relative-time inbox
Read each item's docs before using it and take its props from there; don't guess them. Pro and Premium items need the person's licence key, which they add with `npx candor-ui key <key>`; don't ask for it.