At a Glance
Interactive
You control every step
Autonomous
Controller runs agents
Continuous
Zero interaction
Hybrid
Mix both styles
Interactive
You respond at every step. Each agent asks questions, gathers insights, and produces output for the next agent. Press enter to proceed and inject the next prompt.When to use
When to use
- Tasks need human judgment at each stage
- You want full control over direction
- Multiple perspectives improve the outcome
See Interactive Example
View a complete interactive workflow with logical flow and technical implementation
Autonomous
Controller agent runs agents on your behalf. You brief the controller agent with your objective and workflow structure. It manages the agents, makes decisions between steps. You review the results instead of managing the process.When to use
When to use
- You have a clear objective but don’t need to control every decision
- The task is too long to babysit
- You want to review results, not manage the process
{USER (username):} or {agent_name:}. You have full control to talk to either at any time.
You can pause anytime to
You can pause anytime to
- Talk to controller agent — give more instructions about the project
- Talk to step agent — give direct instructions for that step
You must brief the controller about the full workflow: what agents it will talk to and what output is expected from each. This keeps it on track. Autonomous is the hardest mode to control, but powerful for long objectives when managed correctly.Both step agents and controller agent must be configured to use the signals MCP. Step agents propose proceeding to the next step, and the controller accepts or rejects. This replaces user interaction.
See Autonomous Example
View a complete autonomous workflow with logical flow and technical implementation
Continuous
Auto-advance with zero interaction. Agents run to completion. You provide a specification file upfront. Agents iterate on it following a well-defined pattern. No pauses, no approvals — just results.When to use
When to use
- The workflow pattern is proven and repeatable
- You have a clear specification file
- Same objective, different inputs each time
See Continuous Example
View a complete continuous workflow with logical flow and technical implementation
Hybrid
Mix interactive and auto-advance agents in the same workflow. Some steps need your input. Others run automatically. Hybrid gives you both — time effective and controllable. This is possible because interactivity is set at the agent level, not the workflow level. Each agent decides whether to wait for you or proceed automatically.When to use
When to use
- Key decisions need you, routine steps don’t
- You want speed without losing control
- Most workflows fit this pattern
See Hybrid Example
View a complete hybrid workflow with logical flow and technical implementation
Choosing a Pattern
Interactive
User Involvement: Every stepBest for tasks needing judgment, exploration, Q&A
Autonomous
User Involvement: Brief controller, review resultsBest for long-running tasks, clear objectives
Continuous
User Involvement: None (spec upfront)Best for repeatable, proven workflows
Hybrid
User Involvement: Key decisions onlyBest for most real-world workflows