Changelog

Verified Merges and Smarter Repair

Boss now runs a full verification pass before merging any PR, checks its own work, and can attempt repairs automatically when something blocks a merge. If Boss finds issues after a review, it will try to fix them and re-verify in a fresh session. After two repair attempts, if blockers remain, the PR is parked rather than left spinning. PRs that touch sensitive paths are flagged for human review instead.

Verification results are now written as structured proof records alongside each PR, with a summary comment that explains what was checked and what the outcome was. Boss also uses repository scripts to describe what each verification area covers, so the proof attached to a PR reflects the actual checks that ran.

Features

• Boss can now split an epic child ticket that grows too large into sibling tickets automatically, keeping each piece of work at a manageable scope.
• The accounts screen now shows usage bars and sync state for each account at a glance, making it easier to see which accounts are active and how much of their quota has been used.
• Account credentials are now distributed end-to-end encrypted to connected instances. Each instance enrolls a device key, which can be approved or revoked, and credentials are delivered only to approved devices.
• Claude agent sessions now route through a managed companion account, so child processes use proper account rotation rather than inheriting a single shared credential.
• Boss now balances account selection across weekly reset windows, spreading load more evenly rather than exhausting the same accounts repeatedly.

Improvements

• Settings panels now align values into consistent columns across all screens, making them easier to scan.
• Boss is better at discovering PRs that should be picked up for work, regardless of the current state of the linked ticket.
• Operator notes pinned to a PR are now passed back into the repair process, so context you leave on a PR is not lost when Boss retries.
• The accounts list in the terminal UI is trimmed to the columns that matter, removing clutter.
• Verification blockers are now structured and passed directly to the repair step, so Boss knows exactly what to fix rather than re-reading the whole PR.
• Boss recaptures active Claude spinner panes after a CLI authentication refresh, so sessions continue displaying correctly after re-login.

Fixes

• Fixed an issue where account metadata edits could be lost if a credential sync transition happened at the same time.
• Fixed an issue where Dependabot PRs that passed all checks were not always handed off to the merge owner correctly.
• Fixed an issue where stopping Boss could complete before background merge work had finished, potentially leaving work in an inconsistent state.
• Fixed an issue where a PR title linked to a tracker ticket could be overwritten during finalization.
• Fixed an issue where a skill refresh notification could appear more than once for the same update.
• Fixed an issue where credential enrollment could slow down reconnection after an upstream disconnect.
• Fixed an issue where a Codex session that hit a provider error could publish incomplete work before the session recovered.
• Fixed an issue where verification holds were not always recognized when a PR was parked with a successful status.
• Fixed an issue where review findings confirmed as non-blocking on an earlier pass could resurface on a later pass.
• Fixed an issue where reviewed PR heads were not carried forward correctly after a message-only rewrite.
• Fixed an issue where a transient failure checking model readiness would abort rather than retry once.
• Fixed an issue where terminal focus could be lost when a view was rebuilt in the background.

GitHub Issues tracker

Boss can now connect to GitHub Issues as a project tracker. When linked, Boss creates, ranks, and closes issues automatically as work moves through the pipeline. Epics are supported via GitHub’s native sub-issues, and dependencies between issues are tracked using blocked-by relations. When verify merges a pull request, the corresponding issue is closed automatically.

To get started, point Boss at a GitHub repository with ranking labels configured and run the setup flow from your project config.

Features

• Personal API tokens. You can now create personal API tokens in Boss settings and use them to connect to the hosted MCP gateway. Tokens are scoped to your organization and can be revoked at any time.
• Account usage meters. The web account list now shows usage as progress bars so you can see at a glance how much headroom each account has left.
• Verify now reviews externally-built PRs. Verify can admit pull requests that Boss did not build, apply your repo’s admission policy (by author type or label), and post its own review before merging. PRs that opt out of this flow are left for a person to merge.
• Repository trust in project config. You can now declare which local repositories Boss should trust directly in .boss-project.json, with changes applied only after an explicit CLI confirm.
• Verification handed off to a separate chat. By default, verification now runs in its own chat session rather than inline, keeping your main session cleaner.

Improvements

• Boss now picks accounts whose weekly quota resets soonest first, and avoids accounts that are close to their per-model usage cap when choosing where to run a session.
• Skill reinstalls are now lossless: Boss preserves any local changes before replacing a skill, and checks for stale installs against the latest version from origin before deciding a reinstall is needed.
• Scratch directory cleanup during builds no longer stalls waiting for approval.
• Boss now detects Makefile lint-check and format-fix targets when scanning a project, and prefers them over built-in defaults.
• Callbacks are now cleaned up when a session is archived, so stale callbacks no longer accumulate.
• Claude folder-trust prompts are now recognized and accepted automatically for trusted repositories.
• Large interactive tables in the terminal now render lazily, so they stay responsive with many rows.
• Boss waits for additional confirmation before reporting a detached background process as healthy, reducing false “all good” reports after a restart.

Fixes

• Fixed an issue where sessions stuck in merging or archiving showed incorrect status colors after hitting an error.
• Fixed an issue where a wrapped user message could be misread as a question from the agent, causing Boss to wait unnecessarily.
• Fixed an issue where usage data fell back to stale cached values instead of live readings during account rotation.
• Fixed an issue where a recovery pull request lost its link to the original ticket.
• Fixed an issue where verify used the wrong credentials when checking tracker gates on a scheduled run.
• Fixed an issue where GitHub issue dependencies were read back before all edges had finished writing, causing incomplete graphs.
• Fixed an issue where security findings were not all filed when batched verification ran.
• Fixed an issue where sweep gate failures (lint, formatting, release checks) were reported as empty-work rather than real failures.
• Fixed an issue where Codex registry errors were swallowed instead of surfaced to the user.
• Fixed an issue where closed sessions’ pull request callbacks were dropped instead of kept until the PR was handled.

Improvements

• Boss is better at recovering skill files that were moved or renamed in a repository’s history, so code that appeared to go missing should now be found correctly.
• When Boss pushes a branch and an intentional rewrite was part of the plan, that rewrite is now preserved correctly through retries instead of being silently dropped.
• Boss now claims a piece of work before drafting it, and double-checks ownership before publishing, reducing the chance of two sessions stepping on each other on the same task.
• Before labeling a pull request as ready to verify, Boss now confirms the branch is actually at the expected commit. This prevents stale labels from appearing on branches that have moved on.
• Boss now retries certain acceptance checks when the underlying code has shifted slightly, rather than immediately settling for a partial result.
• Evidence collected during a session is now uploaded through a more tightly controlled path inside the background process, keeping credentials isolated from the rest of the system.
• Deliberate branch rewrites are now preserved correctly when a push needs to retry, and superseded history is handled cleanly during publication.
• When an automated extension is intentionally skipped, Boss no longer files it as a failure. Only genuine problems generate failure notes.
• If an image-related guard hits a usage error mid-session, Boss now saves a snapshot of the plan in progress rather than losing it.
• Duplicate notes that accumulate across long sessions are now deduplicated, keeping context cleaner for the AI working on your code.

Fixes

• Fixed an issue where completed repair attempts would be retried unnecessarily when the underlying input had not changed.
• Fixed an issue where in-progress status labels were too long to fit in the status column.
• Fixed an issue where parallel analysis jobs across multiple worktrees could exceed resource limits; they are now properly bounded.
• Fixed an issue where local gate checks across worktrees were not bounded, which could cause flaky timing behavior.
• Fixed an issue where paginating through repeated operations could return inconsistent results.
• Fixed an issue where session cleanup timing in certain edge cases was non-deterministic, which could cause test failures and unpredictable behavior in production.

Session setup is more resilient and easier to follow

When you open a new session, Boss now keeps more of your work even if something goes wrong during startup. If a transient error interrupts the launch, Boss retries automatically before giving up. If setup was already underway when you reopen a session, Boss picks up where it left off and shows you the progress you missed rather than starting from a blank state. The same applies to trash restores: reopening a session that is mid-restore now rejoins the live progress instead of showing nothing.

Boss also reuses the workspace it already prepared when a previous start attempt failed, so the next attempt is faster and wastes less work.

Improvements

• The session list now shows a chat that is waiting for your input as “Waiting” rather than leaving it in an ambiguous state.
• Session filters and group headings stay visible as you scroll through a long session list, so you no longer lose track of which group you are in.
• Codex capability checks now account for a host that is already under load, reducing false negatives when starting sessions on a busy machine.
• Hosted MCP connections can now authenticate through AuthKit with refresh tokens, so MCP sessions stay alive without requiring you to re-authenticate.
• Rollback cleanup steps each get their own time budget, so a slow cleanup operation is less likely to block or abandon the rest of the rollback.
• Boss can now surface a run that is blocked waiting on its own callback as in-progress rather than showing it as stuck.

Fixes

• Fixed an issue where archiving a session whose workspace removal ran long was not recorded correctly, which could cause it to appear as if the archive never happened.
• Fixed an issue where a failed session start could leave the prepared workspace in a state that prevented the next attempt from reusing it.
• Fixed an issue where a slow initial screen draw could cause a session start to be cancelled prematurely.

Verify gets smarter about PR status and GitHub setup

PRs that are queued up and waiting for Boss to run a verification check now show a “waiting for verify” status instead of just sitting there looking green and done. This makes it clearer that there is still work in progress before a PR is truly ready.

Boss now also detects when GitHub App setup has been refused due to a permissions problem and shows you specific guidance about what went wrong, rather than leaving you to guess. If you have run into a dead-end GitHub setup screen with no explanation, this should help.

Features

• PRs that are queued for verification now show their waiting status clearly on the board, so you can tell they are not fully approved yet.
• When GitHub App setup is blocked by a permissions issue, Boss now shows you a specific explanation and points you toward what needs to change.
• Cron PRs that contain no real commits are now marked as blocked rather than being left to appear as if they could merge normally.
• Boss now detects when a chat session fails to start properly and retries it automatically, reducing situations where a session just sits idle with no output.
• Verification checks can now be triggered directly by GitHub webhooks, so Boss responds faster to PR activity instead of waiting for the next scheduled check.
• Service logs are now kept for two days instead of one, giving you a longer window to review what happened if something goes wrong.
• Errors from plugin processes are now captured and tracked, which should help surface and fix plugin failures faster.

Improvements

• Retro review notes are now grouped by their type, so related notes stay together and it is easier to see which themes are driving review feedback.
• Scheduled jobs that fail no longer lose their next scheduled run time. Previously, a failed run could cause the job to show no future run at all.
• A session that is still starting up now shows as “Initializing” rather than “Stopped,” which more accurately reflects what is happening.
• Boss now correctly separates visual-only changes that have no supporting evidence when deciding what to park, reducing false positives in verification.
• When running in a multi-instance setup, Boss correctly skips verification sessions that belong to another instance, avoiding conflicts on shared repositories.
• Fixed an issue where duplicate criteria could appear in the chat selection flow.
• Fixed an issue where plan writeback would fail if the content contained certain bracket characters.
• Fixed an issue where a failed deployment phase that had been approved was not handled correctly.

GitHub App verification and recovery

Boss now checks whether your GitHub App installation is properly set up after deployment, and flags any installations that are missing required permissions. If something is misconfigured, Boss surfaces what is wrong and how to fix it, rather than leaving you to guess why things are not working.

Fixes

• Fixed an issue where the first command sent to an agent at startup could be duplicated, causing it to run twice.

Improvements

• Fixed an issue where a run waiting on CI checks could appear incorrectly flagged as needing your attention. Boss now correctly treats it as still checking until the pull request’s checks finish.
• Background verification work now does less redundant reading, skipping checks it has already seen and avoiding repeated lookups when nothing has changed. This keeps things running smoothly without any visible change on your end.
• The public share card for Bossanova (the image that appears when a link is shared on social platforms) now renders as a proper image rather than a blank or broken preview.

Fixes

• Fixed an issue where workspace setup could become unavailable under certain conditions. Provisioning is now more reliably protected against interference.

Sessions now move to “Ready for Review” when a draft PR is published

When a pull request leaves draft status on GitHub, Boss now automatically moves the matching session to “Ready for Review.” Previously, the session could stay stuck in a draft-like state even after the PR was already open for review.

Improvements

• Repositories connected via SSH are now correctly matched to their GitHub App connection, so those repos show up where you would expect them in the interface.
• Running a verification sweep is less likely to time out or consume unnecessary GitHub API quota.

Fixes

• Fixed an issue where tools available to an agent were sometimes being resolved against the wrong working directory, which could cause a session to start with an incomplete or incorrect set of tools.

Improvements

• Boss now checks available disk space before running local checks, and reclaims old build cache entries automatically. This makes it much less likely that a long-running local environment will run out of disk space mid-session.
• When Boss detects that a check failed, it can now isolate and re-run just the failing targets rather than the whole suite. You also get a clearer report of what failed and how loaded the machine was at the time, which makes intermittent failures easier to diagnose.
• Epic-level planning now compares related work items through their actual dependency order. Previously, sibling epics could be evaluated out of sequence; now the comparison respects what depends on what.

Fixes

• Fixed an issue where Boss could wait up to eleven minutes before responding to a command if the local installation was out of date. It now tells you immediately that the version is too old to handle the request.
• Fixed an issue where Boss would keep retrying a merge that had already been verified successfully on a different machine, causing unnecessary repeated attempts.
• Fixed an issue where a background process could stall indefinitely after a check had already reached a final result. Boss now moves on promptly once an outcome is decided.
• Fixed an issue where certain draft-stage context was not being recognized correctly, which could cause Boss to miss relevant information when preparing a plan.
• Fixed an issue where knowledge capture could pull in content from outside the intended documentation, causing the captured context to be noisier than expected.

Fixes

• Fixed an issue where moving a chat to a different account would show stale or incorrect information after Boss restarted or switched to a backup server.
• Fixed an issue where certain chat updates would silently stop applying after an unexpected crash, leaving rows out of date until you reloaded.
• Fixed an issue where failures on the Home screen would disappear instead of staying visible so you could act on them.