Who runs these commands? Most pflow commands are run by your AI agent, not by you directly. You handle setup (installation, API keys, MCP servers), then your agent uses pflow to build and execute workflows. This reference documents all commands so you understand what your agent is doing. See Using pflow for what to expect day-to-day.
Command structure
Command groups
pflow (default)
Run workflows by name or file
pflow workflow
List, describe, discover, and save workflows
pflow registry
Browse and test available nodes
pflow mcp
Manage MCP server connections
pflow settings
Configure API keys and node filtering
pflow instructions
Get AI agent usage guidance
Main command
The defaultpflow command runs workflows. Your agent runs this to execute saved workflows or workflow files it has created.
Run a saved workflow
Run from a file
Natural language mode (experimental)
Natural language mode (experimental)
pflow can generate workflows from natural language, but this feature is experimental. For production use, we recommend letting your AI agent build workflows directly.Natural language requests must be quoted. The planner generates a workflow, which you can save for reuse. Requires an Anthropic API key.
Global options
| Option | Description |
|---|---|
--version | Show pflow version |
-v, --verbose | Show detailed execution output |
-o, --output-key KEY | Specific shared store key to output |
--output-format text|json | Output format (default: text) |
-p, --print | Force non-interactive output |
--no-trace | Disable workflow trace saving |
--trace-planner | Save planner execution trace |
--validate-only | Validate workflow without executing |
--auto-repair | Enable automatic workflow repair on failure |
--help | Show help message |
Planner options (experimental)
Planner options (experimental)
These options apply when using natural language mode to generate workflows:
| Option | Description |
|---|---|
--planner-timeout INT | Timeout for planner in seconds (default: 60) |
--save / --no-save | Save generated workflow (default: save) |
--cache-planner | Enable cross-session LLM caching to reduce costs |
--planner-model TEXT | LLM model for planning (default: auto-detect) |
--no-update | Save repairs to separate file instead of updating original |
Parameter syntax
Pass parameters to workflows usingkey=value syntax:
true/false→ boolean10→ integer3.14→ float'["a","b"]'→ JSON array'{"key":"val"}'→ JSON object- Everything else → string
Stdin input
Pipe data into workflows:${stdin}.
Output modes
Text mode (default)
Human-readable output with progress indicators in interactive terminals:JSON mode
Structured output for parsing:Print mode
Clean output for piping (no progress indicators):Validation mode
Validate a workflow without executing it:Traces
By default, pflow saves execution traces to~/.pflow/debug/:
- Workflow traces:
workflow-trace-{name}-{timestamp}.json - Planner traces:
planner-trace-{timestamp}.json(with--trace-planner)
--no-trace for faster execution.
Instructions command
Thepflow instructions command provides guidance for AI agents using pflow.
| Subcommand | Description |
|---|---|
usage | Basic usage guide for AI agents (~100 lines) |
create | Comprehensive workflow creation guide (~1600 lines) |
AI agents should run
pflow instructions usage when first connecting to pflow. This provides optimized guidance for agent-driven workflow building.Related
- Workflow commands - Manage saved workflows
- Registry commands - Browse available nodes
- MCP commands - Manage MCP servers
- Settings commands - Configure pflow

