Profile Routing
Pick the Codex OAuth profile that should execute each request.
Codex Desktop API
A licensed Windows bridge that turns local Codex OAuth profiles into a Responses-style API your tools can call without handing account custody to a hosted proxy.
Desktop appLicensed accessMulti-profile routing
Profile routing verifiedResponses-style local API
authProfileId
Integrations use opaque profile ids instead of filesystem paths.
Safe Sign-In
The app starts Codex login flows without exposing tokens.
How it works
Payment, licensing, and Codex auth each stay in the right place.
The website handles purchase and delivery. The desktop app handles local readiness, license enforcement, Codex OAuth profiles, and the Responses-style loopback API your apps call.
Stripe handles the subscription
Checkout stays on Stripe. Only the currently open cohort is purchasable, and the site records the grandfathered monthly basis for fulfillment.
Keygen unlocks the desktop app
Fulfillment provisions a license and sends recovery links, release metadata, updater-ready download details, and the onboarding path by email.
Your tools call a real local API
Codex auth remains local. Your apps send unary or streaming Responses-style calls to the desktop app's loopback API.
API proof
A local Codex API with profile routing built in.
The core contract stays simple: health, readiness, models, auth profiles, unary responses, and SSE streaming. The profile selector is explicit and token-safe.
Explicit authProfileId routing
Choose a Codex OAuth profile per request, or omit the selector and let the local router use the default eligible profile.
Profile readiness you can inspect
The desktop app shows each profile's health, model count, routing state, and sign-in action without exposing tokens or raw auth files.
Bundled Codex skill onboarding
The included codexos-api skill teaches local Codex agents the endpoints, request shape, streaming route, and safety boundary.
Signed desktop updates
The Windows app checks a signed release feed, prompts when a newer build is available, and keeps a manual Updates page for recovery.
const profiles = await client.authProfiles();
const authProfileId = profiles.defaultProfileId;
await client.createResponse(buildTextResponseRequest({
prompt: "Ship the next local integration step.",
model: "gpt-5.5",
authProfileId
}));Product evidence
Profiles, routing, and sign-in are visible before integrations depend on them.
The app surfaces managed profile homes, explicit request routing, per-profile sign-in, health state, and copyable authProfileId values so customers know exactly what API bridge they are buying.
See setup docsProfile routing verifiedResponses-style local API
Profile Routing
Pick the Codex OAuth profile that should execute each request.
authProfileId
Integrations use opaque profile ids instead of filesystem paths.
Safe Sign-In
The app starts Codex login flows without exposing tokens.
Sequential launch pricing
The earlier you subscribe, the lower your lifetime monthly basis.
Founder 100 is the only cohort open right now. New subscriber pricing steps up only after each launch cohort fills.
Open now at $3/month
Founder 100
The earliest launch cohort with the lowest lifetime monthly price.
$3/ month
The current cohort is open at $3/month. After it fills, new subscribers move to $5/month; earlier subscribers keep their original monthly basis. Annual billing can use the same monthly basis when it opens.
- Codex Desktop API license
- Local API and SSE access
- Bundled codexos-api skill
- Grandfathered annual eligibility
Secure checkout by Stripe. License and download delivered after payment.
Price ladder
Each filled cohort raises the price for new subscribers.
- Members 1-100$3/month
Open now at $3/month
- Members 101-500$5/month
Opens after the current cohort fills
- Members 501-1,000$7/month
Opens after the current cohort fills
Founders are rewarded for taking the earliest risk: when the public price moves up, existing members keep the monthly basis attached to their original cohort.
Privacy boundary
No server-side custody of customer Codex auth.
Codex Desktop API is designed around a loopback API on the buyer's machine. Payment, license state, email delivery, and gated download metadata live in the distribution service. ChatGPT/Codex authentication remains local to the customer device.
Read the onboarding docsSupport
Questions before launch access?
Contact support for purchase recovery, license delivery issues, or setup questions. Do not send Codex tokens, cookies, browser storage, or license keys.
FAQ
Straight answers for the first launch.
Does Codex Desktop API host my Codex account?
No. The first launch path is local-first desktop distribution. Codex auth stays on the buyer's own computer.
Can I route requests across multiple Codex profiles?
Yes. The desktop app includes profile management and profile-scoped auth/model endpoints. Integrations can pass authProfileId for an explicit profile or omit it for default routing.
Are the early prices grandfathered?
Yes. Only one launch cohort is open at a time: $3 for Founder 100 members, then $5 through Early 500, then $7 through Launch 1,000. The server records the purchased tier, monthly amount, and annual-grandfathering metadata for fulfillment and future billing operations.
Where are downloads hosted?
The first launch provider is GitHub Releases behind the gated success and manage flow. Keygen Artifacts and R2 are represented behind the release provider abstraction for a future switch.
Will the desktop app update itself?
Yes after the first updater-capable Windows build is installed. The app checks the signed release feed on launch and periodically, shows a clear install prompt, and keeps a manual update check in the desktop Updates page.