Protocol
Mission Control Agent Protocol 1.0
A vendor-neutral, signed HTTPS protocol for identity, heartbeat, pull assignments, leases, progress, artifacts, completion, failure, and cancellation.
Authentication
HMAC-SHA256 binds method, path, timestamp, nonce, message ID, body checksum, and protocol version. Credentials are workspace- and agent-scoped, displayed once, immediately revocable, and never included in events or examples.
Pull and leases
A bounded long poll returns only the authenticated agent’s eligible assignment. An opaque lease token is required for acknowledgement, renewal, execution messages, cancellation checks, release, artifacts, and completion.
Compatibility
Protocol additions preserve existing push-mode 1.0 agents. Independent Python, Go, or Rust clients can implement the documented canonical signature and JSON envelope without using Mission Control source code.