Hi,

This release, in numbers

Ten days of work, with almost as much test as code. You are the first to run it.

8 new specialists, and the first optional pack

FlowForge now installs 52 specialists, up from 44. That includes a legal org (a head plus a Brazil specialist and a US specialist), a release operator that runs a release up to the point where you give consent, and a marketing head with developer-relations and product-marketing specialists under it. The database specialist was split in two: fft-database-architect designs and never opens a connection, and the new fft-dba is the only agent that may touch a live database, through flowforge db and only under your grant.

The first optional pack ships too: flowforge agents install recebimento-medico adds two Brazilian medical-billing specialists. It installs only if you ask for it. Every specialist is listed at flowforgesoft.com/agents.

ACE that acts

ACE now reads one recap of the fleet. Where a reading is not available it says UNKNOWN instead of guessing, and ACE checks the newest recap before it ends a turn. Failures and questions reach ACE first, and only a decision that is really yours pages you. Behind it, five remedies run in the FlowForge daemon. Two act today: one delivers a review's findings to the worker that owns the pull request, and one nudges a worker that has gone quiet. The other three only watch for now and record what they would have done. I'd rather tell you that than let you think they act. A worker stuck on a permission prompt, or on a /goal that never armed, now shows up as a row that says why.

The Fleet screen and the Workers queue

Both screens now read one shared picture of every worker. On the Fleet, every live session is a lane, a stale worker included. If the daemon is down, a banner says so and nothing vanishes. Select a lane to see its detail and a peek. The Workers queue tells you, on every row, how long a worker has been quiet, how many review rounds its pull request has had, and which wave it belongs to. Rows are grouped under headers. Press ? and help explains every symbol, generated from the screens' own tables, and the columns finally line up.

The War Room tells the truth

Cards no longer vanish from a sprint board when another read lands. A ticket with an open pull request sits in Review, not To-do. The board says when it is stale, and r really re-reads it. You can now choose what the War Room reads: one sprint, one milestone, the standalone tickets, or everything updated since a date. A row under the title says which, and your choice is remembered for each project.

What you told us

A worker killed by an out-of-memory error or a reboot is now found. Its uncommitted work is saved to a rescue branch, and it is respawned with a brief that names the rescue. Workers start on the sprint's own base branch. flowforge merge closes the ticket its pull request owns. A fresh GOLDEN merges on the verdict instead of waiting out an unrelated back-off. A worker's brief carries your project's standing rules from .flowforge/worker-brief.md. Your own Claude Code status line stays yours, and re-emitting an amended plan no longer duplicates every ticket. There are seventeen findings in this round alone, and every one is on the release page with its pull request.

Sign in, Windows and the desktop

The sign-in screen owns the whole screen, the password field takes input, and the desktop sign-in always ends with an answer. You can sign in to Claude Code, or switch accounts, from a menu without opening a terminal. FlowForge runs on Windows through WSL2: the install prepares the Windows side by itself and puts Desktop and Start Menu launchers in place. In the desktop app, the preview has become a reader, with find, zoom and "On this page", and you can ratify a plan right on the page.

Colado

Colado is a jiu-jitsu term for a position with no gaps: justo, perfectly adjusted, full pressure. It's the name we gave the FlowForge gates that leave no space between the rule and your work. This release closes six more. A merge can no longer land under a worker that is still editing. Two drivers can no longer fire the same wave run. An epic can no longer be spawned as work. A merged pull request can no longer close a ticket it did not declare. A verdict can no longer be spent on a branch it never judged. And a spawn can no longer report a worker that does not exist.

Small things that change everything

macOS stops asking whether FlowForge may access data from other apps. A licensing server error reads as a server error, not "check your connection". Ctrl-O is the escape hatch to ACE's own Claude Code session again. A wave reads ≈1, never W0, because W is for workers. And every clock you read is in your own time zone.

One setup step

Quit and relaunch every open cockpit after you update, so the new screens are the ones running. On Linux or WSL, if the desktop app refuses to start, install the GLES runtime your distribution names: libgles2 on Debian and Ubuntu, libglvnd-gles on Fedora and RHEL, libglvnd on Arch. flowforge doctor tells you before the app does. If your workers need standing rules, such as a memory limit for your test runner, put them in .flowforge/worker-brief.md.

Not yet

Three of the five remedies only watch for now. Ordering a rebase on a conflicting pull request and starting an owed review are recorded, not done, so those two still need ACE or you, and the reap of a vanished worker only records. A long single line pasted into ACE still has not been reproduced. A related fault, where a pasted message with line breaks painted over the Workers pane, was found and fixed. If you still see the single-line overflow, a screenshot settles it. And Team Tier is plans only in this release, nothing you can use yet.

How this letter reaches you

This letter comes out of FlowForge's own release pack: the same tooling keeps the release notes, the release page and this letter derived from one committed source. The same pipeline, which renders, exports to .eml and sends at promote, is in your own Settings. It is opt-in and off by default.

Unsubscribe from release letters · Manage preferences · Privacy

FlowForge · v1.2.26 · sheet 1/1