Changelog

Improvements

• Open-port indicators are now opt-in. If Boss detects that a port is open in your environment, it will no longer surface that information by default, keeping the interface cleaner for users who don’t need it.
• Closed or finished terminal sessions are now cleaned up sooner. Previously, ended sessions could linger in the session list longer than expected; they now disappear promptly once all pending activity is resolved.

Fixes

• Fixed an issue where confirmation prompts appeared without a blank line above them, causing them to run visually into the preceding output.
• Fixed an issue where Boss could misread Claude’s input area when a slash-command menu was open, causing it to type into the wrong place and miss sending the intended message.

Fixes

• Fixed an issue where the session header stopped showing the current status and the spinner that appears while a session is being archived.
• Fixed an issue where Boss could press Enter before a typed command had fully appeared, causing commands to be submitted incorrectly or lost.
• Fixed an issue where links to session endpoints lost the remote host information, which could cause those links to point to the wrong place.

Session timeline

Boss now shows a timeline of your session’s activity directly below the chat list. It combines coding activity with account rotation events in one place, so you can see at a glance what happened and when across a session’s full history.

A few rough edges around this view were also cleaned up: events appear in the correct time order, and a chat that was revived after a failure is no longer labeled as having been replaced.

Improvements

• Park status labels (the reasons a session is waiting or blocked) now use clearer, plainer wording throughout.
• When a pull request has been verified but not yet merged, Boss now shows that correctly as a pending merge step rather than misrepresenting its state.
• Blocked park rows now display correctly, and each block reason is shown once rather than repeated.
• Park timing now dates from when the park started, not from a later point in its lifecycle.

Fixes

• Fixed an issue where a session that failed and was handed off to a fresh agent could still be woken by leftover callbacks from the previous one, causing unexpected behavior.
• Fixed an issue where reviving a failed session could run into a race condition, making the revival unreliable. Several related gaps in the revival process were closed at the same time.
• Fixed an issue where the build receipt for a session could go missing after a push, leaving Boss unable to confirm that a build had completed.
• Fixed an issue where sessions connected to repositories using certain uncommon git remote formats (single-letter hostnames, IPv6 addresses, or ssh.github.com) were not recognized correctly.
• Fixed an issue where the status panel could say “Built by hand” for a commit that simply had no factory review, which was misleading. It now says “No review of the latest commit.”
• Fixed an issue where sessions waiting for a review-only check were not shown with the correct review status.
• Fixed an issue where group headers on the home screen were not rendering in the correct color.

Session timeline

The session detail view has been rebuilt to be much more readable. Steps that happen on different days are now labelled with their date, including steps that appear after you expand the full history. Restart interruptions that happen in quick succession are collapsed into a single entry instead of stacking up as repeated lines. The timeline also wraps and caps correctly so it no longer overflows its container.

Improvements

• A session that has been stopped now shows as “stopped” rather than “idle” across the product.
• On the attention board, a pull request that has passed all checks but has not gone through a formal verify stage is now correctly shown as ready to merge.
• When you link a pull request to a session, Boss now prevents you from attaching a PR or branch that is already owned by another active session.
• Blocked or orphaned sessions hold onto their linked PR and will not accidentally claim a PR that belongs to another session when they resume.
• Linking a PR no longer silently reopens a closed session. Closed PRs also remain visible in the list after being closed.
• The “unsupervised” advisory that can appear on the home screen when Boss is running without supervision now fades away after the first minute of a session, so it does not linger when it is no longer relevant.

Fixes

• Fixed an issue where saving repository credentials could be incorrectly rolled back even though the write had already landed, which could cause credentials to appear missing after a specific database error.
• Fixed an issue where status pill colours and spinners on the attention board were not showing correctly.
• Fixed an issue where the sessions table on mobile could break its layout when a notice appeared alongside a group section.
• Fixed an issue where timeline restart interruptions could be grouped incorrectly when they happened at slightly different times rather than the exact same instant.

Merge is now one step

Previously, getting a pull request merged required separate “approve” and “send-back” actions. Now, pressing m approves and merges in one go. The extra steps are gone.

When a PR has not been verified yet, Boss will ask for a human review instead of jumping straight to a merge attempt. This means fewer situations where a merge is requested prematurely.

Features

• You can now type / on the Home screen to filter sessions by name, making it easier to find a specific session when you have many running.
• Boss now shows a timeline explaining why a session needs attention, so you can see what happened and what is being waited on without digging through logs.
• Sessions that need your attention now appear in a dedicated queue, with notifications to let you know something is waiting.

Improvements

• Verified merges that fail transiently are now retried automatically, reducing the chance that a passing PR gets stuck.
• The repair tool now reports when a proxy port has gone missing, so connection problems are easier to diagnose.
• Stopped sessions are now labeled “stopped” rather than “idle,” which more accurately reflects their state.
• Verification evidence now checks each piece of the change once rather than repeatedly, which makes the verify step faster.
• Post-merge follow-up items are now surfaced in verify notes, so nothing that needs doing after a merge is silently dropped.
• Session actions remain available while an archive is being deferred, so you are not left waiting with a frozen screen.
• Fixed ports that are lost during a proxy session are now reported in the repair doctor, making problems easier to spot.

Fixes

• Fixed an issue where GitHub repository names with mixed letter casing could fail to match, causing integrations to miss events.
• Fixed an issue where multi-line skill commands were not sent correctly, and where a refused send could appear to have gone through.
• Fixed an issue where webhook events could be dropped if a transient error occurred during delivery; those events are now retried.
• Fixed an issue where dismissing a notification could re-trigger it after being parked.
• Fixed an issue where post-merge activity could incorrectly block a verify step from completing.
• Fixed an issue where a session’s detail screen showed a waiting message even after the relevant work had finished.
• Fixed an issue where a FIX row showed a failure state even when the underlying state was not a failure.
• Fixed an issue where verification could pass even if the evidence did not actually cover the change being checked.
• Fixed an issue where inline code formatting in draft PR descriptions was being stripped.
• Fixed an issue where a search filter inside plan checks did not parse its options correctly.
• Fixed an issue where a stopped session was shown as idle in some views.
• Fixed a layout issue on mobile where a notice sitting next to a session group could cause the sessions table to display incorrectly.

Webhook visibility for connected repos

Boss can now warn you when a repository’s GitHub webhooks are not reaching it. If Boss isn’t hearing from GitHub about a repo, it will flag that repo so you know why activity might not be showing up as expected, rather than leaving you to wonder.

Improvements

• Session attention alerts are now actionable from any view, not just the one you happened to have open. You can respond to a session that needs your input without first navigating to it.

Fixes

• Fixed an issue where a session stuck in a repair loop would keep refusing to proceed even after you stepped in to help. Boss now resets that refusal state when you attend to a session, and clears the failure count when you manually unblock it.
• Fixed an issue where conflict repairs could fail permanently if the base branch moved while the repair was in progress. Boss now retries in that case.
• Fixed an issue where a session’s working files could fall out of sync with the actual pull request after a repair or during verification. Boss now re-aligns them before continuing.
• Fixed an issue where a blocked verification step was being treated as needing a code review rather than a fix, which could route your attention to the wrong place.
• Fixed an issue where a coding session could get stuck when its composer was in a draft state. Boss now correctly skips sending into it and reads the right configuration for that session.
• Fixed an issue where MCP authentication tokens were not being picked up from your settings profile, which could cause those integrations to fail silently.
• Fixed an issue where a misconfigured stage could cause problems immediately at startup rather than only when that stage was actually used.
• Fixed an issue where leftover terminal output from a previous attempt could bleed into a new one, causing confusing or incorrect output in session logs.
• Fixed an issue where authentication key lookups could occasionally fail due to a stale cache not being refreshed at the right time.
• Tightened child environment restrictions so that untrusted external code runs with stricter isolation.

Verification and review improvements

Boss’s verification workflow got a meaningful round of polish this release. Approvals now carry forward across a rebase when the actual change to the code is unchanged, so you won’t lose a sign-off just because the branch was rebased on top of a moving base. Relatedly, if a PR was parked waiting for human review but the base branch’s policy later stops requiring that review, Boss will re-evaluate the park automatically rather than leaving it stuck.

The repair flow is also smarter: before carrying a prior review receipt forward, Boss now re-reviews the tree if it has changed since that receipt was issued.

Features

• Session list grouped by attention. The home screen now groups sessions by whether they need your input, so the things waiting on you are easier to spot.
• Repo trust and tool token controls. You can now configure trust settings for connected repos and manage the tokens used by integrated tools, directly from Boss.
• Clearer status labels. Sessions that need a human sign-off are now labeled “needs sign-off” rather than “blocked”, and sessions with live work in progress are kept off the “ready” list until they finish.
• Automatic recovery for stalled runs. If a background run gets stuck or dies unexpectedly, Boss will now resume it automatically, backing off between retries.

Improvements

• Approvals carry across a rebase when the underlying change is identical, avoiding unnecessary re-review.
• Parks that no longer trigger under the current base policy are re-evaluated automatically.
• Boss re-reviews a changed tree before reusing an existing review receipt.
• Old repo API keys are scrubbed from storage when credentials rotate, reducing the window where stale secrets could linger.
• CI evidence that is unreadable or disappears mid-check is now treated as a failure rather than silently ignored.
• Security findings from untrusted sources are rejected rather than ingested.
• Quota used for note syncs that were never applied is now refunded.

Fixes

• Fixed an issue where a blocked unattended run’s draft PR was incorrectly discarded when the run finalized.
• Fixed an issue where a blocked run’s status report moved out of its column during finalization.
• Fixed an issue where a session parked for human review showed as “waiting” instead of “needs human review.”
• Fixed an issue where Boss would not re-evaluate a PR sitting under a stale “needs human” label when a new version of the code arrived.
• Fixed an issue where chat titles you set manually were lost after the first message in certain views, and where rollout bindings did not attach correctly in the same situation.
• Fixed an issue where the merge action for a parked PR was not labeled correctly in the session view.
• Fixed an issue where repair could stall indefinitely when it encountered sessions it was not able to reclaim.
• Fixed an issue where a race on session relaunch could cause the resume key to attach to the wrong chat.
• Fixed an issue where MCP tool calls could hang if the connected tool stopped reading responses.
• Restarting Boss is less likely to leave sessions in an inconsistent state when multiple lifecycle events happen close together.

Organization owners can now manage members’ triggers

Org owners can view, inspect, and stop triggers that belong to any member of their organization. Previously, trigger management was scoped to the individual account; now owners have a fuller picture of what automation is running across their org, and can step in when needed.

A new org-level setting also controls whether members can view each other’s sessions. It is off by default, so sharing stays opt-in.

Improvements

• Boss’s verification flow is smarter about what needs human review. Changes that are purely visual (including shared UI token stylesheet updates) are now parked separately so operators can approve them without re-running the full check. Approved parks can also reuse a previously recorded clean run, skipping redundant work.
• You can approve and send back parked PRs directly from the product, without going to a separate tool.
• Session attention is now computed and surfaced by Boss, so the product can better surface which sessions need your eye on them.
• Credentials are no longer included in stored repository origins, keeping them out of logs and exports.
• Trigger launches are now serialized across server replicas, preventing duplicate runs when multiple instances are active at the same time.
• Access tokens for attaching to a session are now single-use, and tokens are revoked when an account is deactivated. This closes a narrow window where a replayed token could be used after it should have been invalid.

Fixes

• Fixed an issue where Codex sessions could not be launched reliably on systems where the service environment had a restricted PATH.
• Fixed an issue where messages sent in a live Codex pane were sometimes not delivered, and where unconfirmed sends were incorrectly shown as dispatched.
• Fixed an issue where chats were lost after a failed session resume.
• Fixed an issue where a port conflict could occur when multiple proxy connections started at the same time.
• Fixed an issue where session and transcript ownership was not consistently enforced across agent runs.
• Fixed an issue where trying to merge using a pinned version of Boss that the connected host no longer supports would fail silently rather than with a clear refusal.

Smarter code review, now running to completion

Boss’s built-in review step no longer races against a timer. Review rounds now run until they are actually done, so a slow-but-legitimate fix pass no longer gets cut off mid-way and marked as failed. Each round continues until outstanding findings are resolved or it becomes clear no more progress is possible.

The review system has also been rebuilt around a cleaner find-then-verify approach: Boss first locates issues, then separately confirms whether they were addressed. Skill authors get a documented override seam if they need to swap in a custom reviewer.

Features

• Repo trust controls: You can now mark a repository as trusted when registering or updating it with boss repo update --trusted. Boss only injects your project’s secrets and environment into sessions for trusted repos, keeping credentials out of reach for repos you have not explicitly vouched for.
• Approval records tied to a specific commit: When an operator approves a PR, that approval is now bound to the exact commit it was made on. If the PR is sent back for changes and new commits are pushed, the old approval is automatically revoked, so stale sign-offs cannot carry forward to a different version of the code.
• Feature map edits that match the ticket plan auto-merge: Changes to a feature map that were already declared in the ticket plan are no longer flagged for manual review. Only genuinely undeclared edits get parked for attention, cutting down on noise for routine planned work.
• Session activity timeline: Boss now builds a timeline of verification activity for each session, making it easier to see what happened and when across a run.
• MCP HTTP server authentication: The local MCP HTTP server now requires a bearer token. You can retrieve your token with boss mcp token. This keeps the local server accessible only to authorized callers.

Improvements

• Access is revoked promptly when someone’s membership changes or their permission to trigger workflows is removed. Boss re-checks authority at trigger delivery, at launch, and periodically for active connections, rather than waiting for the next natural checkpoint.
• Repo API keys are now stored in the system keyring instead of being passed through git command arguments, reducing the surface where credentials could appear in process listings or logs.
• Boss can now resolve the right cloud account for an organization by type, covering cases where the previous lookup could pick the wrong account.
• Clone URLs are now validated before use, and -- is passed to git clone to prevent dash-led arguments from being misread as flags.

Fixes

• Fixed an issue where a review round could be abandoned before all findings were addressed, because the step was time-boxed rather than outcome-driven.
• Fixed an issue where an approval given on one commit could remain in effect after new commits were pushed following a send-back.
• Fixed an issue where environment variables supplied by a repository could be passed to agent sessions without being treated as untrusted input.
• Fixed an issue where removing a member did not immediately revoke their active connections and daemon tokens.
• Fixed an issue where feature map weakening was judged against the wrong base, leading to incorrect parking decisions.
• Fixed an issue where indented code blocks, HTML comments, and list-item fences in feature map declarations could confuse the parser.
• Fixed an issue where a renamed file was not counted as a changed path during verification.
• Fixed an issue where a ticket description edit timestamp could be read from an entry that did not represent a real edit.
• Fixed an issue where operator approvals were not checked against the correct commit head before being accepted.

Verify merges on its own terms

Previously, if CI was red on the base branch, Boss would refuse to merge a pull request even when the PR itself had passed all checks. Boss now judges a PR’s merge readiness by the CI runs that belong to that PR, not by whatever is happening on the base branch at the time. A flaky or broken main branch no longer blocks your work from landing.

Related: Boss also had a bug where it would count CI runs from release-PR merges against the base branch check, which caused nearly every merge attempt to be blocked. That is fixed.

Features

• Verify now shows what it is waiting for. When a verify session is armed and waiting, the session list now tells you what condition it is holding for instead of looking idle.
• Running Boss as a service is now safer. If you have Boss installed as a system service, boss daemon start will refuse to launch a second, detached copy that could conflict with it. If the service is already running, Boss will connect to it instead.

Improvements

• Secrets passed to a session are now delivered to terminal panes in a way that keeps them out of the process list. Previously they could be read by anyone who ran ps on the same machine.
• Agent worktrees now inherit only an explicit, allowed set of secrets from your checkout’s .env file, keeping unrelated or tool-redirecting keys out of the agent environment.
• When a build completes, Boss now posts the build receipt before moving the associated ticket to “In Review,” so the receipt is visible as soon as the status changes.
• Project config export and apply now compare gate commands by what they actually execute, so a gate expressed differently but running the same command is correctly recognized as unchanged. The “ungated” warning on adopted crons is also fixed.
• Fixed an issue where sessions that produced no output could get incorrectly pushed into the pull request pipeline by the repair process.
• Fixed an issue where a session that produced no output would sometimes not close itself cleanly, leaving stray sessions behind.

Fixes

• Fixed an issue where CI runs associated with release-PR merges were being counted against the base branch check, blocking merges that should have gone through.
• Fixed an issue where zero-output sessions were not ending themselves and left orphaned entries that could be picked up incorrectly at startup.