Start in v2 Without Rebuilding v1 – June 2026
This month, our focus was on making the v2 Platform easier to adopt, easier to work in, and more practical for day-to-day Workflow development.
A key update is support for calling v1 Workflows directly from v2. This means you can start building new work in v2 without having to rebuild existing v1 integrations first. Add the Sub Workflow step, point it to the relevant v1 Workflow, and continue from there. No additional setup is required.
We’ve also improved the Workflow build and debugging experience. You can now run a single step, run a Workflow up to a specific step, and view recent activity logs for an individual step. These changes are designed to make testing and troubleshooting more focused, especially when working through larger or more complex workflows.
Builder MCP Server – May 2026
Last month, we introduced Builder MCP Server, a new way for AI agents to create Flowgear Workflows from outside Flowgear.
Builder MCP reflects a broader shift in how teams are building. Instead of switching between an IDE, an agent, and Flowgear to create or update backend logic, builders can stay in their development environment while their AI agent creates the Workflow backend the application needs.
It works with IDE-based agents such as Codex or Claude Code, as well as desktop agent apps. Once connected, the agent can create Workflows directly, combining backend logic, integrations, and Flowgear’s governed execution model into the build process.
Builder MCP Server – April 2026
This month, we are introducing Builder MCP Server. It gives AI agents a way to build Flowgear Workflows from outside Flowgear.
Until now, building an app in your IDE while relying on Flowgear Workflows for data meant switching contexts whenever a Workflow needed to be created or updated. That interruption added friction to the build process.
Builder MCP changes that. Your AI agent can now create the Workflow backend your application needs while you stay in your IDE and keep moving.