Quick Start
1
Simple Usage
pipeline.yaml
2
With Configuration
pipeline.yaml
3
Run programmatically
type: hybrid and routes automatically. Previously only the praisonai workflow run CLI did this; the programmatic API now matches.
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
Hybrid-Only Steps
Multi-Agent Steps (workflow:)
Reference agents defined in the top-level agents: block:
workflow: config:
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
Best Practices
Start with dry run
Start with dry run
Use
praisonai workflow run pipeline.yaml --dry-run to validate step order and agent references before executing shell or deployment steps.Define named agents for reuse
Define named agents for reuse
Put multi-turn agents in the top-level
agents: block and reference them with workflow: steps — keeps prompts and model settings in one place.Mix parallel and sequential wisely
Mix parallel and sequential wisely
Use
parallel: for independent checks (lint, security, type-check) and keep dependent steps sequential to preserve output files like RELEASE_NOTES.md.Use flags for environment control
Use flags for environment control
Define
flags: in YAML and reference them with if: expressions so the same pipeline works in CI and production without duplicating files.Related
Job Workflows
Deterministic + agent steps
Custom Actions
YAML-defined, file-based actions
All Systems
Compare all 8 PraisonAI systems
Workflows
Multi-agent workflow patterns

