Skip to content

Releases

v2.21.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 21:12

v2.21.0 — Relay balances, terminal provider sync, and resilient presets (2026-11-13)

  • Discover balance APIs on supported third-party relay panels, including new-api, sub2api, legacy billing endpoints, and the common user-balance endpoint. Cache the detected panel and distinguish account balances from token balances. Unlimited-token markers and HTML error pages are not reported as usable balances.
  • Add a provider-card action to sync a selected Claude or Codex line to the local terminal configuration. Back up the existing files before replacing them, preserve unrelated settings, and show which line the terminal currently uses. OAuth account lines cannot be copied through this action.
  • Apply the available lines of a run configuration preset on web and mobile, list every skipped line, and reject the preset only when no usable line remains. Mark references to deleted providers and prevent saving those references back into a preset; applying a preset leaves its stored definition unchanged.
  • Default Claude lanes to a one-hour prompt-cache lifetime while preserving explicit prompt-cache settings.
  • Add a clear-all action to the expanded notification deck. Refresh background activity by querying only the displayed task IDs in bounded batches.
  • Keep background continuations moving through an available lane in the same CLI family when the current lane is exhausted. Preserve exhausted-pool diagnostics and stop unattended retries when the run requires human input.
  • Read orchestration state through indexed SQLite queries with terminal receipts and bounded retention, while keeping full record bodies available for detail views and rollback exports. Append chat history tails and observe code revisions in Rust, and use cross-process writer leases to prevent workspace release, snapshots, or finalization while a writer still owns the workspace.
  • Move provider management, CLI switching and version checks, quota rules, and system and history-scan routes into Rust. These migrations retain necessary Node adapters for existing SDK, process, filesystem, and streaming operations until equivalent Rust lifecycle behavior is verified. Other unmigrated host routes remain in Node. The new Node-free runtime image validates the Rust binaries in CI; the complete server still requires the remaining Node host.
  • Update the mobile app to 2.44.0 (build 192), including the preset availability and partial-application improvements.

v2.20.2

Choose a tag to compare

@github-actions github-actions released this 11 Nov 17:13

v2.20.2 — Unattended tasks, resilient routing, and Rust request handling (2026-11-11)

The v2.20.0 and v2.20.1 candidates did not reach a published Release. Both tags are preserved. The v2.20.1 release checks exposed timing assumptions in regression fixtures; this candidate corrects those checks and retains the feature updates below.

  • Validate shutdown drain grace against the remaining shared budget after checkpoint work, rather than an exact elapsed-time log string. Give streaming-timeout fixtures room for admission and connection startup while continuing to require correct timeout attribution, a single outcome, and upstream connection cleanup. Production timeout settings are unchanged.

  • Include the required Rust gateway in fresh-install and regression containers, validate transcript paths using the host platform, and remove a redundant loop rejected by Rust 1.99 Clippy.

  • Keep the gateway process fixture alive under GNU command-line parsing and route isolated Claude completion tests through the fake SDK engine so they never start the real model client.

  • Keep the stale restart lock's recovery guard until the replacement manager identity is recorded, preventing concurrent recovery requests from starting duplicate source servers. Retain the existing shell launcher and Node process-inspection adapter as the migration bridge: moving the restart lifecycle during this fix would also change bootstrap and process-drain behavior. Migrate them together once the Rust host preserves those lifecycle contracts.

  • Reconcile queued chat messages with the transcript so reconnects and message acknowledgements do not leave duplicate entries in the conversation.

  • Switch to the selected CLI before saving an automatic-provider configuration, preserving the provider selection for that CLI.

  • Share stopped-writer evidence across workspace checks and batch code-revision file hashing in Rust, reducing repeated scans while retaining publication evidence checks. The Node host remains a narrow adapter for existing repository and workspace lifecycle interfaces until those interfaces move to the Rust host.

  • Make release regression fixtures portable across Windows, macOS, and Linux, including temporary home directories, line endings, SQLite handle cleanup, gateway-owned routes, and streaming timeout attribution.

  • Add unattended supervision on web and mobile. Set a goal, acceptance criteria, and a time limit; MultiCC evaluates progress and queues follow-ups until the goal is reached, time expires, or human help is required. Pause to take over, resume when ready, and clear a finished run. Recover from transient capacity and host interruptions with bounded retry delays and visible status.

  • Improve Auto Provider continuity. An optional low-quota rule switches to the line with the most remaining quota when the current line falls below 20 percent, while preserving configured priority otherwise. A continuation can leave an exhausted lane, and run configuration presets can be updated in place on web and mobile.

  • Select a dedicated network exit before opening a Claude or Codex account login link, so account authorization and later requests use the selected route. The existing Node network and OAuth adapters remain necessary for the current login clients; move them when the Rust account host provides equivalent authorization and proxy behavior.

  • Keep background work and messages delivered during an active turn under one Rust runtime. Preserve query outcomes, delivery acknowledgements, route attribution, and progress through background completion and reconnects, and avoid finishing a turn while its queued work is still pending.

  • Persist chat history asynchronously in Rust and serialize history mutations, rotation, and transcript pruning. This also fixes recursive append callbacks and makes durable delivery checks wait for their history writes.

  • Route desktop and standalone startup through the Rust gateway on macOS, Windows, and Linux. Move authentication, selected API routes, workspace subscriptions, session persistence, provider routing decisions, and secret redaction into Rust while retaining the existing Node adapters for unmigrated host and SDK interfaces.

  • Consolidate Claude chat execution on the Agent SDK and normalize retired lane aliases in saved run configurations. The Node SDK adapter remains the compatibility boundary until the Rust host can support the same SDK transport and lifecycle.

  • Update the mobile app to 2.43.0 (build 191), including unattended controls, clearer live progress, and the latest Auto Provider settings.

v2.16.0

Choose a tag to compare

@github-actions github-actions released this 06 Nov 04:20

v2.16.0 — Windows desktop agent preview and clearer live progress (2026-11-06)

  • Add the first Windows desktop agent in Rust. It captures the primary screen, sends pointer and keyboard input, and connects to the remote host through a per-user named pipe. The user-level installer manages login startup without an administrator service and safely replaces an existing installation. The agent refuses input on locked and secure desktops and in password fields. Windows CI covers the pipe protocol and installation, while real desktop control still requires hands-on validation before it is described as fully verified.
  • Improve Linux X11 remote control with horizontal scrolling, modifiers, safer pointer handling, and broader conformance and installation checks. The existing C/Xlib agent remains the platform adapter because replacing its display and input layer before equivalent Rust conformance and real desktop checks would expand migration risk; replace it when those checks pass.
  • Keep live chat progress in the streaming reply: show background task activity beside the generation indicator and route attribution, restore that state after a reconnect, and keep the final attribution on the completed message. Codex background events now provide more useful task progress.
  • Refresh Windows CLI discovery and Git probes so installed tools and their paths are found reliably, and make doctor reports preserve the underlying model error.
  • Remove stale CLI session homes through the current Node host lifecycle adapter to prevent abandoned runtime data from accumulating. This adapter remains limited to the existing session-home cleanup contract; move the scan and cleanup to Rust when the Rust host owns CLI home lifecycles and its asynchronous filesystem path has parity coverage.

v2.15.6

Choose a tag to compare

@github-actions github-actions released this 04 Nov 08:10

v2.15.6 — Run preset and provider routing fixes (2026-11-04)

The v2.15.4 candidate stopped before a Release was created: the deterministic
CI suite found duplicate CLI display-name maps in two browser modules. Its tag
is preserved. The v2.15.5 candidate also stopped before a Release was created:
Linux Rust parity rejected an unnecessary question mark in provider-error
serialization. Its tag is preserved; v2.15.6 carries both fixes.

  • Save Auto Provider run configurations as named presets and use them across web and mobile. The Rust core validates, normalizes, and merges presets while the existing Node host adapter handles local persistence and session injection. Applied named presets can now be updated in place without creating duplicates; the current session still changes only after its run configuration is saved. Move host persistence and injection to Rust once the Rust host has equivalent session and storage contracts.
  • Let the Auto Provider pool use native lines for Command Code, Qoder, CodeBuddy, Gemini, Pi, DeepSeek, and Grok on web and mobile. Each CLI owns its account and model catalog; the existing Node CLI and provider adapters bridge these lines into cross-CLI routing until those host interfaces move to Rust. Ordered pools return to a recovered higher-priority line after a quota reset instead of staying on the fallback.
  • Keep a reopened chat's status accurate: restore the persisted API error bar, show user cancellation as cancelled rather than an upstream API failure, and preserve the stale-verdict marker during a repaint. A reconnect also displays attributed streaming frames before the first route event instead of hiding the live reply.
  • Recover a Codex native session when its saved provider is no longer configured, and find the macOS Chrome remote-debugging Allow button inside nested dialog groups. The Codex bridge is a required Node app-server adapter until native host session recovery moves to Rust.
  • Refresh an OpenCode session's worktree directory before spawning its next turn, and probe a borrowed Claude line with a model the lender actually serves. Official Claude relay sharing now supplies its known model list when the account stores no default model.
  • Read vendor-native CLI labels from the shared provider catalog in the browser Auto Provider editor and model picker, so a renamed lane has one display name across the app.
  • Recognize OpenCode context-limit errors across ACP and legacy transports, stop retries that would replay an oversized prompt, and show the underlying reason consistently.
  • Use the Rust core to read OpenCode's native usage and model limits before rotating a full session; keep older messages out of the current turn's usage and show the model context in chat. The existing Node code remains a narrow CLI and session bridge until the Rust host owns those interfaces.
  • Update the mobile app to 2.41.3 (build 189).

v2.15.3

Choose a tag to compare

@github-actions github-actions released this 03 Nov 16:13

v2.15.3 — Honest quota bars, sturdier error handling, and faster computer switching (2026-11-03)

  • Keep an API error out of a finished answer. When one or more "API Error: ..." envelopes are glued onto the end of a reply, including chains produced by repeated background wake-ups, the transcript now keeps only the real answer, and the resident Claude lane's synthetic API error message is dropped when the turn already has output. The retry notice also recognizes a status-only envelope as an upstream interruption.
  • Give every lane the same error treatment. CodeBuddy, Kimi, Qoder, and the ZCode bridge now report a terminal failure with its HTTP status, so a 429 or a quota wall is classified like the other lanes, and a 429 that only the CLI reports afterwards still parks the account so Auto stops choosing it. A background wake-up that fails now releases the held turn as a failure instead of hiding behind the held answer, while a later successful wake still wins.
  • Release the quota guard for one revalidated turn when its blocking reading is older than a configurable age (30 minutes by default), and kick a quota re-read so the cache supplies the verdict. An account that was upgraded or topped up no longer stays blocked until the window resets, and the guard settings now take a maximum reading age. Codex quota reads now refresh an expired token once and retry.
  • Mark inferred quota percentages. When a window's reset time passed after the last measurement, bars across Claude, Codex, OpenCode, Qoder, Kimi, Zhipu, and Ark show it as full with a leading tilde and a tooltip note, instead of recycling the dead window's number as if it were a fresh reading.
  • Keep the token-rate chip calm while the turn is alive. A fresh server heartbeat or a running background task (including rows in the live panel) reads as "task running", and the amber and red fuses are measured in minutes rather than seconds. The background activity line also holds a task through a short grace period when the server snapshot misses it, so the row no longer blinks out.
  • Show the route attribution while the answer is still streaming. When auto routing picks a lane, the "produced by lane - provider - model" line is attached to the streaming bubble as soon as the route event lands and is replaced in place by the final attribution at turn end, so a mid-turn failover never adds a second line.
  • Make switching computers faster in Air. Directory lists are cached and warmed in the background, the Rust proxy keeps pooled connections per computer with a retry that re-resolves on a connect failure, and a stale directory grid stays visible with a warning when that computer is unreachable. With several computers paired, the new-task composer gains a computer pill that chooses where the task is created, lists that computer's own directories and CLIs, and opens the task there afterwards.
  • Treat the old handwritten opencodego line id and the built-in opencode-go id as the same lane on web and mobile, rewriting stored model prefixes when a model list is refreshed so an old session no longer looks empty.
  • Stop a turn rule from announcing a task as goal achieved. A rule verdict now carries no sub-state and leaves the task phase alone; only a manual mark or the later model attribution sets the badge. The local-resource guidance now says to copy an image to the durable assist folder before linking it, and @anthropic-ai/claude-agent-sdk is updated to 0.3.317.
  • Update the mobile app to 2.41.2 (build 188).

v2.15.2

Choose a tag to compare

@github-actions github-actions released this 03 Nov 09:34

v2.15.2 — Live relay model lists, visible background activity, and a quieter debug prompt (2026-11-03)

The v2.15.0 and v2.15.1 candidates stopped before a Release was created:
the remote-debugging prompt dismisser in the CDP gateway first missed a
rustfmt pass and then left its macOS-only timing constants ungated, so the
cross-platform source check failed on Linux and Windows and the desktop
packaging job never ran. Both tags are preserved; v2.15.2 carries the same
changes with the formatting and platform gates fixed.

  • Fetch relay providers' model lists live. GET /api/providers/:id/models asks the provider's own stored gateway for its models endpoint (the browser never supplies a URL), the picker shows the static list first and rebuilds when the live catalog lands, failures keep the static list, and a codex relay's refresh-models action no longer fails with an account-lane error.
  • Show what the background is doing while a turn streams without new text. A live status line under the breathing dot names the oldest running background task, walks its elapsed time, and shows its latest output; the line goes away when the turn ends.
  • Auto-dismiss the Chrome "Allow remote debugging" prompt on macOS. The CDP gateway clicks Allow through the accessibility API during the handshake window when it has permission; when it does not, nothing changes and the manual path with backoff stays exactly as it was.
  • Put the Air sidebar's recent tasks on one rule for web and mobile alike: order by the most recent message time, with no opened-first or current-directory weighting.
  • Fold the Air brand into the directory card so the header shows a single space switcher, with the CLI update badge beside it.
  • Update the mobile app to 2.41.1 (build 187).

v2.14.1

Choose a tag to compare

@github-actions github-actions released this 03 Nov 04:30

v2.14.1 — A per-device send key, unified computer cards, and the WorkBuddy desktop CLI (2026-11-03)

  • Add a per-device send-key preference. Keep the classic mode where Enter sends and Shift + Enter inserts a newline, or switch so Enter inserts a newline and Cmd/Ctrl + Enter sends. The toggle lives in Settings on the Air page, the chat page and the Air chat frame read the same stored value, the composer placeholder names the key that sends, and a change made in one tab applies in the others.
  • Restyle the computer directory cards in Air to reuse the console card grid, so card widths no longer drift with the length of a directory name.
  • Detect the WorkBuddy CLI embedded in the macOS desktop app, so the codebuddy lane works on a Mac even without a PATH installation.

v2.14.0

Choose a tag to compare

@github-actions github-actions released this 02 Nov 12:22

v2.14.0 — Manage multiple computers from one console (2026-11-02)

  • Add multi-computer management to the web console and mobile app. Connect computers you manage, switch between their task directories, and open each computer's settings without leaving the console. Each remote page shows which computer receives your actions and saved settings.
  • Isolate remote requests, live connections, drafts, task caches, files, annotations, and handoff packages by computer. An offline computer or revoked authorization produces an explicit error instead of sending an action to the entry computer. Keep credentials and vaults on their respective computers.
  • Pair computers using individually revocable grants. The Rust core owns computer identities, private grant storage, address validation, remote HTTP transport, and event streams. Existing Express and WebSocket SDK adapters remain as the host bridge until the Rust host supports the same tested interfaces; they do not implement the new authorization or registry rules. Both computers must run this release and be reachable at their configured addresses.
  • Move task-board rules, task storage, and card construction into the Rust core, retain the task board in memory, and synchronize changes by revision. Upgrade task data to schema v2 with layered context records; first startup displays migration progress and allows more time for the upgrade. Existing Node SDK and external-operation orchestration remains during migration and can be removed after its transaction and recovery contracts move to Rust.
  • Synchronize a hibernated workspace with its local base when it wakes. Rust checks checkout ownership, preserves a recovery ref before rebasing unique work, and keeps the original checkout when synchronization cannot proceed safely. The existing Node hibernation and repository-lease adapter remains until that lifecycle moves to Rust.
  • Improve context details in web and mobile chat, distinguishing the current context from cumulative usage and exposing the sources used for a turn.
  • Repair Windows host terminal and CLI discovery, refresh installed-tool paths without restarting the server, and preserve the user's command precedence. Retain the Node-specific process environment and terminal adapters for the current host until equivalent Rust host integration is verified. Update proxy-addr to 2.0.8 and exclude relay-key files from version control.
  • Update the mobile app to 2.41.0 (build 186).

v2.13.2

Choose a tag to compare

@github-actions github-actions released this 01 Nov 06:36

v2.13.2 — Reliable remote dragging and unified input controls (2026-11-01)

  • Unify web remote input across H.264, RFB, and compatibility views. A single finger clicks or drags, a stationary long press opens the context menu, and two fingers zoom and pan locally. Dragging near a zoomed view's edge pans the picture while keeping the remote pointer under the finger. Desktop input supports left, middle, and right buttons, both wheel axes, physical modifier keys, and composed text.
  • Add one-shot and locked modifier controls to web and mobile remote screens. Tap a modifier for the next action, double-tap to keep it held, and release held buttons and modifiers when leaving control mode, losing focus, disconnecting, or switching the view. The mobile trackpad keeps a drag active briefly between finger movements and brings its pointer back into the visible area after panning.
  • Make pointer presses, movement, release, and heartbeat handling consistent across streamed and HTTP input. The macOS Agent advances to build 9, releases stale input after an idle timeout, respects control leases and emergency stops, and shares its pointer state handling with compatibility requests. The Rust remote service validates viewer identities and normalizes modifier names and horizontal scroll input.
  • Retain the existing Node remote-input adapter only as the compatibility bridge for hosts still using the legacy remote backend. It forwards the same bounded protocol fields as Rust; remove this bridge when the Rust backend covers those hosts and cross-platform parity is verified. No new backend business service is introduced in Node.
  • Update the mobile app to 2.40.1 (build 185).

v2.13.1

Choose a tag to compare

@github-actions github-actions released this 31 Oct 18:20

v2.13.1 — Notification channel plugins, an audited secret vault, and a remote scroll rail (2026-11-01)

The v2.13.0 candidate stopped at the release notes check, because its notes
used arrow symbols outside the allowed English punctuation, and was not
published. Its tag is preserved; v2.13.1 carries the same changes.

  • Add notification channel plugins (plugin API 2). A plugin that declares engine.resident is started as <binary> serve and kept running: it restarts after 1 s, 5 s, 30 s, then every 5 minutes, is rescanned every 30 seconds, stops when it is removed, and is replaced when its version changes. A resident plugin that also declares channel becomes a delivery channel: Push settings gain a "Plugin channels" section whose new subscriptions start with only "error" and "waiting for your answer" selected, and hooks gain a "send to channel" action that checks its recipient on save. A plugin's own alerts reach web push, FCM, Bark, and webhooks once per incident and at most 10 per plugin per hour, MultiCC reports plugin-down when a plugin process stays stopped for a minute, Air shows a banner, and trigger cards that point at a removed recipient are marked. Turns interrupted by a service restart are not delivered to channels, and none of this UI appears until a channel plugin is installed. Plugins that require plugin API 2, such as the WeChat desktop notifier, can be installed from the catalog starting with this release.
  • Audit every access to the secret vault. Listing, reading a value, adding, updating, renaming, deleting, injecting secrets into a process environment, and the MCP secret tools each append one line to logs/secret-audit.jsonl (mode 0600) in the Rust core, recording the name, caller, session, and outcome but never the value, command, or URL. When the audit line cannot be written the access is refused with 503 secret_audit_unavailable, and the native module self-check now requires the audit entry point, so a stale cached module is rebuilt instead of reused.
  • Scroll the remote screen from a rail next to the picture on touch devices: drag it for continuous scrolling, or tap and hold its up and down arrows to step. The mobile app replaces its toolbar scroll buttons with the rail, and a second scroll step in the same direction is no longer swallowed. The macOS Agent gains a lease command that holds input control without sending input, for plugins, and moves to build 5.
  • Apply each CLI family's default subagent route when a session is created or switched to another CLI, without replacing a route the user picked. The web and mobile run-configuration panels keep "follow the default" when saving instead of turning it into a per-session choice.
  • Tag error push notifications with their error category, and reposition both READMEs and docs/super-agent.md around MultiCC as a Super Agent workspace that carries a goal through to delivery.
  • Update the mobile app to 2.40.0 (build 184).