Every meaningful release with a full write-up of what changed. Pre-GA versioning, honest about what is live versus still hardening.
The levels now read Assistant › Agency › Agent › Role › Bot. An agency is a team of agents (Client support), an agent is one focused job (CSA), a role groups the bots that do one part of it. Agent city shows them as streets, buildings, floors, rooms and bays.
Everyone who joins gets a link. Friends who join through it move them up the line, and once those friends get going, both get 5,000 bonus runs. Agencies and creators can apply to be partners.
Admin → Economics shows what a customer costs to win and to serve, retention and what one customer is worth, on one screen. Every figure is labelled Actual or Estimate.
Bring your n8n workflows and Make scenarios over as bots, test them against your past runs, and switch over when you are ready. Every import arrives switched off, and nothing goes live until you say so. The same steps are available to your assistant over the MCP.
A workflow is now a bot. The level that was called an agent is now a sub agent, and the level that was called a task is now an agent. The MCP tools and the REST API follow, with the old bot and step names still answering.
A new public site built from a pixel spec (paper, LED-dot numerals, three glass cards on real metrics), formal sign-in / sign-up screens, a waitlist with two house emails, and the app and admin consoles rebuilt around a full-height glass rail, a floating pill and a run-detail screen that shows the real canvas. The bot canvas itself is unchanged; ten app icons are now self-hosted.
Every node field now works like n8n — a per-field Fixed/Expression toggle with schema-reference chips — resource mappers add all columns by default, autosave settled to once a minute, and the Podio workspace picker was fixed.
A full marketing rebuild — content floats over a scroll-driven holographic fly-through, navigation moved to a floating glass hotbar, and three company pages landed.
The execution engine gained deep handlers for the core connectors, and OpFlow shipped an MCP server so an agent can build and run bots conversationally.
Reliability became a feature of the engine, not a plan tier — and bots gained the primitives to compose.
Time-based triggers, and the credit model that defines how OpFlow bills.
OpFlow went live in production at flow.opscend.net.
The core execution engine and the visual editor.