Notifications

YOLO Studio keeps you in the loop when something needs your attention: a Kanban card whose result couldn’t land, or a session that lost its git credentials. Notifications surface in two places: a bell in the toolbar and pop-up toasts for the important stuff. You don’t need to keep a run open to know when it needs you.

Where Notifications Appear

The Bell

A notification bell sits in the top-right toolbar of your workspace, session, and dashboard. A pulsing dot appears when you have unread items — red when one of them is relevant to the page you’re on. Click it to open the notification center, which groups your notifications into:

Recent — alerts raised in this browser, kept on this device so you can revisit them.
This page — unread notifications for the session you’re looking at, pinned to the top. On a workspace page, that workspace’s own notifications appear in the command bar’s panel instead.
Below those, your most recent notifications (up to 20), newest first, with a count of any older ones.

From the center you can mark items as read, mark everything read at once (Mark all read), dismiss individual notifications, or clear the whole list with Dismiss all — which dismisses every notification, read or unread.

Toasts

High-severity events also pop up as a toast in the top-right corner the moment they happen — errors and warnings get an immediate, glanceable alert without you having to open the bell. Toasts dismiss themselves after a few seconds; the same event stays in the bell so nothing is lost if you look away.

Notifications arrive in real time — there’s no need to refresh to see a new one.

What Notifies You

Notifications are generated for events that genuinely need your eyes:

Kanban results that can’t land. When a Background Runner card’s result hits a merge conflict or stalls before reaching its base branch, you get a warning that opens straight to that card’s PR review.
Deploy approvals — a hosting action that needs your sign-off, or one that was granted automatically.
Session problems. If a session can’t find working git credentials — meaning private-repo access would fail — you get a heads-up with suggestions to fix it. You’re also warned before a session is paused for inactivity, and told when it has been paused.
Account problems, such as a failed payment or a provider credential that stopped renewing and needs you to sign in again.
Inbox messages from your hosted sites (see Inbox notifications).

Clean, no-action-needed outcomes stay quiet by design, so the bell reflects things that actually warrant your attention.

Inline Actions

Some notifications carry action buttons so you can respond right from the notification instead of hunting for the right tile. For example:

A deploy approval offers Approve or Deny (or Review & pay when it involves a purchase).

A notification’s link takes you to the right place — a Kanban landing warning, for example, opens the card’s PR review in its workspace.

Preferences

Open Settings → Notifications to set your preferences. Session Updates controls alerts when a session loses git auth, is about to be paused for inactivity, or has been paused. Turning it off stops those notifications from being delivered at all — they won’t appear in the bell or as toasts. It is on by default, and changes take effect as soon as you save.

Kanban landing warnings, deploy approvals and account alerts are always delivered.

To keep things tidy, repeated alerts for the same session won’t pile up — you’ll see one notification rather than a stream of duplicates.

Background Runner — dispatches Kanban cards and lands their results
Tiles — the building blocks of your workspace