Rush CLI 0.2.35

rush install <renamed-alias> now actually installs (BUG-1). Installing a registry agent by a renamed alias (e.g. prix/deep-researcher, which redirects to prix/rabbit-hole) printed Installed … with exit 0 but wrote nothing to ~/.rush/agents/. The container was written under the alias slug directory, which the rename-cleanup step then deleted. The container directory now tracks the canonical resolved agent, and the cleanup never removes the directory it just wrote.

rush init <dir> writes a valid agent name (BUG-3). rush init /tmp/my-project used to put the full path in name:, so the fresh project failed rush build with an invalid-name error. The name is now derived from the directory basename and sanitized to a build-valid two-word slug.

Missing external-runtime dependency is reported at default verbosity (BUG-5). Running an external-runtime agent (codex-cli, copilot-cli, …) with its vendor CLI absent printed a bare Error: Agent run failed; the honest missing dependency: … message only showed under --verbose. The actionable message now surfaces at default verbosity.

iMessage stays reachable after a transient relay disconnect (RUSH-1959). ImessageGateway.Start() gated its self-healing goroutines (readLoop/reconnectLoop/pingLoop) behind the first WebSocket dial succeeding, so a single failed initial connect (a network blip, prix-api mid-deploy, a DNS hiccup) permanently killed the channel for the life of the daemon with no retry — the menu bar still showed "Daemon: running" while the relay correctly reported the user offline. Start() now treats the first dial as best-effort and always starts the goroutines; reconnectLoop (already polling every 10s) picks up the retry.

Cloud transcripts keep every assistant and tool turn (RUSH-2533). A cloud pod wrote messages.jsonl encrypted at rest with a machine-bound key that nothing in the pod could later read, so a finished cloud run came back with its history stripped. At-rest session encryption is now disabled inside the ephemeral, isolated pod, so the full transcript survives the run.

rush whoami no longer says "Not logged in" while the daemon holds a fresh token (RUSH-1918). Post-RUSH-632 the on-disk access_token is always blank (the token lives in the OS keychain). When the CLI's own keychain read missed or was denied, GetValidAuthConfig() bailed on the empty on-disk token before consulting the daemon — the sole token owner, which can serve a fresh token from its in-memory cache. whoami (and the daemon-aware resolver used by rush run / scheduled runs / rush http) now bail only when there is no session identity at all; a present session whose token is only locally unreadable falls through to the daemon consult, and whoami distinguishes daemon-down from signed-out.

rush daemon status reports the real last-refresh outcome, not a fantasy clock (RUSH-1918). The status view derived a confident "Next token refresh" time purely from the daemon's start time, so it printed a healthy future clock even while every refresh was failing. The daemon now records the outcome of each refresh tick and the status view prints Last token refresh: HH:MM:SS (ok) or ... (FAILED: <error>).

Sign-in stays put on a dead session (RUSH-1843). Reconciled an auth split-brain that looked connected while silently failing, and surfaced a clean re-auth prompt instead of failing silently.

Agents are no longer told they're connected to OAuth accounts they have no tools for (RUSH-1035). The connected_<provider> prompt vars are now gated by the agent's ux.yaml declaration — the same signal the builder uses to inject first-party Google/Microsoft/Twitter/LinkedIn tools — so an agent that doesn't declare a provider is no longer injected with that account's context (it had no tools for it, so it could only hallucinate the capability). Declaring agents also report only their declared scopes.

Registry agents run headless without a running daemon (RUSH-1310). A manual cloud run of a registry agent no longer dies on "rush daemon not running".

Headless token refresh no longer wedges on Linux (RUSH-632). The keychain write that persists a refreshed session token could block forever on a box with no unlocked Secret Service collection, so the token was fetched but never saved and expires_at stayed frozen. Every keychain write is now bounded (5s) and a hung write degrades to the plaintext-user.yaml fallback, so rush refresh-tokens and rush run succeed and persist the new token.

Friendlier errors instead of raw Go strings. Quota-exceeded runs show the upgrade message instead of a bare "Model call failed" (RUSH-1841); a daemon round-trip timeout is classified as transient so users see "temporarily unavailable — check your connection and try again" instead of a leaked context deadline exceeded; and rush cloud computers routes its timeout through the shared error classifier ("Request timed out — try again").

The daemon reaps an orphaned instance by pidfile (RUSH-1844, RUSH-1855). rush daemon stop / restart now recover instead of wedging against a detached daemon, and re-bootstrap launchd so the daemon restarts onto the re-signed binary.

rush uninstall cleans up user-created agents (RUSH-1917). Uninstalling now removes the agent's metadata.db row, so a re-created agent of the same slug no longer collides with a stale record.

rush cloud accounts remove/edit accept a short-ID prefix (RUSH-2124). You can pass the short ID shown in rush cloud accounts list instead of the full UUID.

Download as PDF no longer crashes on hardened (garble) release builds (RUSH-1840). The html/template palette is denormalized so field reflection survives obfuscation.

rush build accepts registered first-party tool groups such as box_tools and dropbox_tools during catalog validation.

Smaller CLI-surface fixes. Session-storage init failures emit a structured error_code rather than a raw Go string (RUSH-1838); rush tool accepts -v and applies auth config to dual-registered tools (RUSH-1845); rush exits 1 when signed out and emits side_effect=unknown in run meta (RUSH-1848); rush init scaffolds an agent that passes rush build without a gallery (RUSH-1847); rushx --version prints the version instead of failing with "rushx takes a single agent"; and rush connection disable <name> --for <slug> rejects a connector that was never installed instead of writing an orphan disabled=1 row.