Changelog

GitHub Callbacks

Boss can now watch GitHub pull requests and trigger actions automatically when they change. You register a callback on a PR, and when that PR is updated, Boss picks it up and responds without you having to check in manually. This works from the CLI (boss callback add|list|remove), from MCP tools, and through Boss’s existing session flow.

The underlying plumbing is also more reliable: callbacks are verified before they fire, retried if delivery fails, and automatically expired when they are no longer relevant.

Features

• Stop button in web sessions. You can now stop a running session from the web chat page without having to navigate away or wait for it to finish.

• Desktop notifications when Boss needs you. Boss can now send a native OS notification when a session is waiting for your input. On macOS this uses the system notification center. You can turn this on or off in Boss’s settings, and clicking the notification takes you straight to the session.

• boss plan creates estimates in Linear. When Boss plans work in Linear, it now writes time estimates back to the tickets and uses those estimates to decide when a collection of tasks should become its own epic. Epics are only marked complete when all their acceptance criteria are met, not just when sub-tasks are checked off.

• Defer the draft PR when creating a session. Sessions that operate on a worktree can now skip the automatic draft PR creation at the start and open one later, which avoids noise for work that may not need a PR right away.

• Mobile-friendly settings pages. The web settings pages have been restyled to work properly on small screens.

Improvements

• Adding an account in the terminal now uses selectable confirmation buttons rather than a plain text prompt, which makes the flow a bit harder to misread.

• When Boss restarts, it reconnects to any sessions that were already running rather than losing track of them, reducing dropped work after a restart.

• Boss is better at recovering sessions that get stuck in an auth-failed state when the underlying credentials are actually fine. It will respawn the session in place using the same account rather than switching to a different one unnecessarily.

• Boss now surfaces when an account’s usage pool is exhausted with a clearer signal, so you know why a session stopped rather than seeing a generic failure.

• Fixed a long-standing issue where running Boss in development mode could fail because the system ran out of file handles. Boss now raises its own file-handle limit at startup and reports in the health diagnostics if the limit is still too low.

Fixes

• Fixed an issue where GitHub PR callback messages were being pre-filled but never actually submitted, so the action never fired.

• Fixed an issue where submitting a message could silently fail when the content was wider than the terminal pane, causing Boss to believe it had sent something it had not.

• Fixed an issue where the connection diagnostics could misread a normal agent exit as a PATH configuration problem.

• Fixed an issue where project keys containing special characters could generate invalid identifiers.

OpenCode support

Boss can now run OpenCode as an agent, alongside the existing options. When Boss kicks off a session, it can launch OpenCode headlessly, track the session as it progresses, and report back the result the same way it does for other agents. This rounds out the agent choices available in a Boss-managed workflow.

Improvements

• Epic planning. Boss can now break a large epic into a set of child tickets automatically, estimating each one, flagging which are safe for an agent to tackle, and persisting the decomposition so work can resume if it’s interrupted partway through.
• Concurrent merge handling. When multiple merge requests arrive for the same repository at the same time, Boss now queues them and processes them in order instead of letting them race. This reduces the chance of merges failing due to conflicts caused by the queue running simultaneously.
• Database review. Code review now includes a database lens. Boss checks schema changes against naming standards and flags issues the same way it does for API or logic concerns.
• API and database naming conventions. The API design, API review, and database design skills now include explicit field-naming and schema-naming rules, so Boss applies consistent conventions when writing or reviewing those artifacts.
• Disk cleanup after agent sessions. Boss now cleans up the build cache left behind when an agent session finishes, so long-running installations don’t quietly accumulate gigabytes of stale data on disk.
• More open file handles available. Boss raises its own limit on how many files it can have open at once when it starts up. This prevents a class of obscure failures that could occur in environments with tight system defaults.
• Better status for stuck or failed runs. Runs that ended in an error or were abandoned without a clean shutdown now show a clearer status in the session list, rather than appearing ambiguous or incorrectly colored.
• Skill portability. The built-in Boss skills (review, plan, build, epic, finalize) no longer hard-code project-specific identifiers. They read those values from your configuration instead, making the skills usable across projects without modification.

Fixes

• Fixed an issue where opening Boss in a new browser tab or reloading the page could show a connection error even when the background process was running fine.
• Fixed an issue where worktree setup could silently swallow directory errors, making failures harder to diagnose.

MCP tools can now read and write your settings, and start chats or repairs

Boss’s MCP integration now covers three more workflows you previously had to do by hand. You can read or update your global Boss settings directly through an MCP tool, start a new chat inside an existing session without leaving your AI tool, and kick off a repair workflow the same way. These additions bring the MCP surface closer to full parity with what you can do from the terminal or web UI.

Features

• Session archiving is now visible in the session list. When Boss is archiving a session, the list shows an “Archiving” status so you know something is happening instead of wondering why the session looks stuck.
• Rotation history moved below the chat list. Account rotation details now sit under your chats, where they are easier to read in context. Timestamps are date-aware and show more useful detail.
• Keyboard shortcuts in the web new-chat page. You can now navigate the agent picker and dismiss it with Esc, without reaching for the mouse.
• Detached runs survive a Boss restart. If you started a session with --detach, Boss now re-attaches to it after restarting instead of losing track of it entirely.
• Accounts rotate in a smarter order. When several accounts have the same priority, Boss now picks the one whose weekly quota resets soonest, so you get capacity back faster.

Improvements

• Resurrecting a merged or archived session no longer fails when the original branch is gone. Boss recreates it from the base branch automatically.
• Scheduled (cron) sessions are less likely to be incorrectly cancelled while they are still starting up.
• New repositories now have automatic branch deletion turned off by default. Branches created by no-change cron runs are still cleaned up.
• The “Archiving” spinner in the session list is now driven by a real signal from Boss, so it no longer appears on sessions that are not actually being archived.

Fixes

• Fixed an issue where restarting Boss could cause interactive sessions to show a connection error, even though Boss was running fine.
• Fixed an issue where certain actions (such as viewing daemon-specific information) could fail with a “daemon not available” error in multi-server setups, because the request was reaching the wrong server.
• Fixed an issue where replayed webhook deliveries could be processed more than once.
• Fixed an issue where internal usage metrics could inadvertently expose identifiers across accounts.

MCP Gateway now supports the full tool set

Boss can now be controlled through an MCP gateway with full coverage of the tools available locally. Previously, only a subset of read-only operations were reachable through the gateway. With this release, the gateway supports the complete range: reading repo and session state, triggering and managing cron jobs, updating sessions and chats, and performing destructive operations like archiving sessions or deleting repos. If you use Boss through an MCP-compatible client, you no longer need a direct local connection to reach most of Boss’s functionality.

Cross-user isolation is enforced throughout, so each user’s gateway access is scoped to their own data.

Features

• Delete git branches automatically after archiving. There is a new toggle in repo Automations settings: “Delete git branches after archiving.” When turned on, Boss will delete the local branch for a session when you archive it, keeping your branch list tidy without any manual cleanup. The base branch is protected and will not be deleted.

Fixes

• Fixed a rare race condition where two processes competing over a worktree lock could both lose, leaving the lock stuck. This would have caused a session to stall unexpectedly.

Manage AI accounts from the web

You can now add, test, and remove Codex and Claude accounts directly in the Boss web interface under Settings > Accounts, without touching a config file or the command line. If you use Boss across multiple machines or hand off access to teammates, this is a much more convenient place to manage your AI provider credentials.

The “Add account” option is disabled when no instance is connected, so you won’t accidentally submit credentials into the void.

Features

• Auto-resume after restart. If Boss restarts while a headless run is in progress, it will now pick up where it left off automatically. Previously, a restart would orphan those runs and they would have to be restarted by hand.
• Archive sessions after merge, from the web. The option to automatically archive a session once its pull request is merged is now available in web repo settings, alongside the rest of your repository configuration.

Fixes

• Fixed an issue where rate-limit errors from AI providers were not always recognized correctly, which could cause Boss to mishandle retries or failover.

Cron Jobs

You can now create, edit, and manage cron jobs directly in the Boss web app. Set a schedule, pick a repository, toggle a job on or off, or trigger a run immediately, all from a dedicated Cron Jobs settings page. Previously this required working outside the product entirely.

Auto-archive sessions after merging

Repositories now have an “archive after merge” option in their Automations settings. When it’s on, Boss automatically archives a session as soon as its pull request is merged. If you’re looking at that session when it archives, Boss takes you back to the session list so you’re not left on a blank screen.

Improvements

• When Boss hits a rate limit from the AI provider mid-run, it now rotates to a backup or waits and retries automatically, rather than failing the run outright. You’ll also see a banner in the relevant pane when this happens.
• Rate limit handling now works even when the limit is hit partway through a streamed response, not just at the start of a request.
• Fixed an issue where Boss could misread a background agent’s status as idle when it was actually still working, which could cause premature retries or incorrect status indicators.

Fixes

• Fixed an issue where the hosted MCP gateway was unreachable in production.
• Fixed an issue where opening the billing portal could leave a broken window reference that interfered with subsequent attempts to open it.

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.