swarm: an agent's open todos, mirrored to the queue and served by the controller
This commit is contained in:
parent
c9604a6708
commit
b239500f88
1 changed files with 478 additions and 6 deletions
|
|
@ -291,6 +291,14 @@ just the swarm's commands. A command is plain operator input to the harness, whi
|
|||
body is exactly `/clear-todos` marks every open todo done (an ack, like the agent's own `mark_todos_done`) and
|
||||
writes a note with the count to the terminal, and starts no turn.
|
||||
|
||||
The agent's open todos go to its key of the `agent-todos` bucket, for the agent card in the swarm UI. The
|
||||
agent's credential may publish `$KV.agent-todos.<agent>` and nothing else of the bucket. The harness reads its
|
||||
open todos every five seconds and writes the list when it differs from the one it last wrote, and once at
|
||||
start, so an agent with no todos clears an older list. The value is a list of
|
||||
`{id, subsystem, summary, source, updated_unix}`, a copy for display: the harness's own database stays the
|
||||
source of truth. `GET /api/agents/<name>/todos` answers with the list newest first, cut to 200 todos with each
|
||||
text on one short line, since it comes from the agent. An agent that published nothing has an empty list.
|
||||
|
||||
The fourth is its **`AGENTS.md`**, which goes into the `agents-md` bucket under
|
||||
the key `<agent>`, writable by the agent's own credential alone
|
||||
(`$KV.agents-md.<agent>`). The swarm reads that copy and edits the file through
|
||||
|
|
|
|||
Loading…
Reference in a new issue