Getting started
Install Ropenode
Download the Windows installer from the download page and run it.
Before you start
Ropenode drives an agent CLI, so that CLI has to work on its own first. Open PowerShell and check whichever you plan to use:
claude --version codex --version node --version git --version
You need at least one of claude and codex — installing both is fine and lets you
choose per session. If one is not found, install it and make sure you have logged in
(claude walks you through it on first run; for Codex, run codex login). Ropenode warns
you at startup if claude, node or git is missing; whether codex was found is shown
in Settings → Models.
Where your data lives
Everything Ropenode stores is on your machine:
%APPDATA%\ropenode\ropenode.db— projects, sessions, prompts, tool calls, history.~\.claude\projects\...— the transcripts written by the CLI itself, which Ropenode reads.
Secrets (a Jira token, a mail or FTP password, a WSL sudo password) are encrypted at rest with AES-256-GCM. See Security.
Updating
Ropenode tells you when a new version is ready and installs it with Restart to update.
Your projects, settings and history are kept: they live in %APPDATA%\ropenode\, which the
installer never touches. See Updates.
SmartScreen
The installer is not yet code-signed, so your browser and Windows may each ask you to confirm the first time. That is about the missing signature, not the file:
- When it downloads, the browser may say the file "isn't commonly downloaded". Choose Keep (in Edge: ⋯ → Keep → Show more → Keep anyway).
- When you run it, Windows shows "Windows protected your PC". Click More info, then Run anyway.
To confirm the file is ours, run Get-FileHash on it in PowerShell and compare the result
with the SHA-256 on the download page.
Last updated Oct 11, 2026