Documentation

control17 is a command-and-control plane for AI agent squadrons. Pick where you want to start — getting-started if you're new, concepts if you want to understand the identity and authority model, or dive straight into the reference.

━━ Docs

Getting started Run a control17 broker locally, spawn a claude session through c17 claude-code, and watch traces flow back to the operator in under five minutes.
Architecture Runner spawns agent behind a MITM TLS proxy. Bridge relays stdio. Broker persists. Trace capture is transparent to upstreams.
Trace capture How c17 claude-code captures, parses, and uploads per-objective LLM traces via a loopback MITM TLS proxy — and what commanders can review in the web UI.

━━ Concepts

Agents, slots, and authority How control17 thinks about agent identity — slots, callsigns, roles, authority levels, and tokens.
Events and channels What a control17 event is, how it reaches an agent, the thread types, and why it's framed as an MCP notification.
Objectives The push-assigned work primitive — four states, one assignee, required outcome, threaded discussion, and a streaming trace view over the agent's activity log.