Everything after
the install.

The short manual: requirements, first launch, every route, the recovery controls, and where OpenDeath keeps its data.

On this page

Requirements

  • Windows 10 22H2 or Windows 11, 64-bit. Windows on ARM is not supported by this build.
  • OpenCode Desktop. Required. Install the official desktop build first; the OpenDeath wizard checks for it and links to the download if it is missing.
  • Internet access. Needed for provider sign-in, model requests, and optional components.
  • About 1.3 GB free disk space. The portable build also needs room for its extracted runtime.
  • No administrator account. Both builds install per user. Administrator rights may be needed only if you choose to install a system-wide VPN client.
OpenDeath is not OpenCode. It installs alongside OpenCode Desktop, uses its own executable and data folder, and never launches or modifies the OpenCode app.

Install and first launch

With the setup wizard

  1. Download and verify OpenDeath-Setup-1.0.0.exe against SHA256SUMS.txt.
  2. Run the wizard. It checks for OpenCode Desktop before it copies anything.
  3. Choose a destination, shortcuts, and any optional VPN clients you want. Tor is already bundled.
  4. Finish the wizard and launch OpenDeath from the new shortcut.

With the portable build

Put OpenDeath-Portable-1.0.0.exe in a folder you control and run it. It extracts to a temporary folder and leaves no shortcuts. Settings still live in your Windows profile, so moving the executable does not lose them.

The first window

The network deck sits under the title bar. Start with Auto for a healthy route, or None for a direct connection. Open Settings → Basic to sign in to a provider. There is no OpenDeath account and no separate OpenDeath server.

Routes

A route is how OpenDeath reaches the network. Each mode has its own setup and status; switching modes does not close the current session.

ModeWhat it needsNotes
AutoA configured routePicks a healthy mode and falls back when one stops answering
WARPCloudflare WARP clientInstall it from the wizard or from Cloudflare
TorNothingBundled Tor Expert Bundle; no daemon to configure
HTTP ProxyOne proxy or a host:port listPaste one entry per line; the app rotates through the list
SOCKS5A local or remote SOCKS5 serverEnter host and port; authentication fields appear when needed
Route64WireGuard and an IPv6 route listRotates source routes for IPv6-capable providers
MullvadMullvad VPN clientSign in to Mullvad, then select the route
WindscribeWindscribe clientSign in to Windscribe, then select the route
NoneNothingDirect connection; useful for diagnosis or a trusted network

Fix connection diagnoses the selected route, rebuilds it if needed, and reports the result. Status shows the current exit IP and route health. Neither button restarts the session.

Recovery controls

Reset limit

Clears the current allowance and retries the last prompt in one action. Use it when a provider reports a free limit but the route itself is healthy.

Auto-rotate

Watches for a free limit, finds another exit, verifies it, and sends continue to every waiting chat. It makes up to 50 attempts, remembers burned exit IPs for 24 hours, and stops when the route is healthy. A per-chat delay and a rotation lock prevent the same limit from triggering twice.

Relaunch resume

Waiting chats are written to pending.json. On the next launch OpenDeath restores them and resumes once the new route is ready. If you close the app in the middle of a rotation, the next launch continues from the last saved state.

Fast mode

Skips the pre-check before rotation. It is quicker on a network you trust and slower to fail on one you do not. Leave it off unless you know the route pool is healthy.

Personalization

Settings → Personalization controls the theme, background, rainbow accents, and text color. The default is dark. Light and system themes are available, and every color control keeps body text readable.

Voice dictation is available anywhere the composer is. The keyboard shortcut is shown in the composer menu; it can be changed in Settings.

Data, updates, and uninstall

OpenDeath keeps user data under your Windows profile:

%APPDATA%\dev.opendeath.desktop\
├─ settings\        theme, routes, and preferences
├─ pending.json     chats waiting for a new route
├─ logs\            local diagnostics
└─ cli\             the bundled engine version

The installed app lives in %LOCALAPPDATA%\Programs\OpenDeath by default. The portable build extracts to a temporary folder each time it runs.

Updates are manual. There is no self-updater and no background download. New builds are published on the download page; install the new setup over the old one, or replace the portable executable.

Uninstall from Windows Settings → Apps, or run the uninstaller in the install folder. It removes the app and shortcuts. Your settings and waiting chats are kept so a reinstall can find them; delete %APPDATA%\dev.opendeath.desktop to remove them as well.

Troubleshooting

The setup says OpenCode Desktop is missing

Install the official OpenCode desktop build, then run the OpenDeath wizard again. If it is already installed in a non-standard location, install it per user or add its uninstall entry so the check can find it.

A route will not connect

Press Fix connection and read the Status panel. For WARP, Windscribe, or Mullvad, confirm the client is installed, running, and signed in. For Tor, wait for the bootstrap line in Status; first start can take a few seconds. If you do not need the route, switch to None and continue working.

A tab says the session cannot be found

The tab points to a session that was deleted on the server. Current builds close that tab automatically after a moment; you can also close it with the button in the panel. Your other tabs and settings are not affected.

SmartScreen blocks the installer

The build is unsigned. Verify the SHA-256 against SHA256SUMS.txt, then choose More info → Run anyway. Do not run a file whose hash does not match.

The counter or a download link fails

Release files are served from this host. If a download stops, resume it or start again; the checksum is the same. If the page cannot reach the counter, it shows the last known value or the baseline of 59 rather than blocking.