Skip to content

The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.

3.7 KB
Raw Blame

Provider Protocol

Make your agent platform available on the Autonomous Harness. A user connects it with a URL and a credential, then drives it from the web app or from the hardware device on their desk.

Authenticate, call a method, handle the response. JSON-RPC 2.0 over HTTPS to one URL, with Server-Sent Events for the one method that streams. Eight methods, no SDK, nothing to discover, and no capability negotiation — if you can serve JSON over HTTPS, you can implement this in an afternoon.

spec/ The contract — one page
spec/onboarding.md What to do once you conform, and what to expect from us
reference-provider/ Scripted and deterministic — and it ships the conformance runner
example-provider/ A real one, backed by the Claude Code CLI

Quick start

See it work before reading the spec:

cd reference-provider && npm install && npm run dev     # http://127.0.0.1:4319
curl -H 'Authorization: Bearer any-key' -H 'content-type: application/json' \
     -d '{"jsonrpc":"2.0","id":1,"method":"agent.list","params":{}}' localhost:4319

Then point the runner at your own endpoint. Zero failures is the bar:

npm run conformance -- --url https://your-endpoint --key <credential>

Every line names a rule, so a red result points at something specific rather than at a symptom:

✔ terminal-frame           Every stream ends with EXACTLY ONE terminal event
✖ history-matches-stream   History returns the SAME event objects the stream emitted
             history and the live stream disagree about the same events

What you actually have to implement

Eight methods. All of them are required, and that is the whole surface:

Backs
agent.list the agents a user picks from — authenticated, so it can differ per tenant
agent.send → SSE a turn
agent.history rebuilding the conversation
turn.cancel stopping a turn
agent.create / agent.rename / agent.delete managing the agent list
agent.recap short per-turn summaries the hardware device shows

History is required, not optional: Autonomous stores no transcript for a provider machine. Without it, a page refresh loses the conversation.

"Required" does not mean "pretend". If your agents are managed inside your own product, answer invalid_request with a message instead of faking a mutation — we show that message to the user ("Agents are managed in Example Co"), which tells them more than a control that silently vanished. A provider that summarises nothing answers agent.recap with an empty list, and we derive one from the turn's own text.

What is in this section

spec/                 the contract + JSON Schemas
reference-provider/   zero runtime dependencies — readable end to end
example-provider/     a real agent; runs Claude with permissions skipped ⚠ read its README first

Both packages are plain TypeScript with no runtime dependencies — Node ≥ 20, or ≥ 20.12 for example-provider, which reads its .env with the platform's own process.loadEnvFile rather than take a dependency on one. That is on purpose: you should be able to read reference-provider/src/server.ts and know exactly what your own endpoint has to do.

Contributing, security, licence