Does Ropenode need my API key?

No — and it never asks for one, for either agent. Ropenode spawns the official claude or codex binary, which authenticates itself exactly as it does in your terminal. Your credentials are never read, stored, proxied or seen by us.

Which agents does it support?

Claude Code (fable, opus, sonnet and haiku) and Codex on your ChatGPT account. You choose per session, and both work in the same projects, beside the same git panel, editor and terminals. They are not supervised the same way — see the next question. Install one or both.

Is every agent run supervised the same way?

No. Claude Code sessions go through Ropenode's approval gate: the edit policy, diff review, per-turn undo and the live Log. A Codex session is Codex's own interactive console, which has no approval channel for Ropenode to answer — so it runs under Codex's own approval model, and the app marks it Unsupervised.

Is this a replacement for Claude Code or Codex?

No. It is a management layer around the official CLIs. You still need at least one of them installed and logged in — Ropenode runs it as a real terminal inside the window and builds the workspace around it.

Which platforms are supported?

Windows 10 and 11 (x64), including projects inside WSL, where the agent runs in the distro as the user who owns the project.

How is the per-turn undo different from `git restore`?

git restore reverts the file, which also throws away your uncommitted changes to it. Ropenode captures each file's pre-edit content at the moment the agent asks to write it, so it can revert exactly what one prompt changed and leave everything else — including your own concurrent edits — alone. It covers Claude Code sessions in a git repository.

Can an agent get past the edit policy?

Not through its edit tools. On a Claude Code session every edit is checked in the PreToolUse hook before it runs, and a deny holds even under acceptEdits or bypassPermissions, because the decision is made outside the model’s reach. With Don’t let the shell edit files switched on, the common ways a shell rewrites a file are refused too — but a shell can run any program, so for a hard boundary, run the project in a VM or a container. A Codex session is not covered by the policy at all; see the supervision question above.

What happens to my data?

It stays on your machine. Projects, sessions and their history live in a local SQLite database; secrets are AES-256-GCM encrypted at rest with a key in Windows Credential Manager (or behind a master password you choose). The app contacts ropenode.com for two things only: to check for a new version, and — once you sign in — to re-confirm your licence. Neither sends your code, your prompts or your file paths.

The AI workflow IDE for Windows & WSL

Optimize your AI coding workflow

Run Claude Code and Codex across every project in one window, with a review gate in front of every supervised edit, per-turn undo and a full git client.

Download for Windows Read the docs

Free to download. Bring your own Claude or ChatGPT account — Ropenode never holds a model credential.

Fits the stack you already have

Claude Code

Codex

Windows

WSL

Git

Jira

1 · Start

The right agent for every session

Every session picks its agent: Claude Code (fable, opus, sonnet, haiku) or Codex on your ChatGPT account. Both run as the vendor's own CLI and sign in exactly as they do in your terminal — Ropenode never holds a model credential.

On a Claude Code session, the project's memory notes and your templates are part of the agent's instructions from the moment its conversation starts, so it begins every task knowing how this client's code is written. Claude Code sessions get the whole review stack; a Codex session runs under Codex's own approval model, and the app marks it Unsupervised.

Claude Code or Codex, chosen per session, in the same projects
Project memory and templates added to a Claude session’s instructions
No API key, ever — each CLI signs in as itself
Codex runs as its own console, labelled Unsupervised in the app

How the two agents compare →

2 · Run in parallel

Pro

Every client project in one window

Tile whole projects side by side — each tile a complete project window with its own console, files, git panel and diffs — or several sessions of one project in a Sessions Grid.

Tiles tell you when they need you: amber when an agent is waiting on you, green when a turn has finished and you have not looked yet. You stop babysitting terminals and start supervising.

Projects Grid: two columns or 2×2, saved as named views
Each tile is a full project, not a read-only preview
On Free, the Sessions Grid tiles several sessions of one project
A taskbar flash and a desktop notification when a session finishes

See how the Projects Grid works →

3 · Supervise

A policy gate in front of every supervised edit

On a Claude Code session every edit the agent makes is checked against the project's policy in the PreToolUse hook, before it runs. A deny holds even under acceptEdits and bypassPermissions, because the decision is made outside the model's reach: the agent is never asked, so it cannot be talked past.

Switch on shell-write blocking and the common ways a shell rewrites a file are refused too.

Protect, force-review or hard-block paths, with globs read the way .gitignore reads them
Folders the agent may never read, hidden even from its own searches
Optional shell-write blocking: redirects, sed -i, tee and Set-Content refused; rm and mv ask first
Edits confined to the project root by default, with named exceptions
Say yes in advance: auto-approved paths and commands that never outrank a deny
Test a path against the saved rules before you rely on them

How the edit policy works →

4 · Review & undo

Review every edit. Undo any turn.

When an edit needs your approval, because the session asks or because your policy forces review, it opens as a side-by-side diff with the agent's own reasoning for why. Accept it, or deny it and tell the agent what to do instead.

When a whole turn went the wrong way, revert exactly what that prompt changed: every file, or just one. Your own uncommitted edits survive, because Ropenode kept each file's content from the moment the agent asked to write it. This is not git restore.

Review and undo cover Claude Code sessions. See what is supervised.

Side-by-side diffs with the agent’s reasoning attached
Answered from the keyboard, so a stray click can never approve an edit
Per-turn undo that leaves your concurrent edits intact
A live Log of every prompt and tool call, and the files each session touched

Per-turn undo in detail →

5 · Ship & recap

Commit, deploy and look back without leaving

A real git client sits beside the agent: stage, commit, amend, branch, stash, blame, push and pull with git's real output, and one resolver for conflicts, rebases and cherry-picks.

On Pro, push a project's changed files to a stage or live server over FTP or FTPS — it only ever deletes files it uploaded — and keep a Work log that answers “what did I do on Tuesday?” across every project.

A git panel with muted files, blame and your Jira prefix on commits
Conflicts, rebase and cherry-pick, with Continue and Abort always in reach
On Pro, FTP/FTPS deploy, and a session’s changed files as a ZIP
On Pro, a Work log of every day, searchable across projects

The git panel →

The CLI is excellent. Ropenode is the workflow around it.

Ropenode runs the official CLIs — it replaces neither of them.

	The CLI alone	With Ropenode
Projects at once	One terminal per project	Projects in tabs, or tiled side by side
Switching agent	A second CLI in a second terminal	Claude Code or Codex per session, in the same projects
Undoing an agent	git restore — which also reverts your own uncommitted changes to the file	Per-turn undo that leaves your own edits intact
Guardrails	Permission rules you write in JSON settings	A per-project policy screen: force-review, hard-block, no-read folders and a rule tester
What it can read	Deny rules you write per path	No-read folders, also enforced against git history and recursive greps
History	Transcript files on disk	A live Log of every tool call, and on Pro a searchable Work log of each day
WSL	Runs as whoever launched it	Runs inside the distro as the project-owning user
Review	Read the diff in the terminal	Side-by-side diff with the agent’s reasoning

Everything in Ropenode

Free and Pro, feature by feature

The features above and everything else, one line each. Everything that keeps an agent from wrecking a repository is free, and stays free.

Free and Pro, feature by feature
Feature	Free	Pro
Limits
ProjectsFree keeps three projects and runs agents in three at a time. Nothing over the limit is hidden or deleted.	3	Unlimited
Agent sessions running at onceA session counts while its agent is attached. The limit never stops one that is already running.	3	Unlimited
Safety
Edit policyProtect, force-review or hard-block writes. A deny holds even under acceptEdits.	Included	Included
Read rulesFolders the agent may never read, including through git log -p and recursive greps.	Included	Included
Shell-write blockingWhen switched on: redirects, sed -i, tee and Set-Content are refused; rm and mv ask first.	Included	Included
Auto-approved paths and commandsFewer prompts without weakening a deny: every block rule still wins.	Included	Included
Diff reviewAccept or deny each proposed edit, with the agent’s reasoning attached.	Included	Included
Per-turn undoRevert what one prompt changed, or one file of it, and keep your own edits.	Included	Included
Agents & sessions
Claude Code and CodexChosen per session. Each CLI signs in as itself; Ropenode never holds a credential.	Included	Included
Embedded agent consoleThe real vendor TUI, alive across view switches, with image paste and file drop.	Included	Included
Live Log and session filesEvery prompt and tool call as it happens, and each file the session changed.	Included	Included
Project memory and templatesNotes and presets added to a Claude session’s instructions when its conversation starts.	Included	Included
Sessions GridSeveral sessions of one project tiled, each reviewing its own diffs in place.	Included	Included
Work logWhat happened in every project, day by day, in a calendar you can search.	Not included	Included
Attention signalsTabs and tiles blink when an agent needs you; a notification when a turn ends.	Included	Included
Workspace
Projects GridWhole projects side by side, two columns or 2×2, saved as named views.	Not included	Included
Editor, diff and searchMonaco editor and file explorer, side-by-side diffs, project search with regex.	Included	Included
PHP code intelligencePSR-4 and classmap resolution, namespace completion, import checks.	Included	Included
Terminal dock and tasksReal terminals in a bottom dock, and your npm, composer and artisan scripts a click away.	Included	Included
Git
Git panelStage, commit, amend, branch, push, pull, stash and blame, with git’s real output.	Included	Included
Conflicts, rebase and cherry-pickOne resolver, with Continue and Abort always in reach.	Included	Included
Muted filesKeep an agent’s scratch files off the dirty marker without touching .gitignore.	Included	Included
Integrations
JiraThe project’s issues in a panel: move them across the board, send one to a session.	Not included	Included
Mail inboxAn IMAP inbox beside the work, with filters. Remote images are blocked; nothing is ever sent.	Not included	Included
FTP / FTPS deployPush changed files to stage or live. It only ever deletes files it uploaded.	Not included	Included
Session files as a ZIPEvery file a session changed, packed at its project paths, ready to upload by hand.	Not included	Included
MCP serversPlaywright and Figma for Claude Code sessions, one click, including from WSL.	Not included	Included
Platform & security
WSL projectsThe agent, terminals and git run inside the distro, as the user who owns the project.	Included	Included
Encrypted secretsAES-256-GCM, with the key in Windows Credential Manager or behind a master password.	Included	Included
Local-firstProjects, prompts and history stay in a database on your machine.	Included	Included
Support
Priority supportPro goes to the front of the email queue.	Not included	Included

A Codex session is Codex’s own console: the edit policy, diff review, undo, the live Log and MCP servers apply to Claude Code sessions.

The cockpit, not the fuel

You already pay for the model. We never touch your tokens and take no margin on your AI.

Free

The whole safety stack, a few projects at a time.

forever

3 projects, and 3 agent sessions running at once
Claude Code and Codex, chosen per session
Safe Agent Edits and per-turn undo, free for good
Git, editor, project search and the terminal dock
Sessions Grid and first-class WSL

Download for Windows

Pro

Supervision at scale.

$19 /month

billed monthly

Everything in Free, with no project or session limit
Projects Grid — whole client projects side by side
Work log — every session’s work, a day at a time
Jira panel — issues into a session, status back out
MCP servers — one-click Playwright and Figma for Claude Code
Mail inbox, FTP/FTPS deploy and session files as a ZIP
Priority support

Back shortly. Nothing you have is affected.

Requires the Claude Code or Codex CLI and your own account with that provider (sold separately). Prices in USD; no VAT is added.

Questions

: No — and it never asks for one, for either agent. Ropenode spawns the official claude or codex binary, which authenticates itself exactly as it does in your terminal. Your credentials are never read, stored, proxied or seen by us.
: Claude Code (fable, opus, sonnet and haiku) and Codex on your ChatGPT account. You choose per session, and both work in the same projects, beside the same git panel, editor and terminals. They are not supervised the same way — see the next question. Install one or both.
: No. Claude Code sessions go through Ropenode's approval gate: the edit policy, diff review, per-turn undo and the live Log. A Codex session is Codex's own interactive console, which has no approval channel for Ropenode to answer — so it runs under Codex's own approval model, and the app marks it Unsupervised.
: No. It is a management layer around the official CLIs. You still need at least one of them installed and logged in — Ropenode runs it as a real terminal inside the window and builds the workspace around it.
: Windows 10 and 11 (x64), including projects inside WSL, where the agent runs in the distro as the user who owns the project.
: git restore reverts the file, which also throws away your uncommitted changes to it. Ropenode captures each file's pre-edit content at the moment the agent asks to write it, so it can revert exactly what one prompt changed and leave everything else — including your own concurrent edits — alone. It covers Claude Code sessions in a git repository.
: Not through its edit tools. On a Claude Code session every edit is checked in the PreToolUse hook before it runs, and a deny holds even under acceptEdits or bypassPermissions, because the decision is made outside the model’s reach. With Don’t let the shell edit files switched on, the common ways a shell rewrites a file are refused too — but a shell can run any program, so for a hard boundary, run the project in a VM or a container. A Codex session is not covered by the policy at all; see the supervision question above.
: It stays on your machine. Projects, sessions and their history live in a local SQLite database; secrets are AES-256-GCM encrypted at rest with a key in Windows Credential Manager (or behind a master password you choose). The app contacts ropenode.com for two things only: to check for a new version, and — once you sign in — to re-confirm your licence. Neither sends your code, your prompts or your file paths.

Take the wheel

Download Ropenode, point it at a repo, and watch the first agent run land in a diff you can actually review.

Download for Windows

Free. No account required to try it.