Crewplane Documentation
July 4, 2026 ยท View on GitHub
Crewplane turns coding-agent CLI calls into explicit, resumable workflows with local run records on disk.

Start By Goal
| Goal | Start here |
|---|---|
| Understand what Crewplane is | Why Crewplane? |
| Try it safely without real agent calls | Installation, then Quickstart |
| Prepare a real provider | Quickstart, then Provider setup |
| Follow the guided tutorial track | Running workflows |
| Look up exact syntax and config | Workflow syntax, Configuration, Commands |
First Project Path
For a first project, keep this order:
- Install Crewplane.
- Run
crewplane init. - Run
crewplane validate. - Run
crewplane runwith the generated mock invoker. - Inspect the run record.
- Run
crewplane onboardingwhen you are ready to prepare one real provider.
For details, follow the Getting Started pages in order before moving into the guide track:
- Why Crewplane?
- Installation
- Quickstart
- Provider setup
- Continue to Running workflows.
Guided Tutorial Track
These guides are written to be read in order. Each page ends with a Next
section that continues the tour.
- Running workflows
- Watch Runs Live and Inspect Results
- Inspecting Run Records
- Workflow authoring
- Node modes and provider roles
- Review loops
- Findings artifacts
- Workflow composition
- Optional: Experimental workspace isolation can be omitted unless you need isolated source-tree edits.
- Mock validation
- Troubleshooting
- Reproducible support bundle
- Cleanup
Jump In By Task
Feel free to jump around based on what you need right now:
- Run a workflow: Running workflows
- Inspect outputs: Inspecting Run Records
- Write workflows: Workflow authoring
- Configure provider roles and reviews: Node modes and provider roles, Review loops, Findings artifacts
- Reuse workflows or isolate file edits: Workflow composition, Experimental workspace isolation
- Debug or share a run: Troubleshooting, Reproducible support bundle
- Clean generated state: Cleanup