v2026.09.2
Released 2026-09-15.
Features
Section titled “Features”-
Filter the board with one expression, and save it as a view. The filter bar used to be a row of separate controls, one per kind of condition, which had no way to say “hide done tickets” or compare a number or a date. It is now a single expression —
-status:done assignee:@me due:<2026-10-01— shown as chips you can remove one at a time, and buildable from the + Filter menu if you would rather not type it. Custom fields can be compared too, and are stored by their ID, so renaming a field does not break a filter that uses it.@meandsprint:activeare kept as written and worked out for whoever is looking, so a link you share shows each person their own tickets rather than yours. The same filter applies to Kanban, Planning and Table, is carried in the URL, and is remembered per project in your browser. Give it a name and it becomes a saved view the whole project can pick. A token that does not make sense is shown in red and ignored on its own, instead of emptying the board. -
Minions can ask for tickets with the same expression. A minion can pass a board filter when it lists a project’s tickets.
@memeans the minion itself, so a view someone built for “my open tickets” works for a minion as it is. -
Run an assessment from your own website or service. A catalog can now be driven from outside through an integration key you issue from the catalog editor, so a visitor on your site can answer the questions and a result lands in your workspace. Only the questions and the figures you present leave HQ — contribution amounts, rates, the conditions behind them and the breakdown never do. A key only reaches the sessions it created, the key itself is shown once and stored only as a hash, and a catalog stops being reachable the moment its last key is revoked. When an outside session closes with at least one answer you are notified (email is off by default). Finalizing a result stays a human decision.
-
See where every assessment stands. The assessment list now labels each one as in progress, awaiting review or finalized, and can be narrowed by state, catalog, where it came from and whether anything was answered. Sessions abandoned before a single answer are tucked away by default, and an assessment can be deleted straight from the list.
-
Edit a catalog as tables you can compare. Every tab of the catalog editor used to stack one expanded block per item — thousands of pixels tall for a real catalog — which made the side-by-side comparison that calibration depends on physically impossible. Each tab is now a table with one row per item and only the selected row expanded. Filter chips pull out exactly the items that need attention, such as values still based on intuition. Groups of contribution items can be created and renamed from their heading, which also shows how much of each measure the group accounts for. Tabs now follow the order you calibrate in — measures, then contribution items, then facts — and the verdict sits under the measures it reads. Units can be edited for every kind of measure, and a measure nothing contributes to is marked.
-
Start a catalog from blank. Creating a catalog used to mean copying a sample and deleting its contents. You can now start from blank, or add a sample from a menu that says in one line what each one teaches. There are four: an introductory logo design quote, a website production quote, a deal go/no-go decision and a hiring screen — smaller than before, so their structure can actually be read. Catalogs already in your workspace are not changed, and adding the same sample twice now gives it a numbered name instead of failing.
-
Give each CMS content type its own preview route. A site could hold only one preview URL, so when the blog and the portfolio were built as different pages, one of them always previewed in the wrong place. Each content type can now set its own preview target, or inherit the site’s when left empty, or switch preview off for types such as site settings that have no page of their own. Content type editors can set it themselves, and the content type is still sent with every preview, so a site with a single shared preview route needs no changes.
Improvements
Section titled “Improvements”-
JSON views fold by structure. The raw JSON shown for DAG executions and fixtures, assessment catalogs, document templates and chat tool calls now folds deeper levels by default, so a 1,400-line catalog opens as about 100 readable lines. Unfolded, it is exactly the JSON a minion would push. Short payloads are shown as before. Folded sections are not found by the browser’s find-in-page until you expand them.
-
Deleted catalog items are easier to find and bring back. The “Show deleted” toggle now sits next to the list it filters, shows how many items it would reveal, and explains that deleted items are kept and can be restored from their row. It also no longer makes the header jump when you switch to editing.
-
Links open in the right workspace. A link to a note, project, ticket or similar page read as “not found” whenever the person opening it was last working in a different workspace, even though they had access — and it never reproduced for the person who shared it. If you are a member of the linked workspace, HQ now switches to it and tells you once that it did.
-
Quick add no longer duplicates tickets. A column’s + field created the ticket as soon as you clicked away. With a sprint active, that ticket was hidden by the default sprint filter, so it looked cancelled and people added it again. Tickets are now created only when you press Enter. A failed create keeps what you typed and shows an error so you can retry.
-
No more filters you cannot see. The filter bar only appeared on Kanban, yet its conditions still narrowed the Table, so switching views could leave tickets hidden with no way to clear the filter. Every condition in effect, including the active-sprint focus, is now a visible chip on every view.
-
Japanese input on the board. Pressing Enter to confirm a conversion saved the unconverted text, and pressing Escape to cancel a conversion closed the field.
-
The parent picker skips finished epics. Tickets can no longer be filed under an epic that is already done, though a ticket’s current parent still shows even if it has since been completed.
-
Catalog tabs no longer swallow vertical swipes on touch screens.
Includes @geekbeer/minion 5.11.2.