Check what you downloaded
Compare the printed hash with the one on the build. If they differ, don't run it.
# Windows
certutil -hashfile "REX Setup 0.2.5.exe" SHA256
# Linux / macOS
sha256sum rex_0.2.5_amd64.deb
[ Downloads ]
MIT · 14 days free · sign-in required
Get REX, and everything else I've shipped.
Every build lists its SHA-256 — check it before you run it. That's true of software from anyone, including me.
[ 01 ]
Builds
Loading builds…Reading the release manifest.
Installing on Debian family
Use apt, not dpkg -i — it pulls the
dependencies. As root the launcher adds --no-sandbox for you;
as a normal user it runs fully sandboxed.
sudo apt install ./rex_0.2.5_amd64.deb
rex
# desktop_* tools need xdotool (X11)
# or ydotool under Wayland
[ 02 ]
Three steps and you're working
STEP 01
Add a provider
Settings → Providers. Paste an API key — it's encrypted into the OS credential store, not a dotfile. Or skip it entirely: if Ollama is running locally, REX finds it on its own.
STEP 02
Open a project
New session, then pick a folder. Every file and shell operation is scoped to it, and the status bar shows you which folder is live.
STEP 03
Ask for something real
"Find where we verify JWTs and fix anything unsafe." REX greps, reads, proposes a diff, and waits for you before it writes a byte.
[ 03 ]
Releases
Every build here is published with its SHA-256. Check it before you run anything — including this.
Or build it yourself
It's all on GitHub.
Node 20+, one npm install, and npm start
builds and launches the app.