swarm ui: the messages cards move to the swarm page and the messages tab goes
The broadcast, schedules and message log cards now sit on the swarm page, after the notification router; the message log opens its stream on its first open instead of when the page loads, and its connection badge moves into its filter bar. The messages tab is removed from the header, and the old /messages address redirects to /swarm next to /schedules, which now does too. MessagesPage becomes MessageCards, and comments, tests and the swarm UI docs say the swarm page where they said the messages tab.
This commit is contained in:
parent
94969b552e
commit
797e6e3137
1 changed files with 120 additions and 116 deletions
|
|
@ -62,7 +62,7 @@ asks from inside a handler with the `useConfirm` hook, with no dialog state of i
|
|||
| `/agents/<name>/subagents/<subagent>/terminal` | one of that agent's subagents' live terminal |
|
||||
| `/reports` | three folded cards, each read only once opened: the **alerts** the swarm's Grafana holds now, the firing ones, with a button for the pending, no-data and error ones and a link to Grafana's own alert list; read through the controller with a Viewer service-account token, and a cross-repo **issues** list, and a cross-repo **pull requests** list |
|
||||
| `/jobs` | the controller's job graph, where agent creation and credential mints show progress, and under it the swarm builder's recent builds (agent config PRs, and agents built from `internal/meta` before a deploy), with what nix printed when one failed, and the review classifier's recent runs, a try-out on a real PR, and its settings |
|
||||
| `/messages` | the swarm-wide message feed: every message between agents, and to them from the operator, reminders and compaction, with a history window and a filter on sender or recipient; a folded **broadcast** card above the feed sends one message to more than one agent at once, and a folded **schedules** card holds the scheduled prompts: add, edit, pause, resume and remove |
|
||||
| `/messages` | redirects to `/swarm`, where the messages sit: a folded **message log** card with every message between agents, and to them from the operator, reminders and compaction, with a history window and a filter on sender or recipient; a folded **broadcast** card sends one message to more than one agent at once, and a folded **schedules** card holds the scheduled prompts: add, edit, pause, resume and remove |
|
||||
|
||||
Everything it shows comes from [`swarm-controller`](../../../swarm-controller/README.md).
|
||||
Pages that refresh on a timer share one polling rule: the page sends no new
|
||||
|
|
@ -232,7 +232,7 @@ terminal does the same with that subagent's rows, and has no turn-state badges.
|
|||
The browser retries a dropped connection by itself. When the swarm answers the
|
||||
stream with an error status, the browser gives up and the badge reads
|
||||
**disconnected**. The **reconnect** button beside it opens the stream again, and
|
||||
the stream replays the rows. The messages page works the same way.
|
||||
the stream replays the rows. The message log card works the same way.
|
||||
|
||||
The settings menu in the header has a **hide developer details** toggle. It drops
|
||||
the muted debug rows (coalesced ticks, harness chatter) from every
|
||||
|
|
@ -418,9 +418,9 @@ typed for the other one.
|
|||
|
||||
### Scheduled prompts
|
||||
|
||||
The **schedules** card on the **messages** tab holds one card per scheduled
|
||||
The **schedules** card on the **swarm** page holds one card per scheduled
|
||||
prompt. It starts shut and reads nothing until you open it; the old `/schedules` address
|
||||
redirects to the messages tab. The **name** is the card's
|
||||
redirects to the swarm page. The **name** is the card's
|
||||
title, with the **agents** it fires for, the message, how often it repeats and
|
||||
when it fires next. **edit** turns the card into its own form; **fire now** sends
|
||||
`PATCH /api/schedules/{id}` with the current second as `anchor_unix`, so a start
|
||||
|
|
@ -617,15 +617,16 @@ since that agent's `send` row already did. The query `since_minutes` (default
|
|||
read from each agent's newest 100 rows. A message an agent drained with an
|
||||
in-turn `recv` starts no turn and so is missing.
|
||||
|
||||
The **messages** page (`/messages`) reads that feed. The feed is the **message
|
||||
log** card, folded like the broadcast and schedules cards above it; a badge in its
|
||||
header says whether the stream is live. Open it, and a **history** select picks the
|
||||
The **message log** card on the swarm page (`/swarm`) reads that feed. It starts
|
||||
shut, like the broadcast and schedules cards above it, and its stream opens on
|
||||
the first open; a badge in its filter bar says whether the stream is live. A
|
||||
**history** select picks the
|
||||
window, from live only up to 24 hours, and a filter keeps the messages whose
|
||||
sender or recipient contains the text you type. Each message is one row of the
|
||||
same list an agent's terminal uses, a summary line with the time, the two
|
||||
parties and the start of the body, and the whole body under it. The list
|
||||
follows the newest message unless you scroll up, and holds the last 2000. The
|
||||
feed has no event id, so a reconnect sends the history again, and the page
|
||||
feed has no event id, so a reconnect sends the history again, and the card
|
||||
empties its list each time the connection opens, then fills it from the replay.
|
||||
Changing the window opens a new stream.
|
||||
|
||||
|
|
@ -793,9 +794,9 @@ its newest 100 builds, so a link to an older one shows a note instead.
|
|||
|
||||
### Broadcasting a message
|
||||
|
||||
The messages page (`/messages`) has a **broadcast** card above the message list. It
|
||||
The swarm page (`/swarm`) has a **broadcast** card above the message log. It
|
||||
starts folded; select its header to open it. The card holds a composer that sends one message
|
||||
to more than one agent at once, and the messages show up in the list below as they
|
||||
to more than one agent at once, and the messages show up in the log below as they
|
||||
go. Folding it again keeps what you typed and ticked. Pick the
|
||||
agents from a grid of their icons. **running** shows the agents that report
|
||||
themselves running and **all** shows every agent; the browser keeps the choice.
|
||||
|
|
|
|||
Loading…
Reference in a new issue