ROXYone session · every model
Install

Download ROXY

One executable, no installer and no runtime. Pick your platform, verify the checksum if you want, and launch. The whole flow takes about two minutes.

LATEST RELEASE · v0.2.0 · UPDATES IN-APP
WindowsLinuxFirst runVerify downloadUpdatingTroubleshootingBuild from source
WIN

Windows 10 / 11 · x64

64-bit Windows 10 (1809+) or Windows 11. No admin rights required.

Download .zip →Download .exe →
zip contains roxy.exe + README. The bare .exe is the same binary.
LNX

Linux · ARM64

aarch64 Linux with a desktop session (X11 or Wayland) and OpenGL.

Download binary →
x86_64 Linux builds from source — see below.
“Windows protected your PC — unknown publisher”. ROXY builds are not code-signed yet, so Windows has no publisher identity to show and treats the file as unrecognized. That message is about identity, not detection: a brand-new unsigned binary has no SmartScreen reputation at all. Click More info → Run anyway, or clear the download mark first. Verify the checksum below if you want proof the file is the one published here.
Windows

Install on Windows

  1. Download the ZIP

    Use the Windows card above. Your browser may keep it in Downloads.

  2. Extract it

    Right-click the ZIP → Extract All. Running ROXY from inside the ZIP will not work.

  3. Clear the “downloaded from the internet” block (optional)

    In PowerShell: Unblock-File .\roxy.exe. This removes the SmartScreen prompt entirely.

  4. Move it somewhere permanent

    For example %LOCALAPPDATA%\Programs\ROXY\. The updater needs write access to this folder.

  5. Run roxy.exe

    If SmartScreen appears, choose More info and confirm only if you verified the checksum or trust the source.

  6. Connect a model

    Open Models → API models and add a provider, or install a CLI agent in one click.

Where Windows puts your data

Config, sessions and the log live in %APPDATA%\roxy\. Delete that folder for a clean slate. Settings also have a Data folder button that opens it.

Linux

Install on Linux

  1. Download the binary

    Use the Linux card above.

  2. Make it executable

    chmod +x roxy-linux

  3. Move it onto your PATH

    For example mkdir -p ~/.local/bin && mv roxy-linux ~/.local/bin/roxy.

  4. Launch it

    Run roxy from a terminal once so you can see any graphics-driver message.

  5. Connect a model

    Same as Windows: Models → API models, or install an agent CLI.

curl -fL -o roxy https://github.com/RoaraxAli/ROXY/releases/latest/download/roxy-linux
chmod +x roxy
mkdir -p ~/.local/bin && mv roxy ~/.local/bin/roxy
roxy

Data lives in ~/.config/roxy/.

First run

What happens when ROXY starts

The loader checks your machine, restores sessions, and looks for update and gateway state. Then you land in a chat with one empty session.

1 · Connect a model

Models → API models for a key-based provider, or CLI agents to install Codex, Claude Code, Gemini CLI and friends.

2 · Pick it in the composer

The model button above the message box opens a searchable picker grouped by provider.

3 · Switch whenever

Pick another model mid-thread. The transcript is replayed, so context carries over.

ChatGPT / Codex sign-in. Some agents need an interactive login. ROXY opens your own terminal for that command — it never asks for your CLI password.
Integrity

Verify a download

Every release publishes SHA-256 checksums. They catch a corrupted or swapped file; they do not replace a code signature.

Windows (PowerShell)

Get-FileHash .\roxy-windows-x64.zip -Algorithm SHA256

Linux

sha256sum roxy-linux

Compare the printed hash with the value on the release page or the bundled SHA256SUMS.txt. If they differ, do not run the file — download it again.

Why no publisher name? Windows shows a verified publisher only for signed binaries. A code-signing certificate is a paid, identity-verified process; until ROXY ships signed builds, the checksum is the strongest verification available.
Updates

Updating ROXY

ROXY checks for a new release when it starts. If one exists, a window appears with a live progress bar: it downloads, swaps the binary after ROXY closes, and restarts. No terminal opens, and no manual download is needed.

  • Manual check: Settings → About → Check for updates.
  • Requirements: curl (built into Windows 10+, present on Linux) and write access to ROXY's folder.
  • Portable install: keep roxy.exe somewhere your user account can write, not Program Files.
Troubleshooting

If something goes wrong

The window does not open

On Linux, make sure you are in a graphical session and have an OpenGL driver. Running from a terminal shows the exact error. On Windows, extract the ZIP before running.

“Needs Node.js” when installing an agent

Agent CLIs are npm packages. Install Node.js LTS, restart ROXY, then press Install again. 9Router has the same requirement.

Models list is empty for a provider

Press Refresh in Models. For a local server, confirm it is running — 9Router listens on localhost:20128. A key-based provider needs a valid key before its /models endpoint answers.

The update downloads but nothing changes

The updater needs write access to the folder holding the executable. Move ROXY out of a read-only location and retry from Settings → About.

“Windows protected your PC” — unknown publisher

Windows shows this for every executable that is not Authenticode-signed, because it has no publisher identity to display. Choose More info → Run anyway, or run Unblock-File .\roxy.exe before launching. Removing the message for everyone requires a code-signing certificate issued to a verified publisher; ROXY does not have one yet, which is why every release publishes SHA-256 checksums instead.

Antivirus flags roxy.exe

Reputation warnings are common for new unsigned binaries. Verify the checksum; if you would rather compile it yourself, the source and build steps are below.

From source

Build ROXY yourself

Rust 1.80+ and a C toolchain. The Windows cross-build additionally needs gcc-mingw-w64-x86-64.

git clone https://github.com/RoaraxAli/ROXY.git
cd ROXY

# native build (Linux x86_64 / ARM64)
cargo build --release
./target/release/roxy

# Windows x64 cross-compile from Linux
rustup target add x86_64-pc-windows-gnu
cargo build --release --target x86_64-pc-windows-gnu

A self-hosted build can point the updater at its own manifest with ROXY_MANIFEST=https://…/update.json cargo build --release.