Codex provider (OpenAI CLI-backed sessions) (part 3)
Part 3 of the Codex provider page: what actually runs when you start a Codex session, how Omniscio talks to it and streams a turn back, and where the pieces live in the codebase.
On this page
What it is
This is part 3 of the Codex provider (OpenAI CLI-backed sessions) page. It covers what Omniscio actually starts when a Codex session runs, how the two talk to each other, how a turn is streamed back and folded into readable prose, and which parts of the codebase are involved.
Where to find it
Nothing described here has a screen of its own — it is the machinery behind the Codex sessions you already see in the sidebar. The one visible part, the engine mark in a session header, is covered on the parent page, and the rest is listed at the end of this page as the files involved.
How it behaves
From the outside a Codex session behaves like any other session in Omniscio: the same statuses, the same permission prompt in the same pane, the same per-session cost and token counters, and the same archive, pause and snooze controls. What differs is what runs under it — instead of a Claude process, Omniscio starts OpenAI's own Codex program and speaks to it directly, so a turn can fail in ways that are Codex's rather than Claude's. The notes below are for anyone maintaining that plumbing.
Related
The user-facing half of Codex — switching it on, signing in and what a session looks like — is on the Codex provider (OpenAI CLI-backed sessions) page, and the accounts, per-project default and model chips are in part 2. The behaviour this code must hold to is written up in the Codex robustness contract, and the wider engine registry it plugs into is in the provider registry contract.
Last verified 2026-10-06