Notify on run end only for runs marked Notify me
Auto runs no longer alert on failure or success; only notify_mode on does, unless the run_finished setting (now 'Notify when any run ends', default off) opts into every run end. Waiting still notifies auto and on runs. The setting is stored under a new key so a value saved under the old meaning is ignored.
This commit is contained in:
+5
-3
@@ -681,9 +681,11 @@ appear with a `public/` prefix.
|
||||
### Run notification modes and receipts
|
||||
|
||||
`--notify auto|on|off` records `notify_mode` on the run (also returned in
|
||||
summaries and `run_event` frames). Auto retains stage policies and run-level
|
||||
waiting/failure defaults. On also alerts terminal success without requiring a
|
||||
stage hook. Off suppresses stage, run-level system and browser tray alerts.
|
||||
summaries and `run_event` frames). Auto retains stage policies and the
|
||||
run-level waiting alert; its failure or success is silent unless the server's
|
||||
`run_finished` setting ("Notify when any run ends", off by default) is on. On
|
||||
also alerts when the run fails or succeeds, without requiring a stage hook. Off
|
||||
suppresses stage, run-level system and browser tray alerts.
|
||||
|
||||
`inspect --json` / `get_run` includes top-level `notifications` receipts with
|
||||
`sequence`, `event`, `channel`, `status`, `attempts`, and optional `diagnostic`
|
||||
|
||||
+22
-11
@@ -72,16 +72,22 @@ artifacts=markdown,files
|
||||
## Automatic run-attention notifications
|
||||
|
||||
Independently of any `notify` block, the server publishes one run-level
|
||||
notification to the `system` destination when a run needs a person: when it enters
|
||||
`waiting` (a human stage asked for a decision), when it fails, and — while the
|
||||
**Run finished** setting (`run_finished`, on by default) is enabled — when it
|
||||
succeeds (`Run succeeded`). Queued, running, canceled and interrupted runs are
|
||||
silent. The run's own notify mode still wins: a run started with notifications
|
||||
**on** always notifies on success, a run started with notifications **off**
|
||||
never notifies anything, and the default **auto** mode follows `run_finished`
|
||||
for success (waiting/failed always notify). The setting is read in the same
|
||||
transaction that records the run's final state, so a change applies to runs
|
||||
finishing after it. The payload names the run and its pipeline. Run notifications and stage hooks
|
||||
notification to the `system` destination when a run needs a person or ends and
|
||||
was marked to notify. The run's notify mode decides:
|
||||
|
||||
| Run notify mode | Enters `waiting` | Fails / succeeds |
|
||||
| --- | --- | --- |
|
||||
| **on** ("Notify me" in the app, `--notify on` in the CLI) | `Run needs your decision` | `Run failed` / `Run succeeded` |
|
||||
| **auto** (default) | `Run needs your decision` | silent, unless **Notify when any run ends** is on |
|
||||
| **off** ("Silent") | silent | silent |
|
||||
|
||||
Queued, running, canceled and interrupted runs are always silent. The **Notify
|
||||
when any run ends** setting (`run_finished`, off by default) makes every auto
|
||||
run's end notify too; it is read in the same transaction that records the run's
|
||||
final state, so a change applies to runs finishing after it. A stage `notify`
|
||||
block is the pipeline's own opt-in and still publishes for an auto run; when it
|
||||
covers the same event the run-level alert is not sent again.
|
||||
The payload names the run and its pipeline. Run notifications and stage hooks
|
||||
use the configured web run link described below.
|
||||
|
||||
### Open notifications in the web app
|
||||
@@ -170,7 +176,7 @@ explicit `type=ntfy` stages are not affected.
|
||||
|
||||
| Setting | Default | Effect |
|
||||
| --- | --- | --- |
|
||||
| `run_finished` — Run finished | on | an **auto**-mode run that succeeds notifies `Run succeeded` |
|
||||
| `run_finished` — Notify when any run ends | off | every **auto**-mode run that fails or succeeds notifies; otherwise only runs started with **Notify me** (`on`) announce their end |
|
||||
| `chat_needs_you` — Chat needs your answer or approval | on | chat question/form and approval requests notify |
|
||||
| `chat_reply_finished` — Chat reply finished | off | each finished assistant turn in a chat notifies |
|
||||
|
||||
@@ -182,6 +188,11 @@ changes any subset; both reply with type `notification_settings` carrying all
|
||||
three keys. Unknown keys and non-boolean values are refused with an `error`
|
||||
reply and nothing is written.
|
||||
|
||||
`run_finished` changed meaning: it once meant "auto runs announce success" and
|
||||
defaulted on. It is now stored under `notify.any_run_ended`, so a value saved
|
||||
under the old meaning (`notify.run_finished`) is ignored and every server starts
|
||||
from the new default (off).
|
||||
|
||||
## Clearing notifications across devices
|
||||
|
||||
The app's in-app attention state is shared through the server: dismissing an
|
||||
|
||||
Reference in New Issue
Block a user