Skip to content

v0.3.0

Choose a tag to compare

View all tags
@buldezir buldezir released this 11 Oct 00:23
· 31 commits to main since this release
v0.3.0
2c142f9

What's new

  • rad update installs the latest release over your rad. It checks the download against the release's SHA256SUMS and keeps the previous binary as rad.old next to it. rad update --check only tells you whether a newer release is out.
    • If rad runs as the background service from rad install-service, the service is restarted and rad update waits for the new version to answer.
    • A restart interrupts running turns, so while a session is busy (a turn running, or an approval waiting) it stops before downloading and names the sessions. --now updates anyway.
    • A rad running in a terminal needs restarting by hand. A build from source isn't replaced without --force.
  • Update rad from the Server app. When a newer release is out, the menu offers Update rad to …. The app checks once a day, or when you choose Check for Updates….
    • The app downloads the new rad to ~/Library/Application Support/Remote Agent Server/ and restarts rad from there. It asks first if that would interrupt a session.
    • The app itself doesn't change, so macOS keeps the permissions you gave it, and they apply to the new rad too.
    • When you later install a newer app, its own rad takes over again.
  • The Server app's menu shows which version of rad is running.

Releases up to 0.2.0 don't have rad update, so install this one by hand. From then on, rad update and the Server app's menu do it.

Downloads

  • rad (rad-<os>-<arch>.tar.gz): the server for Linux and macOS. Unpack it, put rad on your PATH and run rad serve. From then on, rad update installs new releases.
  • 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.3.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. To update only rad, and keep those permissions, use Update rad in the Server app's menu.

Full Changelog: v0.2.0...v0.3.0

Assets 9
Loading