Skip to main content

​
Overview

Agents run on their own once you’ve sent them off, and the useful ones take a while. Notifications tell you the moment an agent needs you back, so you can start something else instead of watching a chat window. You get notified about three things:

Needs your input

The agent asked a question or is waiting for you to approve an action, and can’t continue until you answer.

Proposed a plan

The agent has written up how it intends to tackle something and wants your sign-off.

Finished a run

The agent completed its work, or stopped because it hit an error.
This covers every agent you work with: Starcat, Starcat Developer, workspaces, and conversation forks.

​
Turning them on

Notifications are off until you ask for them.
1

Open your preferences

Click your name at the bottom of the sidebar, choose Account Settings, then Preferences.
2

Switch on Browser notifications

Your browser will ask for permission. You have to allow it — the setting can’t grant permission on your browser’s behalf.
3

Repeat on each browser you use

Permission is granted per browser, not per account. Turning notifications on at your desk doesn’t turn them on for your laptop.
If the toggle is on but you’re not receiving anything, the browser is probably blocking notifications for this site. Your preferences page will say so, and you can re-allow them in your browser’s site settings.

​
When you’ll actually be interrupted

Notifications are meant to be useful, not noisy, so a few rules apply.
  • You won’t be told about the conversation you’re already reading. If the tab is open, focused, and showing that exact chat, nothing pops up — you can see it happen.
  • You will be told about everything else. Working in one app while an agent finishes in another still notifies you.
  • You won’t be told about runs you stopped. Pressing stop is you deciding the run is over.
  • Notifications about the same conversation replace each other, so a long-running agent won’t stack up a pile of alerts.
The sound is whatever your operating system uses for notifications — Stardeck doesn’t add its own, and you can silence it in your OS notification settings.

​
When your browser is closed

You’ll still get notified. Agent runs keep going on our side whether or not you have Stardeck open, so notifications are delivered to your browser even when there’s no tab running — the same way any other site’s notifications reach you.
On iPhone and iPad, notifications only work if you’ve added Stardeck to your home screen. See Add to Home Screen.

​
Activity

Every notification is also recorded in your Activity feed, whether or not browser notifications are switched on. The toggle controls whether you get interrupted — not whether things get tracked. Find it under Account Settings → Activity, or click the bell at the bottom of the sidebar. The bell shows a count of anything you haven’t read yet. From the feed you can:
  • See what each agent did and when
  • Click any item to jump straight to that conversation
  • Mark everything as read at once
Read items are kept for 90 days. Anything still unread stays until you read it.

​
Who gets notified

Whoever sent the message that started the run. Notifications follow the person who asked for the work, so a shared workspace won’t alert everyone in it every time one person runs an agent.

​
Troubleshooting

Permission lives with your browser, not your Stardeck account. Check your browser’s site settings for stardeck.ai and make sure notifications are allowed — then reload the page.
That’s expected. Switch the toggle on again from the browser that’s missing them, and allow the permission prompt there.
Some browsers suspend tabs that have been in the background for a long time. Your Activity feed will still have everything, and the notification will arrive once the tab wakes up.
Switch the toggle off. The Activity feed and the bell keep working — only the operating-system notifications stop.