Harness plane / 001Build · Connect · Operate

Any harness.One plane.

Build or bring the agent harness that fits the work. Rivetplane gives it a common ACP connection, remote API and MCP surface, and one place to operate every session.

Create an accountAPI documentation
01 / MODULAR

Build your way

Choose the models, tools, memory, permissions, and runtime that fit the job.

02 / OPEN

Connect through ACP

Give different harnesses one protocol and one stable control surface.

03 / CONTROL

Operate every run

Use REST, live events, and MCP over the same session state.

04 / LOCAL

Keep authority local

The runner dials out. Code, credentials, and permissions stay on the machine.

02 / COMMON PLANE

Build the harness.
Control the run.

Rivetplane is not one fixed harness. It is the shared control layer for harnesses you build or already use. The agent loop and permission authority stay with each local harness.

01 — ACP CONTRACT

Bring any compatible harness

Connect different runners through one open session protocol.

02 — HUMAN INPUT

Questions and approvals

Bind each response to an exact pending ID.

03 — LIVE CONTEXT

Transcripts that stream

Tail messages, tool calls, results, and state changes.

04 — MODEL ROSTER

Create with the right model

Select an explicit model reported by that runner.

03 / API

Read state.
Act deliberately.

REST and MCP use the same authenticated operations and session state. There is no private UI-only control path.

HTTP / MCP

Small surface.
Exact semantics.

List the fleet, load a transcript, inspect the active pending request, then send a message or exact response.

Open API documentation
GET /v1/sessions?status=waiting_approval

GET /v1/sessions/{id}/pending

POST /v1/sessions/{id}/pending/respond
{
  "pending_id": "per_01J...",
  "response": "approve",
  "scope": "once"
}
04 / SECURITY BOUNDARY

Remote control.
Not a remote shell.

The server never opens a connection into a workstation. Model keys, Git credentials, and source files remain local unless a transcript payload explicitly contains them.

01 — Client-initiated outbound WSS
02 — Machine- and account-scoped tokens
03 — Harness-enforced permissions
04 — Exact approval IDs and audit logs
05 — Payload summaries by default
05 / PRICING

Free through
the Alpha.

Use hosted Rivetplane at no cost while the product is in Alpha. Model and harness-provider charges remain with your existing providers.

01 / ALPHA

For harness builders and early teams

$0 / during Alpha
  • Hosted Rivetplane server
  • Unlimited connected runners
  • REST, WebSocket, and MCP
  • Alpha feedback channel
Join the Alpha
02 / ENTERPRISE

For private and managed rollouts

Contact
  • Private deployment options
  • Custom security and retention
  • SSO and organization controls
  • Direct implementation support
Contact us
06 / START LOCAL

Build any harness.
Run it your way.

Create an accountView docs