You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8601540
Browse filesBrowse the repository at this point in the historyBrowse files
feat(watch): the Watch card + investigate-on-attention (TRI-12820)
The card:
- one universal Watch… entry on run, queue, error and health surfaces; the
panel opens with the card pre-filled with the object's recommended condition
- an ephemeral form/system block: Start watching accepts the recommendation in
one tap; Customize expands condition variant, threshold, window, cadence
(schema-floored) and two independent follow-ups — in-chat delivery is fixed
and inexpressible to disable
- a created watch persists as the confirmation block (four lifetime facts); an
immediate-check answer persists as the one-shot result block, no chip, no
wake; an abandoned card leaves no trace
- every watch intent (report cards, investigation recurrence) opens the card
pre-filled instead of posting a text request
- new run_failed kind (failing is the condition; succeeding makes it
impossible); toast titles and terminal chips render the resolved result —
a failed run never wears a success check; nine-state storybook group
Investigate on attention:
- a watch may carry investigateOnAttention, set only on an explicit ask; on an
attention outcome the wake states the investigation has started and opens it
in the same turn — never on positive/neutral, never without consent, never
delaying or invalidating the wake itself
- the watch row carries the external project ref so a wake-opened investigation
persists under the scope later turns can continue (migration 0008)
- watch-for-recurrence is offered only on concluded cards citing an error
fingerprint, emitting a watch intent that pre-fills the card
There's now a **Watch…** button on runs, queues, errors and the health report. It opens a short form with the right thing to wait for already filled in — a run finishing, a queue clearing, an error coming back, an environment recovering — so one click is enough. Open **Customize** first if you'd rather change how long it waits, how often it checks, or what it waits for, and you can ask for an email as well as the chat message.
Copy file name to clipboardExpand all lines: .server-changes/dashboard-agent-watches.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,4 +3,4 @@ area: webapp
3
3
type: feature
4
4
---
5
5
6
-
Ask the dashboard agent to tell you when something happens — a run starting or finishing, a queue clearing or growing past a number you pick, an error coming back, an environment recovering — and it messages you in the chat once with the answer. It tells you either way: that the run finished, that it failed, or that the queue still hadn't cleared by the time it stopped looking. If the thing you asked about has already happened, it just says so instead of waiting. Each chat can wait on up to three things at a time, for up to 24 hours.
6
+
Ask the dashboard agent to tell you when something happens — a run starting or finishing, a queue clearing or growing past a number you pick, an error coming back, an environment recovering — and it messages you in the chat once with the answer. It tells you either way: that the run finished, that it failed, or that the queue still hadn't cleared by the time it stopped looking. If the thing you asked about has already happened, it just says so instead of waiting. Each chat can wait on up to three things at a time, for up to 24 hours. You can also ask it to start looking into the cause if the news turns out to be bad, and it will — otherwise it just tells you and stops.
0 commit comments