Notifications
On this page
Short Leash's notifications tell you when something needs you: a process that stopped, a terminal that rang, new mail, a held webhook delivery, a slow query, a share that dropped, or an agent's finished task waiting for your review.
Where do I see them?
The bell in the power rail, beside the running count, shows how many you haven't read. It opens a list over any screen, grouped by site, each with what happened, how long ago, how many times when it's repeated, and its buttons; Mark all read clears the count. Click a notification to go to what it's about: Open logs opens the log at the line that explains it, and a slow query or an error opens on Dumps with that dump marked. The × on a notification dismisses it, and Clear all dismisses them all, with Undo for a few seconds. New ones also show for a moment at the bottom of the window. Inside a site, its unread ones are under Needs a look on its Overview.
The menu bar popover (the notification area on Windows) shows the latest one and how many are new; click it to open the bell in Short Leash's window, where each can be opened or dismissed.
What does Short Leash notify me about?
| Kind | When |
|---|---|
| Processes | A site's process, server or service stops by itself; a process kept running keeps crashing (after 5 quick crashes in a row Short Leash stops restarting it); a port is taken by another app, which the notification names |
| Terminals | A program in a site terminal rings the bell or sends a notification |
| New mail arrives: one notification per site for a burst of mail | |
| Webhooks | A delivery is held, fails its signature check, or isn't accepted by your site |
| Dumps | A query takes 500 ms or more, or your app logs an error |
| Sharing | A share connects, gets a new address, drops or fails |
| Tasks | Agents' reviews, blocks and lapsed claims: a coding agent finishes a task and it waits for your review ("Codex finished “…”", then "Ready for review in shop.test"), an agent is blocked on a task ("Codex is blocked on “…”", then its reason), or an agent's claim on a task runs out ("Codex's claim on “…” ran out", then "It's open to agents again"). See Tasks |
Each one says what happened and what to do next, with a button for it: restart the process, open its logs, open the terminal, copy the new address, or Open a task with it open beside its list. The same thing happening again within two minutes, or before you've read it, updates the one notification with a count instead of adding more. A task's second line (where it waits for review, or why the agent is blocked) shows under its text in the bell, under Needs a look on the site's Overview, and in the desktop notification.
How do I choose where they go?
In Settings › Notifications, each kind can be:
- Off: not kept at all;
- In app: listed under the bell only;
- In app and system: listed, and shown as a desktop notification while Short Leash's window isn't in front.
Processes, terminals and sharing reach your desktop to begin with; mail, webhooks, dumps and tasks stay in Short Leash. Notify me when an agent in Task settings turns Tasks off, or back on to In app, too. The unread count shows next to Short Leash's menu bar icon and on its Dock icon until you turn off Show the unread count on the menu bar icon. Your choices are saved in Short Leash's config.toml.
Are notifications kept?
Short Leash keeps the latest 200 with what you've read, until you dismiss them or Short Leash restarts. Webhook deliveries still held when it starts again are announced again. Notifications raised while the window is closed are waiting when you open it.