connections · harness · next

A background agent as an executor. The seat's bars as a rail.

Cursor is the third harness most teams run. Background agents take a ticket and return a PR on Cursor's terms; sleds prices the row first, reads the seat's bars so a 91% seat is not dispatched a two-hour task, and signs what came back so the record reads the same as any other agent.

Cursor · dispatch to a Cursor seat · status · verify
picker · ENG-490 · rework the export api · cursor rows
cursor     Background agent · Sonnet   $5–14 · 68% · seat at 91%
cursor     Background agent · Fable    $12–30 · 74% · crosses before it lands
codex      Dana · Codex CLI            $3–9 · 69% · owns billing · headroom
overnight  batch tier · Sonnet         $2.50–7 · by 6:20 am · ½
what it reads · what it writesnothing replaced on day one

Reads

the seat

Cursor's usage and credits, per person.

the agent

A background agent's run: model, tokens, the PR it opened.

the assignment

Work dispatched from the tracker or from the picker.

Writes

the dispatch

The row, with its band and cap, to a Cursor seat.

the actual

Minutes, model and cost when the PR merges, via the same lines.

the receipt

Signed, across agents Cursor did not run.

where it showswritten by the record

In Cursor, in its own words.

Everything sleds writes into Cursor is something Cursor already knows how to show. If you leave, it keeps the rows.

Next. After the seat reader: Cursor Teams usage, then background agents as a dispatch target with the seat's bars as a constraint.

Every connection →

Nothing replaced on day one.

$curl -fsSL sleds.ai/install | sh
free for one · free for ten · pricing →