OpenAI
How Finexia drives Codex CLI: which binary, which workspace, which limits.
- Driven as
- A headless process, one per card, in its own isolated workspace. Finexia never holds a key for it: the subscription and the credentials stay yours.
- What the desk reads back
- The raw stream of the process, turned into a trace — one line per phase, per tool, per process. Never a summary, and the raw output stays open underneath.
- Where it comes from
- This entry is not written by hand. It is read from the core’s provider registry, so a fourth provider appears here the day the core supports it — and no provider can appear here without existing there.
Registry: openaiHow an adapter drives it.
More in Models & Providers
- Provider matrixServed, experimental and planned — with the evidence level of each.
- On your machineYour own subscriptions, driven headless in isolated workspaces.
- AnthropicDriven through the claude CLI, headless, in an isolated workspace.
- GoogleDriven through the gemini CLI, headless, in an isolated workspace.