JsonUI
← jui vizWatch Codex sessions in jui vizjui viz shows the Codex sessions on your machine beside the Claude Code ones, in the same rooms. You can answer Codex's permission requests from the page, stop a turn, start a Codex session from the bell, and choose a local model from LM Studio or Ollama. You can also send a Codex session a prompt from its card, read its history, and clock it out.9 min read
Start the Codex daemonjui viz reads Codex sessions from the Codex app-server daemon. Start it once:
shell
codex app-server daemon start
• While the daemon runs, a `codex` you start in a terminal attaches to it by itself, and jui viz sees it. Nothing has to be installed in Codex: no plugin and no hooks. • jui viz never starts the daemon. With no daemon it shows no Codex sessions and no warning; the Claude Code side works as before. • The `jui viz` server finds a daemon started later on its own, and reconnects when the connection drops.
Sessions jui viz does not see• A codex started while no daemon was running. • Sessions of the Codex extension for VS Code (it runs its own server). • A codex started with a local provider on its command line (--oss, -c model_provider=… or a profile): it does not attach to the daemon. To use a local model, start it from the bell (see Local models below).
Check it`jui viz doctor` has a codex daemon row. It is never NG, because a machine with only Claude Code has no daemon. When the daemon is not running, the row says how to start it:
shell
$ jui viz doctor
OK codex daemon: not running (optional: codex app-server daemon start shows the Codex sessions)
Turning it offTo keep jui viz from reading the daemon at all, write "codexDaemon": false in the viz folder's config.json (on by default). What jui viz sends to the daemon is what you do on the page: a prompt, a stop, your answer to a permission request, a clock-out (it stops following the thread), and the name of a thread started from the bell. It writes no Codex configuration, apart from the homes for local models that you ask for.
What you seeA Codex session is a robot at a desk in its project's room, like a Claude Code session. A thread it starts under itself (a subagent) is one of its subagents. Its robot moves the same way when it runs a command, edits or writes a file, or calls an MCP tool, and the side panel, the tasks and the test runs read it the same way.
Which CLI it isEach robot is ringed in its CLI's colour: its name pill, its name tag in the room, its tag in the session list, the number on its card and its mark in Talk. The session list's tag and the card's number also name the CLI, Claude or Codex. A Codex robot's short name is taken from the end of its thread id, not the start: the start of a Codex thread id is the time it was made, so every one begins alike.
The modelA session's card shows the model it runs under its name. A model from LM Studio or Ollama gets a local (ローカル) tag beside it. A subagent's card shows its session's model.
The exported demo has two Codex sessions among its Claude Code ones, so you can see the rings on the overview page's demo.
Answer Codex's permission requestsWhen Codex asks to run a command or to change files, the request becomes a permission card on the page, the same card a Claude Code request makes. The terminal still shows its own dialog: answer in either place, and the first answer wins. When you answer in the terminal first, the card is marked as answered there. There is nothing to set up for this: no relay and no hooks.
What each button sends• Allow (許可): allows this one request. • Deny (拒否): declines it. A reason you type is not passed to Codex. • Always allow (今後も許可): for a command, the rule Codex proposed with the request; for a file change, allows file changes for the rest of the session. Other kinds of request, such as a request for more permissions or a question from an MCP server, are not shown as cards; answer them in the terminal.
Stop a turnStop (停止) on a Codex session's card interrupts the turn that is running, at once. It does not wait for the next tool boundary as a Claude Code session's stop does, so there is nothing to take back: the card has no cancel for it. It works only while the session is working or waiting.
Start a Codex session from the bellThe Call (呼び出し) dialog has two tabs, Claude Code and Codex; the arrow keys move between them, and the dialog opens on the tab you chose last while the page stays open. Type a name and a role, copy the line, and run it in a terminal yourself. jui viz runs nothing. On the Codex tab the line starts the daemon first (it does nothing when the daemon already runs), then a new Codex session in the room's folder:
shell
cd /work/MyApp && codex app-server daemon start >/dev/null && codex 'This session'\''s role is as follows (from jui viz'\''s call button).'$'\x0a''Session name: Docs writer'
Codex has no option for a session's name, so the name goes into the first prompt, as on the Claude Code tab. When jui viz sees the new thread, it names the thread from that prompt, once, and only when the thread has no name yet.
Local models (LM Studio and Ollama)On the Codex tab a Model (モデル) list offers Codex's default (the model in your config.toml), then the models of LM Studio and Ollama on this machine. They are read when you open the tab, from each server on 127.0.0.1 (LM Studio on port 1234, which `lms server start` starts; Ollama on 11434). A server that does not answer, or has no model, is one greyed-out line saying so.Choosing a local model changes the line. It makes the server's own Codex home when it is missing, starts that home's daemon, and runs codex there with the model:
shell
cd /work/MyApp && jui viz codex-local ensure ollama >/dev/null && CODEX_HOME=/home/me/.codex-local/ollama codex app-server daemon start >/dev/null && CODEX_HOME=/home/me/.codex-local/ollama codex --model=qwen3-coder:30b 'This session'\''s role is as follows (from jui viz'\''s call button).'$'\x0a''Session name: Docs writer'
Why a home of its ownA codex started with --oss or another local provider on its command line does not attach to the daemon, so jui viz would not see it. A codex whose home names the provider as its default does attach. So each server gets ~/.codex-local/lmstudio/ or ~/.codex-local/ollama/, and the `jui viz` server reads the daemon of each such home beside the one of ~/.codex. A home made while the server runs is picked up within 5 seconds.
What goes into the homeIts config.toml names the provider, and copies the [features] and [mcp_servers.*] tables of your ~/.codex/config.toml, so your MCP servers work there too. Nothing else is copied: the sessions, the sign-in and the trusted projects stay in ~/.codex, so the first start in a project asks you to trust it again. The home is made only when it has no config.toml. A home that exists is never rewritten: edit it freely.
You can make or list the homes yourself with `jui viz codex-local` (see /reference/cli-commands). `jui viz doctor` adds a row for each home's daemon, with the line that starts it.
shell
jui viz codex-local ensure lmstudio
jui viz codex-local list
Codex's usage limits in the headerCodex's 5-hour and weekly limits come from the daemon, when a Codex session on it answers. Once a value has arrived, a Claude / Codex list appears beside the limits in the header and picks which plan they show; this browser keeps your choice. Hovering over a limit shows that window for both plans. Claude Code's limits still come from its statusLine (see Panels, cards and boards). Codex's need no install.
Send a promptA Codex session's card takes a prompt in its History (応答の履歴) tab, the same field and Send… (送信…) as a Claude Code session's. It goes through the daemon, so it needs no plugin, no channel and no relay: only the session's connection to its daemon.• When the session waits, the prompt starts a new turn. • When a turn runs, the prompt goes into that turn (Codex's steer). • The page says sent only once the daemon has taken it. jui viz changes nothing else: the model, the approval policy and the sandbox stay as the session has them. • Files attached with Attach… (添付…) go as the same attached: lines as for Claude Code.
When it cannot be sentA Codex session that is not connected to its daemon cannot receive one: the field is disabled and says This Codex session is not connected to its daemon. Prompts cannot be sent. (Codex daemon に接続していないため、ここから送信できません。) A subagent's card has no field, as for Claude Code. When the daemon's answer does not come, the send fails with Codex delivery could not be confirmed; check the history before sending again. jui viz never sends it again by itself.
Read the historyThe History (応答の履歴) tab shows a Codex session's turns: your prompts, Codex's answers, and its tool calls with their output, as for Claude Code. It is read from the session's own Codex files (the rollout the daemon names, and only inside that home's sessions folder), only while the tab is open, with the same limits and Read earlier. Like Claude Code's, it is never written to the log, a snapshot or an export.
What is not shownCodex's instructions and its reasoning are not shown, nor the copies of a message Codex records twice. A subagent's message to its session is a row of its own when its text is plain; an encrypted one is never shown. The same goes for a session on a local model's home and for a subagent's own history.
Clock outA Codex session's card has Clock out… (退勤…). It takes the robot out of the room: jui viz stops following the thread (it unsubscribes from it on the daemon). Nothing is sent to any process, so a Codex terminal is not closed: which terminal holds which thread cannot be told, and stopping following a thread never stops one.• Not while a turn runs: stop it first. • A thread no terminal holds is closed by Codex a little later. Its history stays, and codex resume brings it back. • When a Codex terminal runs in the same Codex home (or that cannot be told), the toast says so: if that terminal holds the thread, the robot comes back at its next turn. • The log reads Clock-out (stop following, no signal) (退勤(購読をやめる・合図なし)).
When the terminal is closedWhen no Codex terminal is left in a Codex home, its sessions' robots leave by themselves, the way a Claude Code session leaves at its end. A turn still running in the daemon finishes first. jui viz tells this from the processes that have the home's log database open (lsof and ps); while another terminal still runs in that home, or when it cannot tell, the robots stay rather than guess.
Stopped at the usage limitA Codex turn that fails on the plan's usage limit is told apart, as a Claude Code one is: the robot is dazed, with × eyes and stars circling its head, and reads Stopped at the limit (上限で停止) until the next prompt. See Stopped at the usage limit in Reading a robot at a glance.
Not yet• Bills and the cost of a Codex session: Codex's token counts are not read. • Codex's own records of its agents talking to each other do not show in Talk. A message sent with `jui viz message` does (see Messages between sessions). • The sessions in Sessions jui viz does not see above.
Keep reading
jui viz`jui viz` shows the Claude Code sessions and subagents running on your machine, and the Codex sessions too, as rooms and robots in the browser. Start with the demo below, then pick the article for what you want to do./viz
Set upInstall the plugin, start the server, change the page's language, and update, remove or troubleshoot jui viz./viz/setup
The room and its robotsWhat a room, a robot, its motion and its one line of text tell you about a session./viz/room