Quick Start
pipeline.yaml
How It Works
TheHybridWorkflowExecutor delegates deterministic and agent-centric steps to JobWorkflowExecutor, while handling multi-agent workflow: and parallel: steps itself.
Step Types
Hybrid workflows support all step types from both engines:From Job Workflows
| Key | Type | Description |
|---|---|---|
run: | Shell | Shell command |
python: | Script | Python script file |
script: | Inline | Inline Python code |
action: | Action | Named actions (3-tier resolution) |
agent: | AI Agent | Single agent via Agent.chat() |
judge: | Quality Gate | Evaluate content with threshold |
approve: | Approval | Human or auto approval gate |
Hybrid-Only Steps
| Key | Type | Description |
|---|---|---|
workflow: | Multi-Agent | Execute a named agent from the agents: block |
parallel: | Parallel | Run multiple sub-steps concurrently |
Multi-Agent Steps (workflow:)
Reference agents defined in the top-level agents: block:
workflow: config:
| Field | Description |
|---|---|
agent | Reference to an agent in the agents: block |
action | The task/prompt for the agent to execute |
Parallel Steps (parallel:)
Run multiple sub-steps simultaneously:
parallel: can be any supported step type — shell, script, agent, etc.
Dry Run
Full Example
hybrid-release.yaml
Comparison: Job vs Hybrid
| Job Workflows | Hybrid Workflows | |
|---|---|---|
| Type | type: job | type: hybrid |
| Deterministic steps | ✅ | ✅ |
| Agent steps | ✅ agent, judge, approve | ✅ |
| Multi-agent | ❌ | ✅ workflow: |
| Parallel | ❌ | ✅ parallel: |
agents: block | ❌ | ✅ Named agent definitions |
| Use case | CI/CD, automation | Complex pipelines mixing automation + AI |
Related
Job Workflows
Deterministic + agent steps
Custom Actions
YAML-defined, file-based actions
All Systems
Compare all 8 PraisonAI systems

