connections · harness · openai seat · live

The second seat platform. Same record, same exits.

Codex sessions run through the proxy on the workspace's own OpenAI key, with a provider entry sleds init writes and uninstall removes. Bars and credits are read from the seat; a wall on Codex gets the same menu, and a hand-off from a Claude seat can land on a Codex one through a buddy, metered to the right workspace.

Codex CLI · sleds pickup <id> · sleds defer · sleds status
codex · dana · session 9c1e · hand-off picked up
$ sleds pickup nn75kg2hyr4r
Handed off by jake@ via SLEDS. Pick this up and carry it through.
Where it stands: migration 40 min in · tests not yet run · worth high
…
Seat:      openai · gpt-5.6 · 71% of the weekly bar left · metered to workspace acme
Estimate:  $3–9 · 25–60 min · 69% · recorded est-2f7a
working…
what it reads · what it writesnothing replaced on day one

Reads

the seat

OpenAI bars and credits, the reset.

the session

Model, tokens, cost, the wall, a snapshot at the limit.

the key

The workspace's OpenAI key; batch tier for overnight.

Writes

the provider

A sleds provider in Codex's config; removed by uninstall.

the exits

The same six, in the session.

the record

Rows keyed by seat and platform, never one word for three rails.

where it showswritten by the record

In Codex CLI, in its own words.

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

Next. OpenAI walls with defer and overnight on the batch tier; the second reader for the seat's usage page.

Every connection →

Nothing replaced on day one.

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