Changelog

Repository management on the web

The web interface now has a full repository management section. You can view all connected repositories, update settings like merge strategy, and remove a repository with a confirmation step to prevent accidents. This brings the web interface to parity with what was previously only possible in the terminal client.

Security

Boss now authenticates every connection between the CLI and the local background process it talks to. This closes off a gap where other processes on the same machine could have made requests. The change happens automatically and you should not notice anything different day to day. If something does go wrong, Boss will surface a clear error rather than a silent failure. There is also a new boss daemon rotate-token command if you ever need to reset that credential manually.

Improvements

• Account rotation history now shows email addresses on both sides of a switch, making it easier to see exactly which accounts were involved.
• You can now toggle accounts on and off in the accounts list using the space bar, consistent with how toggles work elsewhere in Boss.
• Fixed an issue where Boss would occasionally log spurious errors for sessions that had already finished or been archived.
• The web accounts page no longer shows unnecessary alerts during account switches.

Fixes

• Fixed an issue where the “Refreshing usage” status message could run into the accounts table visually.
• Fixed an issue where removing a repository through the web UI could be triggered twice if clicked quickly.
• Fixed an issue where repository loading on the web could fail silently when the connection URL was in an unexpected format.

Improvements

• Fixed an issue where Epic mode could crash or behave unexpectedly when a draft pull request had no content yet.
• Fixed a crash that could appear in certain browser environments due to a compatibility issue with a built-in JavaScript method.
• Unrelated error noise from third-party scripts is no longer incorrectly captured as Boss errors, so reported issues more reliably reflect actual problems in the product.
• On mobile, the session detail view no longer shows a redundant title in the sub-header, keeping the layout clean on small screens.
• Mobile list rows now align their repository and date columns correctly, and icon buttons are consistently sized.

Fixes

• Fixed an issue where the “Cannot connect” error message ran directly into the recovery hint with no breathing room, making it harder to read at a glance.
• Fixed a small visual glitch where the upgrade spinner label had an extra space before it.

The “boss-build” skill and smarter planning

The skill previously called boss-implement is now named boss-build. The name better reflects what it does: building and iterating on code, not just implementing a spec. If you have any workflows or habits built around the old name, now is the time to update them.

Planning also got smarter. When Boss works out a plan for your task, it now figures out upfront what kind of verification the work will need, rather than discovering that later. This means fewer surprises mid-task.

Features

• Usage at a glance. Boss now shows per-account usage information directly in the terminal UI, including how fresh the data is. You can see how much of your quota has been used without leaving the app.
• Merge when it counts. On the web, the Merge button now only appears when a pull request is actually passing. No more wondering whether it is safe to merge.

Improvements

• Archiving a session from the session list no longer jumps your cursor to a different item. Boss keeps your position so you can continue where you were.
• The agent selector on the web is narrower and now shows a loading indicator while it initializes, making it easier to follow what is happening.
• The session detail page on mobile now stacks the title above the action buttons so everything is readable without squinting.
• Scheduled task status now correctly reflects whether a session is actually active. Previously, parked or stranded sessions could show as “Running.”

Fixes

• Fixed an issue where running a Boss deployment could drop your terminal connection.
• Fixed an issue where boss-plan would silently drop screenshots and file attachments from reporter tickets when rewriting descriptions. Those attachments are now preserved.
• Fixed an issue where the web app would show a confusing error during GitHub setup instead of a clear explanation of what went wrong.
• Fixed an issue where certain network request failures did not surface the full error detail, making them harder to diagnose.
• Fixed an issue where approved pull requests could not be merged from the web.

Suspended-account detection

Boss can now recognize when a connected Claude account has been suspended. Instead of surfacing a confusing error, it handles the state gracefully so you know what happened and why things stopped working.

Improvements

• Merge status is now tracked on the server. Previously, the “Merging” state shown in the session list was calculated in the app and could get out of sync. It is now computed in one place, so what you see reflects reality more consistently.
• Fixed an issue where the “Merge” button could remain visible while a merge was already in progress.

Fixes

• Fixed an issue where a session proof that was cut off mid-run would be marked as a hard failure. It now surfaces as a neutral “truncated” state, which is more accurate when the run was simply interrupted rather than broken.

Merging status is now visible

When Boss is in the process of merging a pull request, the session list now shows a “Merging” status so you can see what’s happening without having to guess. Previously there was no indicator during this step, which made it easy to think nothing was going on.

Features

• Boss now warns when a blocker is itself blocked. When Boss auto-links a blocking ticket during planning, it will flag if that blocker is transitively stuck behind something else. This surfaces hidden bottlenecks before they quietly stall your work.
• API docs are now versioned and published. Each release of the Bossanova API now has its own reference page, along with an API changelog so you can track what changed between versions.

Improvements

• TUI proof recordings are more reliable and easier to watch. Captions are now synced to the video clock and burned along the bottom of the frame, stale captions no longer linger between scenes, and video files are properly normalized so they play back correctly.
• Boss now exits with an error when a TUI proof is incomplete or a scenario is missing, rather than silently succeeding. This makes broken proof runs much easier to catch.

Fixes

• Fixed an issue where the web app could show Boss as offline after the background service restarted, even though everything was running fine.
• Fixed an issue where a stalled terminal connection could get stuck in a state where Boss appeared online but was not actually sending output. The stuck state is now detected and cleared automatically.
• Fixed an issue where reconnecting to a session could behave incorrectly after a failed or partial connection attempt.
• Fixed an issue where database conflicts during session updates could cause writes to fail silently instead of retrying.

Accounts Management in the TUI

You can now manage your Claude and Codex accounts directly from the Boss terminal interface, without leaving the TUI. The new Settings → Accounts screen lets you view all connected accounts, see their health status, cooldown state, and last-test results, and edit labels, email, or priority inline. You can also register new accounts, run a live connection test, and safely disable or remove accounts you no longer need, all from the keyboard.

Features

• Account registration flows in the TUI. You can add a new Claude or Codex account without switching to the web UI. The registration flow runs natively in the terminal.
• Account detail and editing. Select any account to see its full details, including status, usage columns, and timestamps. Edit fields inline and save without leaving the screen.
• Disable and remove accounts from the TUI. Both actions include a confirmation prompt so you do not accidentally remove an account that is still in use.
• Account health and cooldown visibility. The accounts list and detail screen now surface health state, cooldown timers, and last-test error details so you can see at a glance why an account might not be getting work.
• Clearer rotation status when no account is available. When Boss cannot assign work because no account is eligible (for example, all are disabled or unhealthy), it now reports that specifically rather than giving a generic “no capability” message. This shows up in the TUI and the accounts list.
• boss repair start command. If auto-repair stops running, you can now restart it from the command line with boss repair start instead of having to restart the whole service. Boss also re-arms repair automatically after a restart.

Improvements

• When you finish editing a cron job and return to the list, the job you just edited is highlighted so you can see exactly what changed.
• Emptying the trash now shows a live progress count so you know it is working on a large deletion rather than sitting silently.
• Boss now avoids starting a new session for a ticket whose pull request has already merged, catching cases where work would otherwise be duplicated.
• Cron sessions that got stuck mid-flight during a previous interrupted run are now cleaned up automatically on startup.
• If a chat session gets stuck waiting on a question for more than 15 minutes, auto-repair can now move past it instead of stalling indefinitely.
• Stopping or restarting Boss no longer accidentally terminates plugin processes belonging to other running Boss instances on the same machine.
• The docs now include an upgrade guide and a note that Boss automatically picks up a .env file in your worktree.

Fixes

• Fixed an issue where session titles were sometimes derived from internal metadata lines rather than the actual content of the conversation.
• Fixed an issue where restarting Boss could briefly show a false connection error.
• Fixed an issue where switching to a different user account could leave the previous session in an inconsistent ownership state.

Plugin verification

Boss now checks that any plugin it loads is signed and unmodified before running it. If a plugin binary does not pass the integrity check, Boss will refuse to run it. This is a quiet but meaningful safety improvement: you no longer have to take on trust that the tools Boss executes are the ones that were shipped.

Features

• boss new is smarter about picking repositories. You can now type a short unique prefix of a repository ID and Boss will resolve it automatically. Boss also derives a session title for you when one is not provided, and rejects inputs that look like display IDs rather than silently picking the wrong thing.
• Archiving is now concurrent. If you have several sessions to archive, Boss processes them in parallel instead of one at a time, so bulk cleanup finishes faster.
• Boss can now handle a login without restarting. Running boss login while Boss is already running now re-registers the account correctly in the background. Previously this could leave the session in a misconfigured state until you restarted.

Improvements

• Boss routes certain background tasks to a lighter-weight model tier, which keeps costs down without changing the results you see.
• Boss reuses context it has already read within a session rather than re-fetching it on every turn. This reduces unnecessary work and keeps things moving.
• The web Daemons list now shows the correct running instances across all servers. Previously it always appeared empty in production.
• Disabled cron jobs now show their “Gated” status in a neutral grey rather than orange. Orange implied something needed attention; a disabled job is just off.
• Fixed an issue where duplicate cron saves could occur.

Fixes

• Fixed an issue where switching between servers could cause a false connection error during a brief authentication hiccup. Boss now retries gracefully instead of surfacing the error.
• Fixed an issue where the tool discovery step for long-running sessions could behave differently across runs, occasionally causing tasks to start in an inconsistent state.
• Fixed an issue where the web Daemons list was always empty, even when instances were running.

Smarter account management and automatic failover

Boss now manages multiple Claude accounts more actively. When one account is near its usage limit, Boss can automatically switch to a healthier account mid-session, so your work keeps moving without manual intervention. A local proxy handles the credential switching transparently, meaning the Claude session running in your terminal sees a valid key at all times without you touching any config.

Boss also now picks the best available account from the start, choosing accounts with more headroom rather than defaulting to whichever one was used last.

Features

• Automatic account rotation. When an account hits an auth error or approaches its usage cap, Boss can now switch to another account automatically. Sessions continue without you needing to manually intervene or restart.
• Utilization-aware account selection. Boss now picks the account with the most remaining capacity when starting a session, rather than always defaulting to the same one.
• Proactive rotation (opt-in). There is a new opt-in setting that lets Boss rotate away from an account before it actually hits its cap, reducing the chance of a mid-task interruption. This is off by default.
• /boss switch is now credit-free. Typing /boss switch inside a Claude session no longer consumes credits to process the command. Boss intercepts it directly.
• Usage-limit detection. Boss can now recognize when Claude’s interface is showing a usage-limit banner, which helps it decide when to rotate to another account.
• boss settings --managed-accounts flag added for configuring managed account behavior from the command line.
• Linear API key from your project. If your repository has a LINEAR_API_KEY in its .env file, Boss now passes it into sessions automatically. You no longer need to set it globally.

Improvements

• Account IDs are now shown in full in CLI output rather than being truncated.
• The account list screen has an improved layout.
• Boss now logs a diagnostic at startup when account rotation lanes are unavailable, making it easier to understand why rotation might not be working.
• When Homebrew updates Claude’s installation path, Boss now detects and corrects the stale path automatically rather than failing silently.
• Sessions that are created for planning work (with no code changes expected) now complete cleanly instead of being flagged as errors.

Fixes

• Fixed an issue where chats between agents could be assigned to the wrong account, potentially causing auth failures.
• Fixed an issue where sessions created before managed accounts were configured could be left without an account binding, causing them to miss rotation.
• Fixed an issue where an account that cannot be verified due to a missing runner was shown as failed rather than temporarily unavailable.
• Fixed an issue where tmux startup errors were not surfaced clearly, making terminal launch failures hard to diagnose. Boss now auto-recovers a missing TERM setting and shows the real error when launch fails.
• Fixed an issue where a chat session running alongside others could pick up the wrong account’s credentials.
• Fixed an issue where restarting Boss could leave a session showing as active when its status was actually stale.

Improvements

• Boss now reads Claude usage more reliably. Previously, usage could appear lower than it actually was if certain setup activity wasn’t counted correctly. That gap is now closed, so what you see in the product reflects your actual consumption.
• Starting and restarting Boss is more stable. Boss now waits a bit longer for its background process to fully come up or shut down before reporting a problem, which means you’re less likely to see a false connection error when restarting.

Account usage is now visible in Boss

You can now see how much of your AI usage quota is left for each connected account, directly from the boss account ls command and the MCP list_accounts tool. Boss checks usage for both Claude and Codex accounts and shows utilization levels alongside reset times. Pass --refresh (or refresh in MCP) to fetch the latest numbers live rather than returning the cached snapshot.

This also fixes a significant bug where Boss could incorrectly decide that a freshly-switched account was at its limit. When Boss rotates to a new account, it now checks that account’s actual usage before marking it as exhausted. Previously, a banner left over from the previous account could trigger a false alarm, causing a cascade where all accounts got incorrectly cooled down.

Improvements

• boss skills sync is now a standalone command. Running it refreshes your skills without going through an interactive menu, which makes it usable in scripts and makes edits to repo-level skills take effect in live sessions without a restart.
• Upgrading Boss from within the app now shows a spinner while the upgrade is in progress, so it no longer looks frozen.
• After triggering a restart from the upgrade screen, Boss waits for the connection to come back before showing any status. Previously it would sometimes flash a misleading “cannot connect” error immediately after restart.

Fixes

• Fixed an issue where rotating to a new AI account could cause a cascade of false “account exhausted” signals, eventually marking all accounts as unavailable when they were actually fine.
• Fixed an issue where plugins could stop responding after an unexpected exit. Boss now automatically restarts them and resumes any work that was in progress.
• Fixed an issue where adding an account that was already registered could produce errors or duplicate entries.
• Fixed an issue where Codex chat transcripts were sometimes not captured correctly.
• Fixed an issue where cached usage data could be dropped during a probe outage instead of being preserved.