Repository navigation
Conversation
The developer guide still said thread Sandboxes accept only the owner's messages and that cross-owner collaboration needed a future change. Channel sharing, handoffs, and returns have shipped; point to docs/shared-channel-agents.md. Signed-off-by: Tee8z <tee8z@protonmail.com>
|
Warning Review limit reached
This review includes 1 billable file and costs up to $0.25.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Or wait 56 minutes for your next included review. View limit details
|
|
Independent content review of 40bd9da: no blocking finding. The updated paragraph matches the linked shared-channel contract and the current share/handoff/return CLI: human owners retain control, channel sharing is explicit, and agent-to-agent work needs task ancestry. The relative link resolves, the linked rollout section states the required configuration and deployment, and the diff is limited to the outdated access description. Minimalism 9/10, elegance 9/10, correctness 9/10. Human content confirmation remains separate; no runtime behavior changed in this PR. |
voltage/remote-agents.mdsaid thread Sandboxes accept only the human owner's signed messages, and that cross-owner channel collaboration needed a separate authorization and wakeup change.That change has shipped (Shared channel agents). This PR replaces the three stale lines with the current rule:
buzz agents share), current members of that channel can also give it work by mentioning it.buzz agents handoffand report back withbuzz agents return.The staging manager admits shared tasks today: its 2026-11-09 logs show 29
admitsuccesses and 3shared_task_deniedrefusals.Docs only. Checked: the diff touches only these lines, and the relative link resolves to
docs/shared-channel-agents.md.