bamboo-broker — a standalone network message broker for sub-agent
ask/reply (and future task/handoff) traffic.
The broker fronts durable per-session Mailbox
queues with a WebSocket bus, so a central orchestrator and its workers —
local subprocesses, local Docker containers, or SSH/remote hosts — exchange
messages over the network with durability and at-least-once delivery, without
sharing a filesystem.
Topology: a single central broker (hub-and-spoke). It is a pure message
bus — it routes messages, it does not spawn actors or coordinate with other
brokers. Spawning the PUSH-side workers lives in [deploy] (the Deployer
family: local / docker / ssh / russh). (The bamboo_subagent::WorkerLauncher
trait that earlier docs referenced was never wired and has been removed; the
PULL-side actor runner dispatches placement inline.)
Layers:
- [
proto] — the client↔broker wire frames. - [
core] — [BrokerCore], the transport-agnostic routing engine (tested in-process). - the WebSocket server + auth +
bamboo broker servewiring layer on top (added next).