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 496f3bd
Browse filesBrowse the repository at this point in the historyBrowse files
feat(acp): report control command outcomes as system rows
Switches the acknowledgement from a kind:9 message to a kind:40099 system
message. A cancelled turn or a rotated session is a lifecycle event, not the
agent speaking, so it belongs in the grey system row beside "X joined the
channel" rather than in the conversation.
The row still lands in the thread the command was typed in: client thread
placement is derived from NIP-10 `e` tags and is kind-agnostic, so the system
message carries the same tags a kind:9 notice did.
Payload is `{type, actor, target}` — `actor` the owner who issued the command,
`target` the agent it acted on — matching every other system message, so both
renderers resolve them to profile names and prefetch their profiles. Six types,
one per outcome, including the two no-ops.
Adds `buzz_sdk::build_system_message` so the NIP-10 tag construction is shared
with `build_message` instead of duplicated in the harness, and cases in both
renderers: an unknown `type` is dropped silently by each, so a client older
than this contract shows no row at all. That is the one regression against the
kind:9 shape, which rendered everywhere.
Reverts the `post_failure_notice` rename from the first commit: the kind:9
helper is failure-only again now that control outcomes have their own path.
Refs #3711
Co-Authored-By: Claude Opus 5 <[email protected]>
Signed-off-by: Bérenger Ouadi <[email protected]>
Copy file name to clipboardExpand all lines: crates/buzz-acp/README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -159,7 +159,9 @@ Use `!cancel` to stop only the current turn; it is a no-op when the channel is i
159
159
160
160
Owner control commands must be kind:9 stream messages from the owner, must mention this agent with a `p` tag, and are consumed by the harness instead of being forwarded to the agent.
161
161
162
-
Because the command never reaches the agent, the harness posts the outcome back into the channel as a kind:9 notice — including when the command was a no-op (`!cancel` with no turn in flight, `!rotate` with no cached session), so a command that changed nothing is distinguishable from one that was never received.
162
+
Because the command never reaches the agent, the harness publishes the outcome back into the channel as a kind:40099 system message — the grey row clients render beside "X joined the channel", since a cancelled turn or a rotated session is a lifecycle event rather than the agent speaking. It lands in the thread the command was typed in, and it is published for the no-op outcomes too (`!cancel` with no turn in flight, `!rotate` with no cached session), so a command that changed nothing stays distinguishable from one that was never received.
163
+
164
+
The payload is `{"type": …, "actor": <owner>, "target": <agent>}`. Clients switch on `type` and silently drop an unknown one, so a client older than this contract shows no row at all.
163
165
164
166
> **Note:** The default mode is `owner-only`. Agents without a registered `agent_owner_pubkey` will not respond to any events until the owner is resolved. Set `--respond-to anyone` to disable the gate entirely.
0 commit comments