# Notifications - Obss

Set up
Notifications
Read Obss notices in the header inbox, and choose Email and In-app delivery for each kind of notice from the dashboard, the CLI, or the plugin.
Obss notifies you when an experiment finishes, a schedule needs you, a connection breaks, or your run balance changes, in the dashboard inbox and by email. Choosing your notifications is step 8 of the
setup checklist
.
Read notifications
Select the
Notifications
bell in the dashboard header. The inbox shows the current project’s notices and organization-wide ones, such as run balance and provider changes.
Dashboard
CLI
Plugin (MCP)
Select a notice to open what it’s about.
Select
See all notifications
to open the
Notifications
page, with
All
and
Unread
tabs.
Select
Mark all as read
when you’re done.
obss
notifications
list
--status
unread
obss
notifications
acknowledge
--all
acknowledge --all
marks up to
--limit
notices as read, so repeat it while
hasMore
is true. Pass
--id
to mark one notice (
obss notifications list
).
Ask your AI assistant what needs your attention. It calls
List notifications
(
list_notifications
), and
Mark notifications as read
(
acknowledge_notifications
) when you’re done.
Choose your notification preferences
Your preferences on
Profile → Notifications
apply in every organization you belong to. For most kinds of notice, you turn
Email
and
In-app
on or off separately.
Preference
Covers
Channels you can change
Experiment updates
Your experiments and schedules
Email, In-app
Billing and runs
Your plan and run balance
Email, In-app
Connections and model providers
Sign-ins and model lists
Email, In-app
Product news and marketing
Product updates, tips, and offers
Email only (In-app shows
Not used
)
Account and sign-in
Welcome messages and sign-in help
None (
Required
)
Operational alerts
Deletions you started
None (
Required
)
You get a notice when:
Experiment updates:
an experiment you launched or joined completes, has incomplete results, or stops with an error. These notices, such as
Experiment completed
, show who launched the experiment and the run balance. You also get one when a schedule you own pauses, skips three launches in a row, is short of runs, or is deleted with its experiment.
Billing and runs:
a plan starts, renews, or changes; runs are added, refunded, or disputed; a plan payment is due; or few or no runs remain.
Connections and model providers:
an MCP server or personal provider connection needs a new sign-in, a provider adds or removes models, or a model refresh fails. Model list changes show only in the app.
Operational alerts:
a deletion you started doesn’t start or needs attention.
Dashboard
CLI
Plugin (MCP)
Open
Profile → Notifications
.
Turn
Email
or
In-app
on or off for each preference.
obss
notifications
preferences
obss
notifications
preferences
update
--patch
'{"experiment-updates":{"email":false,"in-app":true}}'
The keys are
experiment-updates
,
billing-updates
,
connection-alerts
, and
product-marketing
. Set
email
and
in-app
separately.
product-marketing
takes
email
only (
obss notifications preferences update
).
Ask your AI assistant to change your notifications. It calls
Get notification preferences
(
inspect_notification_preferences
), then
Change notification preferences
(
manage_notification_preferences
).
Stop emailing me about experiment updates, but keep them in the app.
Schedule notices
Schedule notices follow
Experiment updates
. A notice that a schedule paused, is skipping launches, or is short of runs names the schedule in its title, such as
Schedule paused: Nightly checkout
, and the email names it beside the project.
Because a schedule can launch many times a day, Obss limits its notices:
A scheduled experiment that finishes without problems sends no notice.
One with problems, such as errors or failed Evals, sends an in-app notice.
Email sends at most one of these a day for each schedule.
An experiment you start with
Launch now
, or any other way, sends the usual notices (
Schedules
). In the CLI and the plugin, schedule notices and the problem notices of scheduled experiments carry a
scheduleId
for
obss schedules get
or
get_schedule
.
From the CLI and the plugin
Task
CLI
Plugin (MCP)
List notifications
obss notifications list
list_notifications
Mark notifications as read
obss notifications acknowledge
acknowledge_notifications
Read preferences
obss notifications preferences
inspect_notification_preferences
Change preferences
obss notifications preferences update
manage_notification_preferences
A notice that needs a payment or a sign-in links to the dashboard, where those steps happen.
Next steps
Set up your organization
Step 9: invite your teammates.
Install the Obss Plugin
Operate Obss from your AI assistant.
Tasks and rubrics
Write your first task and rubric.
Quickstart
Launch your first experiment.
Profile
Obss Plugin (MCP)
Powered by
This documentation is built and hosted on Mintlify, a developer documentation platform