What's coming next.
No dates, no promises. Priorities shift when users push back, so if something below matters to you, say so on Discord.
The whole flow, from your phone.
Start a piece, walk it through the flow, spawn a session, get notified when something needs you, and review your work. Control your factory from your phone. End to end encrypted.
Drive it from the terminal.
Fermata can expose itself as an MCP server, so a Claude Code session in your terminal reads and drives your pieces without switching windows. An agent outside Fermata can file new work into your Backlog too, spec and all, where it sits inert until you release it.
Not just Claude.
Today the engine runs Claude. Next you pick the model for each stage: plan with one, code with another, review with a third, without changing how the factory works.
Every run teaches the next one.
When a piece closes, Fermata proposes what it learned about your codebase. You approve or edit it, and future runs start with it instead of relearning the hard way.
Work arrives on its own.
Streams connect the trackers you already live in. Tracks are the cards they produce, waiting for your approval before any of them becomes a spec.
Past one desk.
Shared projects and pieces for small teams, without giving up the local, private core that makes it yours in the first place.
Something missing? Tell us on Discord.