Polychrome

Build your own anything. Polychrome runs agent conversations — the kind where a model calls tools and takes real actions in a loop. Each conversation gets its own isolated sandbox, so an agent can research, evaluate, and execute without reaching anything you didn't give it — on one machine or across a cluster.

Every surface is an edge. Chat, web, code-forge bots, email, cron, even other agents: each is a small adapter over the same public API — a chat-completions-compatible HTTP route backed by a streaming Connect RPC. Adding a surface means writing an adapter, never forking the core.

Every turn leaves a record you can replay. Two planes run every conversation: the control plane owns the public API, the Kubernetes reconciler, and a durable, signed event log — the source of truth for what the agent did. The execution plane runs one sandbox per conversation, and human-in-the-loop approvals pause a turn until someone decides. Backends, tools, and tenants swap behind Rust traits, so the orchestration core never changes.

Start here

• Edges, ingress, and clients — the one API, the adapter contract, and the edge patterns anything rides on.
• Architecture — control plane, execution plane, and the durable event log.
• Personas — durable principals, caller attribution, and memory that follows the human.
• Payments — link a wallet with a passkey, let an agent pay from it, and the safety model behind it.
• Trust — how every tool call is contained: capabilities, outside content, escalation, and recovery.
• Run and Deploy — local two-process setup and the Kubernetes overlays.
• Operator CLI — cluster lifecycle, introspection, and driving turns.