Workflow is defined in Markdown, and Crewplane runs the nodes defined in the workflow using native coding CLIs such as Codex and Claude Code. So the control is back to you: different workflows for different tasks with different models, what they depend on, and how they run (parallel or sequential or both). Every input, intermediate output, log, manifest, and final result is preserved on disk so you can trace a run after the fact.
Workflows can be reused and composed into larger pipelines, and interrupted workflows can be resumed. There is no vendor lock in, and it’s easy to adapt your workflows for various tasks - research, design, implementation, debugging, deployment, anything that works as structured procedures.
Give it a try and adapt your own workflows, there is a built-in Mock CLI so you can just try the workflow syntax and composition without worrying about costs (no model calls). Any feedback or suggestions would be greatly appreciated.
Open source (Apache-2.0): https://github.com/crewplaneai/crewplane