Private beta · Built for Codex users
Connect your local Codex to a trusted provider machine when you need more capacity, then track exactly what you borrowed or lent. Your repository stays local. Their OAuth credentials stay put.
~/acme/checkout
$ codex
✦ Ready. What are we building?
› finish the subscription migration
Weekly capacity unavailable on this account.
✦ Picking up in the same local workspace…
✓ Updated billing migration
✓ Tests passing
›
Two sides. One local-first relay.
CodexShare keeps execution where it belongs. The consumer keeps their workspace, shell, approvals, skills, and MCP. The provider contributes only model capacity through a revocable local daemon.
For consumers
Pair once, launch the official Codex CLI, and keep every tool call inside your local environment.
codex-connect --share "codexshare://HOST:PORT/connect/CODE"For providers
Start a time-boxed daemon, send a one-use link, then watch devices, sessions, and token flow in real time.
Local usage ledger
Every completed Responses stream updates a private local ledger. Inspect sessions, requests, failures, traffic, and input/output tokens for any time window.
codex-share --usage --days 30The hosted console uses demo data today. The CLI ledger is real and remains on your machine.
Capacity moves. Control does not.
CodexShare is not a system-wide proxy. It accepts only the Codex Responses model surface, strips sensitive headers, and injects provider authentication at the last hop.
Access tokens, refresh tokens, and account identifiers never enter the pairing file or consumer environment.
Product logs contain lifecycle and metering metadata, not prompt or response bodies. Sensitive fields are redacted.
The provider terminates the relay and could inspect traffic if modified. Pair only with people or teams you trust.
Deliberately narrow first release
P0 records usage only. The withdrawal interface is visible so the product model is clear, but there is no calculated balance, payout, wallet, or settlement behind it yet.
Per-session requests, failures, bytes, input tokens, and output tokens stored locally with a JSON interface.
A hosted read-only view of user-approved aggregates, with raw request content and OAuth credentials excluded.
The interface is reserved, but balances and payouts remain disabled until pricing, authorization, reconciliation, and dispute rules are implemented.
Why the honest version wins
TokenShare proves that provider/consumer framing is compelling. CodexShare starts with the measurable part: real local usage. The disabled withdrawal surface is explicit about what is still missing.
Questions before you connect
The provider daemon forwards model requests and therefore handles their contents in memory. CodexShare does not persist prompt or response bodies, but a modified provider could inspect them. Use a trusted provider.
No. The daemon injects OAuth only when calling the Codex backend. The consumer gets a scoped device credential, never the OpenAI credential.
The official Codex CLI, repository access, shell commands, file edits, approvals, MCP servers, and local skills all stay on the consumer machine.
No. CodexShare is an independent, experimental project. Users are responsible for ensuring their use complies with applicable subscription, organization, and service terms.
Private beta
macOS & Linux · official Codex CLI required