June 19, 2026

Rush CLI 0.2.18

Fixes a class of agent failures where an installed agent whose local decryption key (DEK) had drifted out of sync with its container version would fail to run — most visibly, every inbound iMessage to Rush replied "I ran into a problem and couldn't respond."

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

DEK keystore misses now self-heal. rush run <agent> resolves an installed encrypted container and looks up its DEK in the local keystore (keychain + ~/.rush/keys). When the installed container version and the stored DEK version drifted apart (e.g. a partial/cross-version update left the 1.0.14 container with only a stale 1.0.15 key), the bare-name run path failed hard with "DEK not found … reinstall the agent". The daemon turned that into the channel fallback "I ran into a problem and couldn't respond", so every inbound iMessage (1:1 and group) failed while path-loaded scheduled runs kept working. The bare-name path now refetches the DEK from the prix/api registry (its source of truth) and re-caches it — matching what the direct .rush-container path already did — so a version-desynced install recovers on the next run instead of bricking the agent.

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.