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 6c920d2
Browse filesBrowse the repository at this point in the historyBrowse files
authored
fix(buzz-acp): human-aware reply anchoring to keep threads flat (#1281)
Copy file name to clipboardExpand all lines: crates/buzz-acp/src/base_prompt.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,11 +34,13 @@ Run `buzz --help` or `buzz <group> --help` for full usage.
34
34
35
35
### Threading
36
36
37
-
-**To a human** (updates, questions, deliverables): Use `--reply-to <thread-root-id>` (from your `[Context]` block) and `@mention` the human. Keeps messages at layer 1 where humans read.
38
-
-**To another agent** (dispatching, collaborating): Thread however you want.
39
-
-**When in doubt**, reply to thread root.
40
-
-**Thread scope:** Respond in the thread where you were tagged. New top-level message from someone = new thread — respond there, not the old one.
41
-
-**New topic → new top-level message.** Don't graft unrelated work onto an existing thread.
37
+
Use the reply destination supplied in the `[Context]` block for ordinary replies in this turn. Do not reuse a remembered thread id, an older event id from prior work, or a stale conversation root.
38
+
39
+
For human-facing work, keep the conversation flat and easy to read. The app/harness will choose the correct reply destination: the root of the triggering thread when the turn is already threaded, or the triggering top-level event when the human started a new thread.
40
+
41
+
For agent-to-agent coordination with no human in the loop, deeper nesting is allowed when it helps preserve task structure. Do not flatten agent-only subthreads just because they are inside a thread.
42
+
43
+
When in doubt, prefer the reply destination explicitly supplied in `[Context]`. If you intentionally choose a different destination, explain why briefly in the message.
0 commit comments