Hi,

This release, in numbers

You ask me one question every time I write one of these: does FlowForge make you faster. So from now on every release states its numbers plainly — tests outnumber code, and a third of the cycle went to fixing bugs, not building anything new. I'd rather say that than spin it.

Radio and the K.I.T.T. spectrum

Press J and a full screen of radio opens — no cockpit rows spent. Search 30,000 stations, play, stop, and mark a favourite with f; F shows every one you've ever kept. Watch the K.I.T.T. spectrum sweep from the centre outward, red to white, while it plays. It plays on macOS and on Linux, through PulseAudio or PipeWire. A resting radio costs the cockpit nothing.

What you reported

The Gantt as a planning instrument

ADR-0130 makes the Gantt a real planning instrument. Every sprint's data date prints on the frame, so a stale read never looks fresh. Duration, effort and elapsed are three fields, each bar starting at the ticket's first session, not its creation date. Dependencies carry a type and a lag, the critical path carries total and free float, and eight bars stacked on one person are named as the conflict they are. Percent complete is counted in hours — the same hours your timer records to pay you — so nobody is ever asked how done they feel.

The War Room got fast

The War Room used to repaint a busy fleet ten times a second, redrawing bytes that hadn't changed. Measured with a fleet open and nothing typed: repaints per second, 11.675/s → 1.675/s (#5689). Press Up now and the selection moves while the viewport holds still, and a refresh that finds nothing never blanks a board that was already full.

Colado

This release ships the first customer-visible seals in that family.

A billing identity that used to drift between machines now fails closed to one, healed the moment a session starts. The rule behind it — fail closed, no exceptions — is written down once now, so the next gate inherits it instead of re-deciding it for itself.

A merge can no longer go through on a check that never ran — on a plan with server-side enforcement. Where that enforcement isn't available, the backstop says so plainly, never a false all-clear. Your protected branch gets the same honesty: a check that can't read it is never reported as if it passed.

Autofire stopped confusing a plan waiting on your sign-off with a broken build — it opens for ratification instead of reporting red. An old Claude Code version now says so by name, instead of reading as a FlowForge defect. One more gap closed the same way, from outside that family: the CI setting that said main-only while your repository ran it on other branches too now reads the workflow back and says what actually runs — because the gap between the two was billed minutes you never expected. And the door FlowForge opens to your own ticket system is inventoried and locked down, seam by seam — a second provider is a change in one place, not a rewrite.

Small things that change everything

A backtick typed into any cockpit field used to open a terminal instead of reaching your text; now it's just a letter, and the terminal has its own chord. An ACE reply used to silently drop any line containing the word "token" — so the answer you were waiting for never arrived; now it reaches you, and a section that is genuinely empty says so instead of leaving a bare heading.

ACE's window used to land wherever tmux put it, with quitting as the only way back to the cockpit; now it opens at a pinned slot and one key brings it home. flowforge doctor used to flag your own custom agents as an install defect; now they don't count against you.

Your commits used to carry a Co-Authored-By line your own FlowForge wall then refused; the install now switches it off where it is written, so a commit is right the first time.

And you can now choose ACE's model — Opus, Fable or Latest — in Settings, applied to the session you're already running, so a better model never needs a FlowForge release.

One setup step

Four things ship their code here and switch on once one setup step lands: marketing consent (its data functions), the new subscription verbs (configured per account), company-membership writes (new data functions), and the new English voices, which fetch from HuggingFace until our own CDN mirror job runs.

Not yet

Team tier's visible half still needs a production step and a console change. The post-checkout page no longer promises an email it cannot send — no payment webhook is registered yet. ACE speaking to the spectrum waits on the voice sidecar cut.

How this letter reaches you

This letter comes out of FlowForge's own release pack — the same tooling that keeps the release notes, the deck and this letter itself derived from one committed source. For v1.2.22, I'm still sending it by hand.

I'm announcing what's coming in v1.2.23: the same feature, for your own product. A release letter and a release page generated from your own release notes, sent to your own customer list. It will be opt-in, in Settings, off by default.

* Requires a transactional email service account — Resend, Mailgun, SendGrid, Amazon SES or Postmark — configured in Settings.

Unsubscribe from release letters · Manage preferences · Privacy

FlowForge · v1.2.22 · sheet 1/1