Skip to content

Release Channels and Updates

Ryan Stoffel edited this page Oct 29, 2026 · 1 revision

Release Channels and Updates

Parallax publishes two channels as GitHub releases. Both are built from develop. A stable release is a nightly that was promoted, or a fix that couldn't wait for the next nightly.

Channel When it's published Tag On GitHub
Nightly A check runs every half hour. It publishes when develop has commits since the last nightly and that nightly is at least six hours old. v<version>-nightly Prerelease
Stable When a maintainer promotes the latest nightly v<version>, the same version as the nightly it came from Marked Latest

Each release's notes list the pull requests merged since the previous release of the same channel. Why it works this way: 0051 and 0028.

Versions

The version is the UTC time of the release's commit, written YYMM.1DDHH.1MMSS. A commit made on 2026-09-30 at 17:45:12 UTC is 2609.13017.14512: year and month, then a 1 before day and hour, then a 1 before minute and second. A nightly adds -nightly.

Versions rise with time, and a stable release sorts above the nightly it was promoted from. Why: 0030.

Your version is in Settings > General > About > Version.

Which channel you're on

The build you installed is the channel. There is no setting for it.

  • A version ending in -nightly follows nightlies. Any other version follows the release marked Latest.
  • On macOS and Windows, a nightly is named Parallax (Nightly) and has its own icon.

To switch channels, install the other build. The install commands and the AUR package install nightlies. Stable installers are on the releases page, under the release marked Latest. Both builds use the same data folders, so your threads carry over.

Updating the app

The Update button in the sidebar's footer shows a dot when something can be updated. Hover it to see what, with the release notes under "What's new in Parallax". Click it to open the update dialog, choose what to update, and press Update all. With some unticked, the button reads Update 2 selected, or however many you chose. Parallax restarts last, if you chose it. If threads are running, the dialog says how many will be interrupted and offers Continue threads after restarts.

The app checks for a new release at launch, every 30 minutes, and when one of its windows comes to the front. The checks read GitHub's releases feed.

A release downloads when you choose to update it, and installs when Parallax restarts or quits. Settings > General > Updates changes this:

Setting What it does
Download updates automatically Downloads a new release as soon as it's found, so updating only restarts the app
Check for provider updates Checks each computer's Claude Code and Codex every 30 minutes and lists new releases under Update
Update providers automatically Updates Claude Code and Codex as soon as a new release is found. Running threads keep going.

Each OS's build is added to a release as soon as it finishes, so a release can appear before your OS's build is on it. Until it is, the app reports "The newest release has no update for this computer." and picks the update up at a later check.

By OS

  • macOS: the update must be signed like the installed app. Release builds are signed, and the dmg is notarized after the release is published.
  • Windows: builds are unsigned, and they still update.
  • Linux: only the AppImage updates itself. The AUR package updates through your AUR helper, and the app says "Updates work only in the AppImage."

Updating plxd

On this computer

The app carries its own plxd. After an update, a plxd from the previous version may still be running, and the app replaces it with the new one. When plxd runs as a login service, the app waits until no agents are running before it restarts the service. On Windows, the installer stops plxd itself.

On other computers

Once this computer's plxd runs the app's version, the app updates every connected SSH host, paired computer, and Parallax Connect device whose plxd is older. Each one is tried once per launch.

  • A recent plxd updates itself. It downloads parallax-plxd-<version> for its OS from the release, checks its SHA-256, and installs it. It restarts once no agent's turn is running there. The computer needs HTTPS access to github.com.
  • An SSH host with an older plxd gets the same download over ssh, after its agents finish.
  • For a plxd too old for either, the app says what to do instead: update Parallax on that computer, or on Linux run npx plx-connect setup --channel <channel> there.

A notification says "Updated plxd on <computer>" when it reconnects on the new version, or "Couldn't update plxd on <computer>" with the reason and Retry. plxd never moves to an older version.

Updating from the update dialog restarts a computer's plxd at once instead of waiting for its agents.

Why it works this way: 0066 and 0072.

Terminal only

A terminal-only install updates when you run its install command again. See Terminal.

When an update fails

The Update button's card shows the reason. Troubleshooting lists each message.

Clone this wiki locally