July 14, 2026

Rush CLI 0.2.33

Name: Rush
Author: Phoenix Horizon, Inc.

Install

macOS / Linux

curl -fsSL https://cdn.getrush.ai/install.sh | bash

Windows

irm https://cdn.getrush.ai/install.ps1 | iex

Homebrew

brew install phnx-labs/tap/rush

Debian / Ubuntu

sudo apt install rush-cli

Already installed?

rush upgrade

Fixed

Channel agent failures now surface the real error instead of a silent "exit status 1". The daemon received the subprocess's execution_error event but dropped it as an "unhandled event type", so a failed run (e.g. an LLM/proxy rejection) was recorded only as exit status 1 and the channel got a generic "I ran into a problem" reply. The daemon now captures the classified error and scrubbed details onto the execution record (visible in logs / agents sessions) and routes the user-safe classified message to the channel.
rush cloud run's interactive agent picker now offers only dispatch-backed coding runtimes (claude, codex). The picker previously listed gemini and droid, which could be selected but failed at submit time with Unsupported agent (RUSH-1682).
Every agent run no longer shows "Couldn't finish" with no response (RUSH-1699). Session messages.jsonl is encrypted at rest (RUSH-1375, Encryption: true), but FinalizeSession read the file raw and json.Unmarshal failed on every encrypted line — so it never saw the execution_end status and defaulted every session to outcome="incomplete" (which the app renders as "Couldn't finish", with the assistant response hidden). Finalize now decrypts each line via the new memory.DecodeSessionLine (machine-bound crypto, plaintext fallback) before parsing, so completed runs record outcome="success" with their response, and RecoverIncompleteSessions heals sessions mislabeled by earlier builds.
rush build output can be run directly again: rush run ./<agent>.rush on a locally-built container no longer fails with "container signature verification failed: footer marker not found" (RUSH-1364). rush build seals an unsigned container, but the direct-path run required a registry signature. Direct-path execution now opens unsigned containers (matching inspect/dev verify), while registry-installed agents (run by slug) stay signature-verified — their signature is still checked at install time and on every by-slug run.

Security

rush cloud run now resolves the correct GitHub App installation per target repo (RUSH-398). A cached installation ID (which records no owner) was returned unconditionally, so a user with multiple installs (e.g. personal + org) who connected once and then dispatched against a differently-owned repo got the wrong, non-matching installation. The cache is now a fallback used only when there is no repo owner/name to resolve against.

Downloads

Platform	Binary	SHA-256
macOS · Apple Silicon	download	—
macOS · Intel	download	—
Linux · x64	download	—
Linux · arm64	download	—
Windows · x64	download	—
Windows · arm64	download	—

Checksums are published for the current latest release. Verify older binaries against rush --version after install.