v2.1.0-rc.15

AI Code Conductor Beta v2.1.0-rc.15

Beta Release (pre-release)

Fixes from the rc.14 feedback and from an independent stability review of rc.14. The in-app browser pane no longer sits in front of a page tab; the SSO Sign-in browser choice is back on managed machines with a per-user Chrome; on a Mac, quitting asks before it stops anything and reopening from the Dock works; a restarted session is no longer shown as exited; and the remote sessions you leave running are remembered even when they were the only thing open. The Usage page loads account by account and reuses the figures your open sessions already report (the primary account aside), a background run can no longer be signed out by a token refresh, and editing a config that has a session running warns you first.

Added

• The Usage page loads one account at a time, in place. Opening it shows a row per account straight away and fills each one in as its figure arrives, so a slow account no longer holds the whole page blank, and an account whose fetch fails says so on its own row instead of stalling the rest.

Changed

• An account with an open session shows the usage its session already reported, instead of asking Anthropic again; the primary account is the exception and is always fetched. Accounts with no session open are fetched one at a time, so opening the page no longer fires a request per account (which was drawing rate-limit errors), and it never refreshes a signed-in account's token behind a running session. The one exception: an account on extra usage (paid credits) still makes a single request for the credits figure the status line cannot carry, with the token it already has.
• Editing a config that has a session running warns you first. Opening the editor for an SSH config with a live or left-running session shows what is affected and reminds you that changes apply on the next launch, not to the running session, and that changing where it connects can break resuming the one you left running. Cancel, or Edit anyway; it never blocks.

Fixed

• A signed-off canvas is done, not resumable. Once you approve (or dismiss) a canvas, it drops out of the resume list and the purple "resumable" dot on the Canvas button, instead of lingering there until you formally mark it complete. A canvas you sent back (rejected) stays resumable, because a rejection asks for another round, and one still awaiting your decision stays too.
• The terminal, browser, Agent Canvas and logs pane are now one at a time. Opening the canvas while the browser was open did nothing — the browser held the foreground and the canvas never appeared. Opening any of the browser, the canvas or the logs pane now switches to it and closes the others; clicking the pane you are already in returns you to the terminal.
• A token refresh can no longer sign out an account that a background run was using. The Usage page refreshes an account's token only while nothing is using it, but headless runs (Insights, cross-account synthesis, Sentinel), cloud agents and plain shells under an account were invisible to that check, so a refresh could rotate the token under them and the next start of that run redeemed an already-spent token and logged the account out. Every such run now counts as using the account for as long as it runs, and one that starts while a refresh is in flight waits for the new token before it reads anything.
• Editing a saved SSH config can no longer point a left-running session at the wrong host. A session you leave running is remembered with the host, user, port, path and container it was left on; if you then change where that config connects, the app no longer probes or ends a session of that name on the new host. The old session shows as retargeted in Remote Resumable, with Remove as its only action, and tells you how to end it on the host it is really on.
• A saved sudo password is never typed into a container. The password kept for a container entry that needs sudo answers the host's own sudo prompt, before the container shell appears; a sudo-shaped prompt printed inside the container afterwards, by a start-up script or by something you ran, gets nothing.
• Quitting no longer hangs when the app's window has crashed. If the window's renderer died while the save-or-cancel question was up, the quit waited forever for an answer that could not come; it proceeds now. Pressing Quit a second time while the question is showing also goes through, as a second close already did.
• A left-running remote cannot be revived by text a host prints on connect. The check that asks a host which sessions still exist reads only what the host printed between the check's own markers, so a login banner or a message of the day can no longer make a finished session look alive in Remote Resumable.
• Quitting on a Mac asks before it stops anything. Cmd+Q or Quit used to shut down every session and background service first and show the save-or-cancel dialog afterwards, so Cancel handed you back an app that had already stopped your work. The question now comes first: Cancel keeps everything running, and Save shuts down only after your sessions are written.
• Reopening from the Dock works on a Mac. Closing the last window and then clicking the app's Dock icon could bring back a blank, hidden window, or take the app down, because the window's controls were being registered a second time. They are registered once now.
• Restarting a session no longer shows it as exited. The old process's exit could arrive after the new one had started and mark the healthy replacement as ended, so Ask Conductor treated the session as dead and started yet another one. An exit from a process that has already been replaced is ignored.
• Remote sessions you left running are remembered even when they were the only thing open. Leaving the last SSH session running and then closing the app forgot its Remote Resumable entry, so the next launch of that config started new work instead of reattaching. The list of left-running remotes is now kept on its own, including when you decline the resume prompt or close without saving.
• Left-running remotes on a Mac with a Homebrew tmux are no longer pruned as dead. The liveness check could not see a tmux installed outside the login PATH, took its empty answer as proof, and removed live entries; it now looks in the same places the End command does.
• Signing in again for an expired account waits for the actual sign-in. The prompt used to report success after four seconds whether or not you had signed in, because the account's email was still on disk from before. It completes only once the credentials have really changed.
• Capturing a second account signed into mid-session no longer risks the first one. The app restores the original account from a backup that was refreshed only when the session ended, so a token that had rotated during the session could be replaced by a stale one that no longer worked. The backup now follows each rotation that happens while a session on that account is open.
• A session's transcript-indexing opt-out survives save and restore. A restored session dropped the setting and was indexed regardless.
• A container that cannot be entered no longer puts Claude on the host. When the container was stopped or missing, or the engine was down, the failed entry dropped back to the host shell and the app took that for the inside of the container, so Launch Claude set up and started Claude on the host instead. The failure is recognised now, from the engine's or sudo's message or from the host's own prompt coming back: the session says so, Launch Claude refuses the host, Run again re-enters the container once it is running, and Skip remains the explicit way onto the host shell.
• The saved SSH password is no longer typed into a sudo prompt. After a key-based login the saved password was still waiting for a prompt, and a sudo prompt shaped as a bare "Password:" (the macOS form) matched it first, so the wrong secret went to sudo and the first attempt failed even with a sudo password saved. Once the login has completed, such a prompt is treated as sudo's, whether or not the session runs a post-connect command.
• Closing a container session tab ends the Claude inside the container. Container sessions never showed the End-or-Leave dialog, and the plain close only killed the local connection, which does not reliably stop the process inside the container; abandoned Claudes accumulated there. Close now ends that session's process in the container first, without touching another session sharing it.
• The browser pane stays behind whatever you open on top of it. The pane, and the claude.ai artifacts view that can live in it, are drawn by the app itself rather than by the page, so nothing on the page can sit over them: they have to be told to step aside. They stepped aside when you switched sessions, but not when you opened a page tab, so opening Settings (or Tokenomics, Logs, the Feature Guide) with artifacts open left the artifacts view in front of the page you asked for. Every page tab now hides the pane while it is in front, and so does every window-covering dialog, the guided tour and the welcome walkthrough; the pane comes straight back when you return to the session, and a page that arrives while something is on top waits until the pane may show rather than flashing over it.
• The SSO Sign-in browser picker is back on machines with a per-user Chrome. On a managed workstation where you cannot install software for everyone, Chrome (and sometimes Edge) lives in your own AppData folder rather than under Program Files, and the app only ever looked under Program Files. A machine with both browsers therefore looked like it had one, and the Sign-in browser picker on an SSO account, which only appears when there is a genuine choice to make, stayed hidden: Edge could not be chosen. Both per-user locations are now checked as well, after the system-wide ones. The same lookup drives the vision browser, so a per-user Chrome now serves that too.

Full changelog: https://github.com/nubbymong/claude-command-center/blob/v2.1.0-rc.15/CHANGELOG.md

---

Upgrading from 2.1.0-beta.5 or earlier? Download the installer from this page — that build's updater looked for the old file name.

Claude and Claude Code are Anthropic trademarks.

SHA-256 checksums are in CHECKSUMS.txt attached to this release.