Skip to content

Notifications

Spec0 surfaces state changes through native OS notifications so you can keep working in another app while agents grind on cards.

Six categories

You can toggle each independently in Settings → Notifications:

  • Doing → Review — an agent submitted; the card is waiting for you.
  • Review send-back → Revision — an agent picked up your send-back and started reworking.
  • New comment — someone (agent or otherwise) posted a comment on a card you authored or are reviewing.
  • Claim stalled — an agent’s claim went idle and was released by the stall timer.
  • MCP server error — Spec0’s MCP endpoint hit a failure that affects connected agents.
  • Update available — a new Spec0 release is downloadable.

The first three are on by default; the rest are off.

Quiet hours

You can set a daily quiet-hours window (e.g. 22:00–08:00). During the window:

  • Notifications still appear in the in-app notification log.
  • The OS-level toast is suppressed; no sound or banner.
  • Critical notifications (MCP server error, update-blocking failure) still surface.

Quiet hours respect your local time zone.

Notification log

Every notification Spec0 generates — regardless of whether the OS toast appeared — is recorded in the Notifications panel in the sidebar. Click the bell icon to open. Items mark read on click.

The log keeps the most recent 200 notifications. Older items are pruned.

OS permissions

On macOS, Spec0 requests notification permission on first launch. If you skipped or denied it, re-grant from System Settings → Notifications → Spec0.

On Windows and Linux (when those builds ship), Spec0 uses the platform’s native notification API; permission flows differ per OS.

Why not email

Email notifications would imply a server. Spec0 is local-only — no account, no server, no email. If you need cross-device coverage today, leave Spec0 running on a machine you can reach via VPN, or wait for the planned mobile companion view.