v0.2.0

What's new

• Web client. Remote Agent now runs in a browser too, with everything the apps do: sessions, approvals and questions, images, diffs and revert, slash commands, and the light and dark themes. Run it from source (cd web && npm install && npm run dev) or from the Docker image ghcr.io/buldezir/remote-agent-web; web/compose.example.yaml runs it on port 8080.
• rad pair --web <url> prints a link that opens the web client at <url> with the pairing filled in.
• New config option web_origins. rad answers browsers only from the pages listed there. The default lets in pages on localhost and 127.0.0.1; to open the web client from another address, add it, for example web_origins: ["localhost:*", "127.0.0.1:*", "my-server.local:8080"]. The apps aren't affected.
• A page served over https:// can't reach rad on plain http://: serve the web client over http:// too, or put rad behind HTTPS, for example with tailscale serve.

Downloads

• rad (rad-<os>-<arch>.tar.gz): the server for Linux and macOS. Unpack it, put rad on your PATH and run rad serve.
• Remote Agent (Remote-Agent-macOS-arm64.zip): the client app for the Mac.
• Remote Agent Server (Remote-Agent-Server-macOS-arm64.zip): the menu bar app that runs rad on a Mac.
• Web client: the Docker image ghcr.io/buldezir/remote-agent-web, tagged latest and 0.2.0. web/compose.example.yaml runs it.

Both Mac apps need macOS 27 on Apple silicon. They are signed ad hoc, not notarized, so macOS blocks their first launch: allow them under System Settings › Privacy & Security, or run xattr -dr com.apple.quarantine on the app. After each update, macOS asks again for the Server app's permissions and for the client's access to its saved pairing tokens.

Full Changelog: v0.1.3...v0.2.0