Codex
If the machine has Codex signed in, its sessions show up in the dashboard next to Claude Code’s, each with its own badge. Fleetly reads the sessions Codex writes to ~/.codex/sessions and never reads the Codex login: it only checks that it exists.
What you can do
- See the sessions, their state (working or your turn), the chat and the commands Codex ran.
- Send a message to a Codex session. Each message resumes the session on the same machine, and the answer streams in live.
- Start a new session: in +, choose Codex and the model (the list comes from the Codex installed on the machine).
- Use the queue: the message is delivered when the session finishes what it is doing.
- Approve from your phone, with the Codex hooks installed and approved in Codex (in VS Code, Review hooks → Allow all; in the terminal,
/hooks). See Approvals.
Permission modes
In sessions Fleetly drives, Codex works in its sandbox:
| In the dashboard | In Codex |
|---|---|
| Ask for approval, Plan only | Read-only: reads and answers, changes nothing. |
| Auto, Can edit files | Edits only inside the project folder, no internet. |
Fleetly never turns off the Codex sandbox.
What isn’t possible yet
- Messaging a session open in the terminal (interactive
codex): Codex has no input the dashboard can reach. The session shows up; to answer, use the terminal or wait for it to close. - Codex cloud tasks and ChatGPT on the web: they aren’t on the machine, so they don’t show up.
- Automatic session names and the plan meter come from Claude. On a machine with only Codex, they stay off.
When the Codex quota runs out, the chat says so, with the date it renews.
Didn’t find what you were looking for? Write to admin@fleetly.tools.