Skip to content

Changelog

What's new in Bossanova.

v1.165.0

v1.165.0

When something is skipped or waiting, Boss now tells you why

Previously, if Boss skipped a ticket or left a session in a waiting state, the UI would show a vague status like “awaiting green” or just “waiting” with no further detail. Now Boss names the specific rule that caused a ticket to be skipped during selection, and session and chat lists describe exactly what a waiting item is blocked on, such as “checking 12/20”. You no longer have to guess or dig through logs to understand why work is paused.

When a verification step decides it does not apply to a pull request, Boss now records that note directly in the PR comment, so reviewers can see the reasoning without leaving GitHub.

Improvements

  • Operators can now accept pinned PR review blockers directly from the CLI, unblocking sessions that were stuck behind a required review.
  • When Boss runs verification, it can now run multiple independent verification stacks on the same host at once, rather than being limited to one at a time. This reduces queuing when several sessions need verification simultaneously.
  • Boss now handles GitHub quota limits more gracefully. Background activity backs off when quota runs low and logs each refusal once per window rather than flooding the logs.
  • When a credential sync reconnects, it now uses the correct credentials. Previously it always failed silently due to a mismatch between the token used and what the account listing required.
  • If your account state was synced to a Boss instance that was running an older version, those changes were silently discarded. Boss now accepts those edits instead of reverting them.
  • Renaming a chat now updates its label in the timeline view without collapsing or resetting the list.
  • When Boss hits a problem refreshing credentials, it now prints a specific remedy line pointing to the cause, rather than hiding the real error behind a generic failure message.
  • Retrying ticket tag setup is now fairer across sessions. A persistent failure on one session no longer prevents later sessions from getting their turn.

Fixes

  • Fixed an issue where a busy Boss instance would never finish processing synced account state, leaving account changes stuck and never applied.
  • Fixed an issue where verification claim results could block a session from proceeding through CI, even when those claims were not relevant to the CI wait decision.
  • Fixed an issue where webhook activity could block Boss from processing other work, causing it to appear unresponsive to account sync messages.
v1.164.0

v1.164.0

GitHub quota management

Boss now manages its GitHub API budget more carefully across all the work it does on your repositories. Verify runs (the checks Boss uses to validate changes) are guaranteed a reserved slice of that budget, so a busy queue of other activity is much less likely to delay or block them. If Boss does hit a quota limit mid-flight, it waits for the limit to reset and then picks up where it left off rather than dropping the work.

Boss also caches the quota reading instead of checking it before every single action, and now batches its open-PR lookups into one shared query per repository per cycle rather than making repeated individual calls. PRs that are waiting on a person are re-checked when their base branch moves, not on a fixed two-minute tick. Together these changes mean Boss is spending its GitHub API budget on things that matter, not on housekeeping.

You can see how Boss has been spending that budget with the new boss account github-usage command, which shows last-hour call counts broken down by activity type alongside current quota levels.

Features

  • Predicted verify holds at plan time. Boss can now flag that a change is likely to be held for verification before it starts planning the merge queue, so you see that signal earlier instead of discovering it mid-run.
  • Enrollment renewal from the CLI. You can now run boss account devices to request a fresh device enrollment for your credentials, without going through a manual setup flow.
  • Weekly retro reports now include verify health. The automated retro summaries Boss produces now cover verify outcomes: changes that slipped through without a verdict, unnecessary holds, and merges that completed without a final decision.

Improvements

  • PRs waiting on a person are now re-evaluated when their base branch gets a new commit, rather than on a fixed polling interval.
  • Boss now handles cases where a sweep’s “ticket not selected” decision could incorrectly override a more recent hold on the same change. It also names the specific rule that caused the skip, so it is easier to understand why a PR was passed over.
  • Finalize steps that were interrupted by a GitHub quota reset now resume automatically once the quota recovers.

Fixes

  • Fixed an issue where verify evidence runs could loop repeatedly when Boss could not assess the result, rather than stopping after a bounded number of attempts.
  • Fixed an issue where certain account configurations with incomplete links could cause Codex account setup to fail.
  • Fixed an issue where credentials across independent installations could end up on mismatched versions and fail to sync correctly.
  • Fixed an issue where evidence collection could pick up criteria from outside the current change’s scope.
  • Fixed an issue where operator-only actions (approving and merging) could be invoked through paths that did not properly confirm operator permissions. Boss now enforces this check in one consistent place.
v1.163.0

v1.163.0

Verify now acts on confidence

When Boss verifies a change, it now factors in how confident it is about the result. High-confidence verifications merge automatically. Moderate- or low-confidence results pause and ask you to confirm specific items before proceeding. This means fewer cases where Boss merges something it was not sure about, and clearer prompts when a human check is warranted.

Improvements

  • Factory health warnings are now visible. If something is wrong with the environment Boss uses to run checks, that problem now shows up on the relevant proof pages and in the queue, so you know why things are stalled rather than having to guess.
  • Draft PRs that were once marked ready are now kept as drafts. Previously, a PR that had been marked ready and then converted back to a draft could lose that draft status. Boss now preserves it.
  • Older verification chats are folded in the session view. When a session has gone through multiple rounds of verify and repair, earlier chat exchanges collapse out of the way so the current conversation is easier to follow.
  • Verification sweeps correctly recognize already-judged items. An unscoped sweep would sometimes overlook a verification that had already been decided, causing it to be re-evaluated unnecessarily. Boss now picks those up correctly.
  • “Cannot assess” results are handled cleanly. If a re-run during verification hits an error, Boss now correctly reads that as “cannot assess” rather than treating it as a verification failure. Sessions in that state keep trying rather than stopping.
  • Park history is preserved across fix waits and attention pauses. Some internal state that tracks what Boss was doing before a wait was being lost, which could cause it to lose its place. That is fixed.

Fixes

  • Fixed an issue where converting a PR back to draft after it had been ready once did not stick.
  • Fixed an issue where verification sweeps skipped items that had already been judged, sometimes triggering redundant re-checks.
  • Fixed an issue where an errored re-run during verification was counted as a hard failure instead of an inconclusive result.
v1.162.0

v1.162.0

Session timeline in the web UI

The web session detail view now shows a timeline of what happened during a session, displayed below the chat. You can see the sequence of steps Boss took, with dates, giving you a clearer picture of how a session progressed without having to read through the full chat history.

Improvements

  • Clearer sign-off requests. When Boss needs your approval before merging, it now shows you exactly what it is waiting on and names the specific thing it wants you to sign off on. The web UI also flags when a step is waiting for you, so approvals are easier to spot and act on.
  • Smarter repair behavior. During automatic repair, Boss now drafts notes about the issues it is working through so that verify feedback is available earlier in the process. It also stops re-carrying findings that were already fixed in a previous pass, which means repair cycles are shorter and less repetitive.
  • Epic coordination picks up live PR activity. Boss can now detect coordination signals from pull requests as they are updated, rather than relying only on a snapshot taken at the start. This keeps multi-PR epics better in sync with what is actually happening in your repo.
  • Consistent verdict language. Verify results now use the same wording whether they appear in session notes or in PR comments, making it easier to understand the outcome at a glance regardless of where you see it.

Fixes

  • Fixed an issue where a repeated verify failure would not surface properly, leaving the status unclear after multiple failed posting attempts.
  • Fixed an issue where disk cleanup could stall when Boss was running under certain system-level process management, leaving old worktrees on disk longer than intended.
  • Fixed an issue where already-resolved repair findings could be carried forward into new repair cycles unnecessarily, causing redundant work.
v1.161.0

v1.161.0

Verify gets a lot smarter about what it checks and how it signals

Verify, Boss’s automated review step, now understands more kinds of code changes and reports its findings in a clearer way.

When a PR only moves files, deletes them, bumps dependencies, or changes generated code, Boss now recognizes these as routine housekeeping rather than behavior changes, and scopes its evidence checks accordingly. Proof video clips are now tied to specific claims, so each piece of evidence maps directly to the thing it is meant to prove.

When Verify parks a PR (decides it needs a human reviewer), it now posts a green status on GitHub and opens a review request, so reviewers get a normal GitHub notification and the PR does not look broken. While a PR is blocked or waiting, Verify posts a red status and keeps the PR as a draft, giving contributors a clear signal of where things stand.

Features

  • Session timeline shows verify, build, and repair chats. You can now see the full sequence of automated activity for a session in one place, including which phase each chat belonged to.
  • Session and chat lists show ticket IDs and short titles. Both the desktop and web views now display a ticket ID alongside a short title, making it easier to find the session you are looking for without memorizing long names.
  • Verify findings can be filed as follow-up tickets. When Verify surfaces issues that are not blocking enough to stop a merge, an operator can now have them filed as tracked tickets automatically rather than letting them get lost.
  • Verify-only sessions now exist as a distinct mode. Boss can run a verify pass on an externally created PR without treating it as something to build or auto-repair. Human-authored PRs can also be adopted into these sessions.
  • Blockers from already-merged PRs are cleared automatically. If a build blocker was tied to a PR that has since merged, Boss now removes it without manual intervention.
  • Review blockers that only touch unrelated files no longer stall builds. If a PR in review has no file overlap with the build candidate, Boss can proceed with selection rather than waiting indefinitely.
  • Boss can now compute a confidence score for changes, based on blockers, affected areas, change size, and available proof.
  • Defects can now be traced back to the PRs that introduced them. When a bug escapes into production, Boss can link it to the merged PRs that shipped it, making retrospectives more specific.
  • Proof pages can be published through a configurable hook. Repositories can now provide their own publish hook to control where proof pages are uploaded, rather than relying on a hard-coded destination.
  • Verify notes that were previously hidden are now visible. Advisory and review notes from both verify paths are now shown in a folded view, so nothing is silently dropped.
  • An optional open-PR limit is available for automated builds. Teams that want to cap how many PRs are open at once can now configure a maximum, and the build cron will stop opening new PRs once that limit is reached.

Improvements

  • Boss now labels PRs with their linked ticket automatically and keeps that tag up to date, even as heads move.
  • When Boss is automatically rebasing a conflicted PR, it now labels the activity as “rebasing” so it is clear what is happening.
  • Verify parks are now checked again after a PR sits parked, so conflicts that develop while waiting are caught and the rebase is started automatically.
  • Retrospective notes from core-owned issues now route to upstream notes rather than being lost.
  • Dependency overlap notes now include the names of the containing areas, making it easier to understand which parts of the codebase are affected.
  • Stage gates now apply only to the configured team, rather than all teams in the tracker.
  • Chat and session names in the automation are now shorter and include role labels, making it easier to read through activity logs.

Fixes

  • Fixed an issue where sessions stuck in a “fixing checks” state with no active repair would stay stuck permanently and stop responding to PR events.
  • Fixed an issue where draft PRs held by Boss could lose their ownership information across polling cycles, causing repair not to start.
  • Fixed an issue where verify send-backs on draft PRs could become permanently unrepairable.
  • Fixed an issue where a repair loop would repeat indefinitely when the underlying problem could not be fixed automatically. Boss now routes these cases to verify review instead.
  • Fixed an issue where ticket verify holds were not surfaced as items needing attention, so they could be overlooked.
  • Fixed an issue where duplicate verify sessions could both proceed, leading to conflicting verdicts.
  • Fixed an issue where a PR session caught in a broken “fixing checks” state would silently drop every incoming PR event.
  • Fixed an issue where stuck verify waits whose callbacks could never fire were not surfaced, leaving sessions in a silent hold.
  • Fixed an issue where repair start contention could leave a block that was never retried or cleared.
  • Fixed an issue where Boss could fail to start cleanly when PR association work ran at boot, occasionally causing a false connection error.
v1.160.0

v1.160.0

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.
v1.159.0

v1.159.0

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.
v1.158.0

v1.158.0

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.
v1.157.0

v1.157.0

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.
v1.156.0

v1.156.0

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.