TalentOS Help
Settings & notifications

Get notified when work finishes

Turn on browser notifications for finished work, read the bell for things that need you, and choose the right channel for long running tasks.

Long jobs are the point of having a Talent, and staring at a spinner is not. TalentOS gives you three different signals, each for a different situation.

Ping this device when a turn finishes

The bell icon in the chat header opts this browser on this device into a notification when your Talent finishes what it is doing.

  1. Open your Talent in the browser.
  2. Click the bell in the chat header.
  3. Accept your browser's permission prompt when it appears.
  4. The icon changes to show notifications are on.

Ask for something slow, switch to another tab, and you get a system notification the moment it is done.

This is per device and per browser. Turning it on at your desk does not turn it on for your laptop or your phone. Turn it on again wherever you want to be pinged.

The bell in the top bar

The bell in the app header is a bounded inbox for things that need a decision, not a history feed. It surfaces items such as:

  • an action your Talent is waiting for you to approve
  • a Skill or Routine version submitted for your review, or changes requested on yours
  • comments addressed to you
  • "Private login needed" when your Talent hit something only you can sign in to
  • "Memory is full" when your active memory pages have hit their ceiling
  • "Workspace credits are running low"

Clear it by acting on the items, not by scrolling it. For the durable record of everything that ran, use Activity instead.

Let the work come to you in a messaging channel

If you would rather not watch the browser at all, ask for the work in the channel you already live in. Your Talent answers where you asked, so a Routine set up from team chat reports back there, and quick approvals can be answered with a tap without opening the console.

A worked example

An agency producer asks their Talent for a competitive teardown that will take several minutes, clicks the chat header bell, accepts the browser prompt, and goes back to email. Six minutes later the notification arrives and the Artifact is waiting. The next day they set the same job up as a weekly Routine and point it at team chat, so Monday's teardown arrives without anyone watching the app.

What to check

  • The bell is not in the chat header. Your browser does not support web push. Use a connected messaging channel instead.
  • The bell shows as blocked. You previously denied notifications for this site. Only your browser settings can undo that; re-allow notifications for the site, then click the bell again.
  • You allowed notifications but nothing arrives. Check that your operating system is not in a focus or do-not-disturb mode, and confirm you enabled it on the device you are actually watching.
  • You are getting nothing anywhere. Confirm the work actually ran. Open Settings, Activity and look at Failed.
  • The header bell never empties. Some items need a decision from you and stay until you make it. Expired approvals stay visible on purpose, because a stalled run is something you need to know about.

On this page