Execution orchestrator and message router for AI agent platforms
mfe_portal | Internal | loading.html
stdio Bus
Acts as a process supervisor and message router between external clients (IDEs, CLIs, services) and worker processes. It handles NDJSON-framed JSON-RPC messages with session-based routing, while remaining completely agnostic to protocol semantics.
Stack Position
stdio Bus operates as a transport layer between external clients (IDEs, CLIs, services) and worker processes. It receives connections via stdio, Unix sockets, or TCP, routes messages to appropriate workers based on session affinity, and returns responses to the originating client. stdio Bus does not interpret message content—it treats all payloads as opaque JSON-RPC envelopes.
Architecture
Loading diagram...
stdio Bus runtime architecture: clients connect via transport layer, messages route to workersstdio Bus Architecture overview showing client connections, daemon components, and worker processes
Key Characteristics
Single-Threaded
Event-driven architecture using epoll (Linux) or kqueue (macOS). No threading complexity.
No External Dependencies
Pure C11 implementation with only libc. No runtime dependencies to manage.
Protocol Agnostic
Routes JSON-RPC messages without understanding MCP, ACP, or any specific protocol semantics.
Session Affinity
Maintains client-to-worker session bindings for stateful interactions.
Backpressure Management
Handles flow control between fast clients and slow workers without message loss.