Skip to main content

​
Why Orchestrate Agents?

Modern AI coding isn’t about a single prompt—it’s about systems that keep agents aligned, verified, and fast. Zenflow combines workflow orchestration, spec discipline, and multi-agent verification so you get the speed of AI with production-grade reliability.

Structured workflows

Replace ad-hoc prompting with repeatable flows (feature, bug, refactor). Each workflow defines the steps, owners, and artifacts so agents operate like a coordinated team.

Automated verification

Dedicated verifier agents run after builders to execute tests, lint, security checks, or spec validations, preventing regressions before code reaches you.

Parallel execution

Run multiple agents simultaneously—either to cover independent steps (plan, code, docs) or to have different models tackle the same goal and compare outputs.
Orchestration is how AI transitions from a clever assistant to a reliable engineering system. Zenflow provides the structure, verification, and parallelism required to scale output safely.

​
Zenflow’s Orchestration Map

Think of Zenflow in three levels of abstraction—projects, tasks, and subtasks/chats. Each level has its own UI surface and orchestration responsibility.

Projects

The left column keeps projects, task views, and Kanban boards organized so you can fan work out across teams without losing control.

Tasks

The middle column (Task Overview) turns workflows into executable steps, showing branches, status, changes, and commits.

Chats

The right column hosts step-aware conversations, telemetry, and verification streams so you can guide or override any agent run in real time.

​
Projects: Launching Orchestrated Work

Projects define the scope, repository, and automation presets used across tasks. The left column gives you:
  • Project switcher & quick menu – Jump between recent projects, open the current workspace in your IDE, edit metadata, or delete unused initiatives.
  • List ↔ Board toggle – Move between a stacked list and Kanban board. Both surfaces support sorting by Status, Creation date, or Last updated.
  • Task cards with rich controls – Status indicators track each workflow stage and every card exposes Edit, Open in IDE, Duplicate, Archive, or Delete actions.
  • Rapid creation – The global + icon and New task buttons launch the workflow-aware creation modal; in Board view you can add cards directly inside To Do.

Why it matters

Projects aren’t just labels—they determine which workflows run, how automation is tuned, and how many tasks can execute in parallel without stepping on each other.

​
Tasks: Where Workflows Execute

Open any task and the middle column (Task Overview) becomes the orchestration cockpit:
  • Context header – Shows title, dedicated branch, a status dropdown, and the primary Merge button when code is ready to ship.
  • Steps tab – Surfaces plan.md so you can edit steps, add new ones, or toggle Auto-start steps for hands-free execution.
  • Changes tab – Presents diffs from the task branch so you can review what agents changed before committing or merging.
  • Commits tab – Lists every commit created in the task workspace and highlights when none exist yet.
  • Task menu (⋯) – Gives access to Edit, Open in IDE, Duplicate, Archive, or Delete.

Why it matters

This surface turns workflows into executable subtasks so requirements, specs, and implementation plans stay synchronized as agents progress.

​
Subtasks & Chats: Directing Multi-Agent Runs

The right column represents the live agent context:
  • Step-aware tabs – Tabs such as Requirements, Technical Specification, or Implementation mirror your plan so each phase has its own chat log and instructions.
  • Live telemetry – Zenflow streams the active step, shell commands, file reads, and reasoning effort so you can watch agents think and act.
  • Interactive composer – Reference files with @, switch execution modes (DEFAULT, APPROVALS, PLAN), attach artefacts, and inject new guidance mid-run.
  • Add tab / All Tabs controls – Spin up additional chat contexts for new subtasks or quickly switch between existing ones when agents run in parallel.

Why it matters

This is where you clarify constraints, course-correct early, and request additional deliverables (tests, docs, PRDs) without restarting the task.

​
From Projects to Verified Output

  1. Start inside Projects – Choose the project, open the creation modal, and pick the workflow (Quick Change, Fix Bug, Spec and Build, or Full SDD) that sets the orchestration plan.
  2. Drive Tasks through steps – Use the Steps tab to define plan.md, enable Auto-start, and watch Changes/Commits as artifacts materialize.
  3. Guide Subtasks via chat – Monitor the right column to see what each agent is doing, offer clarifications, and let verifier agents run after builders.
  4. Parallelize intentionally – Spin up multiple tasks per project or multiple step-specific chats so planning, implementation, docs, and verification happen simultaneously.
When you orchestrate agents in Zenflow, you’re managing a production system—not a series of prompts. Workflows keep execution deterministic, verification keeps it trustworthy, and parallelism keeps it fast.