multi-bot-desk-orchestrator
Orchestrate multi-bot agent teams with per-bot serial turn queues, bounded hop-depth guards, in-band MCP tool approvals, and isolated display/gateway leases. Do not use for single-bot stateless chat or raw VNC tunneling.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- multi-bot-desk-orchestrator
- description
- Orchestrate multi-bot agent teams with per-bot serial turn queues, bounded hop-depth guards, in-band MCP tool approvals, and isolated display/gateway leases. Do not use for single-bot stateless chat or raw VNC tunneling.
02 资源文件 3
- 参考文档CARD.md2.1 KB
- 参考文档config.default.yaml214 B
- 脚本scripts/multi_bot_desk_engine.py1.7 KB
03 SKILL.md 正文
Multi-Bot Desk Orchestrator
multi-bot-desk-orchestrator distills the multi-agent desktop orchestration architecture from bot-hq. It governs how multiple persistent bots collaborate on a shared host without colliding on browsers, corrupting primary agent configs, entering infinite bot-to-bot loops, or bypassing human tool approvals.
See CARD.md for the companion summary card and mandatory invariants checklist.
Consult config.default.yaml for baseline operational budgets and ../agent-harness-architect/SKILL.md for harness isolation design.
1. Per-Bot Serial Queue & Hop-Depth Guard
Serialize turns per bot_id and bound multi-bot chatter:
- Serial Turn Queue: Execute one turn per bot at a time so browser/desktop state never races.
- Hop-Depth Cap: Track
current_depthacrosssend_to_botrelays and reject dispatches oncecurrent_depth >= max_depth(default3). - Room Fan-Out Bound: In group rooms, route to
@mentionedmembers or cap unmentioned broadcasts at 3 members.
Completion criterion:
BotHopDispatchOutcomereturned with boundednext_depthandtarget_bot_ids.
2. In-Band MCP Approval Gate
Enforce human-in-the-loop safety inside the MCP tool endpoint:
- Read-Only Fast Path: Read-only tools and explicitly
always_allowed_toolsexecute immediately (auto_allow). - Blocking Write Card: Mutating tools suspend the turn (
require_approval) until the user approves or refuses. - User Interrupt Supersession: A new user message immediately supersedes pending approval cards as
skipped.
Completion criterion:
McpApprovalOutcomeclassifies every tool call without engine-specific forks.
3. Primary-vs-Managed Home & Screen Isolation
Isolate managed bots while preserving the host's primary agent:
- Primary Non-Interference: Never restart, stop, or rewrite the primary bot's config (
mutates_primary_config = False). - Dedicated Resource Leases: Assign each managed bot a unique
display_index(1–3),gateway_port(8650 + slot), andcdp_port(9200 + slot).
Completion criterion:
BotDeskLeaseallocated with zero port or display collisions.
The Three Foundational Pillars
1. Bounded Multi-Bot Collaboration
Cap bot-to-bot hops at 3 and room fan-outs at 3 so teams collaborate without runaway ping-pong loops.
2. In-Band MCP Safety Boundary
Gate mutating tools inside the MCP endpoint so every channel and engine shares one approval contract.
3. Non-Destructive Primary Coexistence
Run managed bots in isolated homes, ports, and displays without mutating the primary host agent.
Anti-Patterns
- Unbounded Bot Ping-Pong — Allowing
send_to_botrelays without a strictmax_depthceiling, causing infinite turn loops. - Shared Browser Helper Collision — Launching multiple managed bots against the same
BH_HOMEor Chrome DevTools port. - Primary Config Clobbering — Restarting or overwriting the host's primary agent
config.yamlwhen adding companion bots. - Stale Approval Deadlock — Leaving a pending tool approval card active after the user has already sent a new message or interrupted the turn.
04 同仓库更多 Skills
ui-behavior-primitive-architect
Architect, audit, and verify zero-dependency headless UI behavior primitives, WebMCP agent bridges, WAI-ARIA/SSR/RTL tri-modal checks, and framework expert routing. Do not use for static CSS theme styling or backend database migrations.
trustgraph-ontology-governor
Govern knowledge graphs, SHACL-AF triple policies, OntologyRAG subclass validation, PROV-O dual named graphs, and Laya entropy decision scoring. Do not use for relational SQL queries or generic web scraping.
shim-harness-governor
Govern universal CLI agent loops, 4-tier tool permissions, ancestor-symlink workspace sandboxes, deterministic-first command routing, collision-safe MCP namespacing, and layered skill loading. Do not use for static UI styling or external SQL analytics.
graphiti-zep-memory-governor
Govern bi-temporal knowledge graphs with Graphiti future-edge clamping, MinHash/LSH entity dedup, RRF/MMR reranking, and Zep typed ontologies. Do not use for static SQL joins or generic web crawling.
agora-mcp-workbench-architect
Architect, audit, and orchestrate Agora Workbench MCP servers, loopback sidecars, unified state graphs, gateway/dispatcher connectors, and policy-enforced data lakes. Do not use for static frontend CSS styling or non-MCP desktop GUI automation.
skill-eval-assurance-runner
Evaluate and assure agent skills using small-N Wilson confidence intervals, unbiased pass^k reliability, deterministic trajectory graders, preflight boundary honesty, and sealed digest verification. Do not use for subjective prose review or unconstrained production deployment.