Changelog

Filtering gets a full upgrade across the web app

Every list in the Bossanova web app, including sessions, repositories, cron jobs, daemons, and accounts, now uses a consistent filter bar modeled after Linear’s filter UI. Filters sync to the URL, so you can bookmark or share a filtered view and it will open exactly as you left it.

The new filter bar supports picking multiple values at once, inverting a filter to “is not”, and editing an active filter directly from its chip without reopening the whole menu. When you have more than a handful of values selected, the chip shows a count instead of listing every name, keeping the bar readable. The last daemon filter you chose also follows you between lists, so you do not have to re-apply it every time you navigate.

Features

• Read issue descriptions from the CLI. You can now retrieve a stored issue description from the tracker command line, not just write one.
• Sweep migration support. Boss now includes the internal pieces needed for migrating between sweep configurations, along with documentation for the migration path.

Fixes

• Fixed an issue where drafting a plan headlessly and flipping the epic parent could silently apply a clamped estimate without warning, because the parent’s details were never re-read after the switch.
• Fixed an issue where filters applied from the URL could be lost on navigation if the page had not finished loading when the filter state was seeded.
• Fixed an issue where opening a filter facet on a small screen could trigger incorrectly on hover instead of tap.
• Fixed an issue where the empty-state message on filtered pages used the wrong plural form.
• Fixed an issue where a returned-to session would lose its highlight when a seeded filter was active.
• Fixed an issue where clicking a row in the filter menu would keep the menu open; picking a row now closes it, while using the checkbox keeps it open so you can select multiple values without extra clicks.
• Fixed an issue where a selected organization was shown by its internal key instead of its display name when below the facet grouping threshold.

Binary drift detection

Boss can now tell you when the CLI you are running does not match the background service it is talking to. Running boss doctor or boss env will flag the mismatch directly, so you know to restart or update rather than chasing a confusing error.

Improvements

• When multiple Boss sessions happen to pick up the same ticket at the same time, they now detect each other and back off, so work is no longer duplicated silently.
• Boss can now filter the pool of planned tickets it picks up using label-based selection rules. If you have configured a selection, the build worker and the gate that feeds it now apply the same filter, so nothing slips through or gets dropped unexpectedly.
• Plans are now checked at authoring time for claims that cannot be verified, such as criteria with no measurable threshold or research that cannot be located. Catching these early means less drift between what was planned and what actually gets built.
• Temporary files created during a run are now kept in a private, named directory per session. This prevents concurrent sessions from stepping on each other’s scratch files and stops cleanup from accidentally deleting another session’s work.
• Review findings that cover regressions now get their own reserved fix round, so they cannot be silently crowded out by the general fix budget.
• When Boss evaluates test gates, it now checks that a failing test would actually go red for the kind of change being made. Gates that would pass vacuously are now flagged rather than accepted.
• Ticket assignee and creator are now available as identity filters in the gate libraries, so you can scope which tickets Boss acts on by who owns them.
• CI gate reads now validate that the checks they inspect actually ran against the current commit, rather than accepting a stale or mismatched result.
• Installed skill drift reports now correctly identify what is out of date, in which direction, and what to do about it, and the repair holds for the full duration of a run.

Fixes

• Fixed an issue where boss chat show would fail on large chat sessions, crashing before it could display anything.
• Fixed an issue on iOS where opening the keyboard would push the top navigation bar off screen in the chat view.
• Fixed an issue on mobile where the session filter bar would scroll away with the list instead of staying anchored at the top.
• Fixed an issue where gate results could be misread from cache, causing a passing result to be reported when the underlying checks had actually failed.
• Fixed an issue where shell scripts in skills could produce incorrect exit codes or silently pass under certain shell configurations, particularly with piped commands and glob patterns.
• Fixed an issue where tracker reads and writes could fail silently, return empty results, or not be retried when a transient error occurred.
• Fixed an issue where commits could end up untagged or a push could be reported as successful when it had not fully completed.
• Fixed an issue where a Codex chat session could fail to attach to its rollout on startup, leaving the session in an unresponsive state.
• Fixed an issue where dispatched background tasks had no reliable way to confirm they were still running or had completed, which could cause work to be lost or reported incorrectly.
• Fixed an issue where plan description comparisons could produce a false drift verdict after a legitimate write.
• Fixed an issue where UI screenshot capture could misroute changes that only affected non-visual code, leading to incorrect proof attempts.
• Fixed an issue where missing installation errors were not always surfaced clearly, making them harder to diagnose.

Fixes

• Fixed an issue where certain configuration blocks with commented-out headers were not parsed correctly, which could cause Boss to misread or reject otherwise valid files.

Fixes

• Fixed an issue where certain YAML values spanning multiple lines were not parsed correctly, which could cause tools or configurations that use that style of YAML to fail or behave unexpectedly.

Boss Epic: run multiple epics together, with reliable progress tracking

Boss can now coordinate several epics in a single run. Instead of kicking off epics one at a time, you can point Boss at multiple starting points and it will work through all of them together, prioritizing work that unblocks the most downstream tickets first.

Alongside that, the epic driver now tracks each run as a durable sequence of steps. If something is interrupted mid-flight, Boss can pick up where it left off rather than starting over. Progress is reported per epic, so you can see what each one is doing without the updates blurring together.

Improvements

• When you send a chat message through Boss (via the CLI or any connected tool), it is submitted immediately by default. Previously you had to opt in to submission explicitly; now the expected behavior is the default.

Fixes

• Fixed an issue where Boss could crash with a “send on closed channel” error when shutting down a stream that had multiple active writers. This was intermittent and hard to reproduce, but could cause a session to drop unexpectedly.

Fixes

• Fixed an issue where closing Boss would lose your in-progress chat sessions. Chats are now preserved on exit so you can pick up where you left off.
• Fixed an issue where re-opening a session with no content would let you attach to an empty chat. Boss now declines to reattach in that case, so you land somewhere useful instead of a blank slate.

Fix: PR status no longer gets hidden by an idle chat

When a pull request was verified and ready to merge, Boss could show a “waiting” indicator instead of the green verified status. This happened when a chat session had queued up a follow-on action in the background. The waiting state would take over, obscuring the fact that the PR had already passed review.

Boss now correctly surfaces the verified-green PR status in these cases, and the waiting indicator steps aside rather than covering it up.

Smarter watch conflict detection

When Boss monitors two conditions that can never both be true at the same time, it now warns you instead of silently setting up a watch that will never fire. Previously, that kind of misconfigured watch would sit there armed but unsatisfiable, with no indication anything was wrong. Boss now catches the conflict at the moment you register it and surfaces a clear warning so you can fix it before it quietly does nothing.

Improvements

• Boss handles pasting multi-line text into Codex prompts correctly now. Previously, pasting a block of text could produce garbled or broken input.
• Boss is better at following up on work it started: it now re-checks CI results and returns to unfinished tasks more reliably rather than leaving them hanging.

Fixes

• Fixed an issue where a split-group callback registration would fail silently, leaving a watch armed that could never be satisfied.

Boss now follows through on unfinished work

When Boss submits a pull request, it now waits for CI to finish and checks the results before considering the task done. If tests fail, Boss goes back and addresses them rather than stopping at “PR opened.” Similarly, if Boss set something aside mid-task, it now reliably picks that work back up on re-entry instead of leaving it half-done.

This changes the experience from “Boss hands off and hopes for the best” to “Boss sticks around until the work is actually complete.”

Improvements

• Boss’s responses during skill execution are more direct. Removed some older, verbose patterns that were getting in the way of clear output.

Fixes

• Fixed an issue where visiting the site without www could fail to load correctly.