Repository navigation
Relay 0.1.8
Relay 0.1.8
Relay 0.1.8 adds chat wallpapers, context usage, file attachments, and text file
previews. This release includes separate Windows desktop client and backend
downloads.
Highlights
- Chat wallpaper: choose one device-local image in Settings > Wallpaper,
adjust opacity with live preview, and save. Desktop and mobile keep the
original image; chat chrome, messages, and Home cards share an acrylic tint.
Display-sized decoding and a shared blurred backdrop keep scrolling smooth. - Context usage: the line above the solo-chat composer shows used tokens
and the model's context window, such as42k / 200k, and refreshes after
compacting a conversation. - Files in your workflow: attach files through the composer's + menu
without sending automatically. Open text files in a read-only preview with
syntax highlighting.
Other changes:
- Rename any session except Main. Copy settled messages or edit your own
message back into the composer. - Home has a What's new entry. Settings > About can check GitHub for a newer
version without downloading it. - Update CLI is available in the composer's + menu.
- Replies Claude starts on its own can be stopped and no longer spin forever.
- File access checks cover dot-suffixed copies of sensitive paths and symlink
destinations. Oversized directory downloads stop scanning at the size limit. - Backend setup verifies the native terminal dependency and supports npm 12's
install-script policy. - Quickly created messages keep distinct IDs, avoiding message action and
rendering mix-ups on Windows.
See the changelog
for the complete change list.
Downloads
| Asset | Purpose |
|---|---|
| relay-windows-x64-v0.1.8.zip | Windows x64 desktop client. Extract the entire archive and run relay.exe. |
| relay-backend-windows-x64-v0.1.8.zip | Windows x64 backend with Node.js 24.15.0, npm, locked production dependencies, and setup/service/credential commands. |
| relay-android-v0.1.8.apk | Existing release-signed Android client, version 0.1.8, version code 18; retained unchanged. |
| relay-backend-setup-v0.1.8.tar.gz | Existing source setup bundle with Linux, macOS, and Windows adapters; retained unchanged. Requires host Node.js and dependency installation. |
| SHA256SUMS | SHA-256 checksums for all four downloads above. |
Windows build sources on the 0.1.8 branch:
- Desktop client:
df2f097,
including the Windows message ID fix found during release validation. - Backend:
5532e35.
Windows backend setup
-
Extract the entire backend ZIP to a permanent, writable directory. Keep
server,backends, andruntimetogether. -
Install at least one supported agent CLI on this host: Claude Code, Codex,
OpenCode, or Hermes. Complete its login or provider setup on the host. -
Open PowerShell in the extracted directory and run:
.\setup.cmd .\status.cmd
-
Choose a port and network mode, then create an encrypted device credential.
Import the generated.relay.jsonor.relay.pngfromserver/credentials
in the Relay client and enter the passphrase.
Node.js, npm, and backend dependencies are included. Agent CLIs and optional
cloudflared are installed separately. The backend archive contains no local
deployment state, credentials, or compiled Flutter client. Setup creates a
Scheduled Task that starts Relay when the current Windows user logs in.
Use these commands from the extracted directory:
.\start.cmd
.\stop.cmd
.\status.cmd
.\credential.cmd --url https://YOUR-BACKEND
.\uninstall.cmdUse HTTPS for public access. Quick Tunnel addresses can change after restart;
generate and import a new credential when the address changes. Uninstalling
stops the service and removes its login task while retaining configuration,
credentials, and history. See the bundled README for updates and log locations.
Android signing
The retained Android APK uses Relay's release certificate, SHA-256
3e4dea3f6cd50fd30b25a168ba9eb2c14a14ecb8f786ffcb4e3c1836275a720f.
When upgrading from an older debug-signed APK, uninstall it once before
installing this version, then import the machine credential again. Releases
using this release key can update in place.
Windows build validation
flutter analyze --no-pubflutter test --no-pub: 145 passed.flutter build windows --release --no-pub- JavaScript syntax checks for all 71 tracked backend files.
- Backend test suite: 276 passed, 2 skipped, no failures.
- Packaged backend start, stop, status, credential command, HTTP authentication,
and a real Windows PTY session through the terminal WebSocket. - Archive contents and SHA-256 checksums checked; no local deployment state or
signing secrets included.