Conductor is designed for local-first execution. There is no cloud control plane requirement and no database dependency by default.
What local-first means here
- config in flat files
- tasks in markdown
- work isolated in git worktrees
- sessions run under tmux
- secrets stay in your own environment
Operational restart pattern
If the dashboard looks stale after config or project changes, restart it with the workspace you actually want to serve.
CO_CONFIG_PATH=/path/to/workspace/conductor.yaml \
co start --workspace /path/to/workspace --port 4747
Why teams choose this model
This setup is a good fit when you want orchestration without handing task state, secrets, or code-adjacent metadata to a hosted SaaS product.
Read next
Last modified on March 6, 2026