What Makes Up a Workflow
Every workflow has: Optionally, workflows can also include:- Separators - Visual dividers between workflow phases
- Tracks - Different workflow paths users can choose from
- Condition Groups - Questions to customize which steps run
- Sub-agents - Additional agents the workflow can use
- Controller - An agent that guides users before the workflow starts
- Modules - Main agents with loop ability
- Specification - A project brief needed before starting
- Autonomous Mode - Who drives the workflow (you or the system)
How Workflows Execute
Workflows run step by step. Each step contains an agent that performs work, produces output, and passes context to the next step.Onboarding
If tracks or conditions are defined, user answers questions to configure the workflow path.
Step Execution
Each step runs its agent. The agent receives prompts, uses tools, and produces output.
Workflow vs Agent
| Concept | What It Is | Scope |
|---|---|---|
| Workflow | Execution plan | Orchestrates multiple agents |
| Agent | Engine session | Executes a single step |
One workflow can have many agents. One agent belongs to one step.
Components
Name
The workflow name defines the objective of the overall workflow. It’s what users see when selecting which workflow to run. A clear name helps users understand what the workflow will accomplish before they start.Define Your Workflow Name
See how to name your workflow
Steps
Steps are agents set in sequence. The arrangement matters for execution because each step receives context from previous steps. Every workflow requires at least one step. Each step runs an agent that performs work and passes output to the next.Configure Your Steps
Learn how to set up workflow steps
Separators
Separators are visual dividers that organize your workflow into phases. They appear in the TUI timeline to help users understand workflow progress.Add Separators
Learn how to add visual dividers to your workflow
Tracks
A track is a workflow variant, a path that determines which version of the workflow runs.- Users pick one track (like choosing a route on a map)
- Each step can belong to specific tracks
- If a step doesn’t belong to the selected track, it’s skipped
Configure Tracks
Learn how to set up workflow tracks
Condition Groups
Conditions are feature flags, options that control which steps run based on what’s needed.- Users can select multiple conditions (like checkboxes)
- Steps can require all selected conditions to match
- Steps can also run if at least one condition matches
Configure Condition Groups
Learn how to set up workflow conditions
Sub-Agents
Sub-agents are specialized helpers that main workflow agents can call upon to handle specific tasks. Think of it like a manager delegating work to team members with different expertise:- Main Agent: “Project Manager”
- Sub-Agent: “Frontend Developer” (builds UI)
- Sub-Agent: “Backend Developer” (builds API)
- Sub-Agent: “QA Engineer” (writes tests)
Configure Sub-Agents
Learn how to set up workflow sub-agents
Controller
A controller is a conversational guide, an agent that talks to the user before the main workflow starts. It’s like a project intake meeting: the controller asks questions, gathers requirements, and plans before the automated work begins. How it works:- Controller starts and begins a conversation
- User chats with controller (asks questions, provides context)
- User presses Enter with no input to signal they’re ready
- Workflow steps execute
Configure Controllers
Learn how to set up workflow controllers
Modules
Modules are main agents with loop ability. They can repeat their work until a goal is reached. Unlike regular agents that run once and finish, modules can cycle back and refine their output based on feedback or changing conditions.See Modules in Action
View real workflow examples using modules
Specification
A spec is a plain text document (markdown) that describes what you want to build: your project’s goals, requirements, and context. It’s like a project brief you hand to a team before they start working. You can set a workflow to never start without a spec, ensuring the agents always have clear direction.Configure Specification Mode
Learn how to require specifications
Autonomous Mode
Autonomous mode controls who drives the workflow: you or the system.- Always autonomous - The system runs everything automatically. You can’t pause or intervene.
- Never autonomous - You stay in control. The system won’t proceed without your input.
- Toggle - You can pause anytime to orchestrate manually, then hand control back to the system.
Configure Autonomous Mode
Learn how to set up autonomous mode
Import Workflows
Imports are external workflows built by the CodeMachine team or community.- Shared via external repos
- Contains workflows, agents, prompts, and config
- Install via TUI or CLI
- Anyone can share, anyone can install