The AI workflow IDE, for Codex
Optimize your Codex workflow
Sign in with `codex login` once, and run Codex inside Ropenode: in every project you open, beside a full git client, an editor and terminals, on Windows or inside WSL.
Free to download. Ropenode never holds a model credential — the `codex` CLI authenticates itself.
What you get
The workspace, around the Codex console
A Codex session is the real Codex CLI in a terminal inside Ropenode. Everything around it is the same app a Claude Code session gets.
No API key
Ropenode starts the official codex binary, which signs in with your ChatGPT account. Your credentials are never read, stored or proxied.
Every project in one place
Codex sessions live in the same projects as everything else. On Pro, the Projects Grid tiles whole projects side by side.
A full git client
Review what Codex changed in the git panel: diffs, staging, commits, stash, blame and a conflict resolver.
Editor and terminals
A Monaco editor, project search and a dock of real terminals beside the console.
WSL, as the right user
In a WSL project, codex runs inside the distro as the user who owns the project, not as root.
Your model settings
Ropenode passes no model flag, so the model is whatever your ~/.codex/config.toml says.
What is supervised, and what is not
Ropenode's edit policy does not apply to Codex sessions. This is the most important thing on this page.
A Codex session is the real Codex TUI running in a terminal inside Ropenode. A terminal has no approval channel for Ropenode to answer, so none of the review machinery reaches it:
- no edit policy — protected, blocked and no-read rules are not enforced;
- no accept/deny diff;
- no per-turn undo;
- no live Log or session file list;
- no MCP servers from Ropenode — Codex reads its own MCP configuration.
What governs writes there is Codex's own approval model, exactly as if you had run codex yourself
in Windows Terminal. The desktop app marks every Codex console Unsupervised rather than
leaving you to find out.
If you need the policy enforced
Use a Claude Code session for that work: the edit policy, the diff review and per-turn undo all apply there. For Codex, keep a close eye on the git panel, which shows every change it made.
Codex questions
No. Run
codex loginonce and the CLI holds its own ChatGPT session at~/.codex/auth.json. Ropenode never reads it.
Point it at a repo
Install it, run `codex login`, and open your first project. The Free tier holds three at a time.
Download for WindowsFree. No account required to try it.