FAQ
Frequently asked questions about Chief.
General
What is Chief?
Chief is an autonomous PRD agent. You write a Product Requirements Document with user stories, run Chief, and watch as your code gets built—story by story.
Why "Chief"?
Named after Chief Wiggum from The Simpsons (Ralph Wiggum's dad). Chief orchestrates the Ralph loop.
Is Chief free?
Chief itself is open source and free. However, it requires an agent CLI with its own access:
- Claude Code (default) — requires a Claude Pro subscription or Anthropic API access
- Codex CLI — requires an OpenAI API key
- OpenCode CLI — supports multiple model providers
What models does Chief use?
Chief uses whatever model is configured in your agent CLI. Each agent has its own model selection—see your agent's documentation for details.
Usage
Can I run Chief on a remote server?
Yes! Chief works great on remote servers. SSH in, run chief, press s to start the loop, and let it work. Use screen or tmux if you want to disconnect.
ssh my-server
tmux new -s chief
chief
# Press 's' to start the loop
# Ctrl+B D to detachHow do I resume after stopping?
Run chief again and press s to start. It reads state from prd.json and continues where it left off.
Can I edit the PRD while Chief is running?
Yes, but be careful. Chief re-reads prd.json between iterations. Edits to the current story might cause confusion.
Best practice: pause Chief with p (or stop with x), edit, then press s to resume.
Can I have multiple PRDs?
Yes. Create separate directories under .chief/prds/:
.chief/prds/
├── feature-a/
└── feature-b/Run with chief feature-a or use the TUI: press n to open the PRD picker, or 1-9 to quickly switch between tabs. Multiple PRDs can run in parallel.
How do I skip a story?
Mark it as passed manually:
{
"id": "US-003",
"passes": true,
"inProgress": false
}Or remove it from the PRD entirely.
What are worktrees?
Git worktrees let you have multiple checkouts of a repository at the same time, each on a different branch. Chief uses worktrees to isolate parallel PRDs so they don't interfere with each other's files or commits. Each worktree lives at .chief/worktrees/<prd-name>/.
Do I have to use worktrees?
No. When you start a PRD, Chief offers worktree creation as an option. You can choose "Run in current directory" to skip it. Worktrees are most useful when running multiple PRDs simultaneously.
How do I merge a completed branch?
Press n to open the PRD picker, select the completed PRD, and press m to merge. If there are conflicts, Chief shows the conflicting files and instructions for manual resolution.
How do I clean up a worktree?
Press n to open the PRD picker, select the PRD, and press c. You can choose to remove just the worktree or remove the worktree and delete the branch.
What happens if Chief crashes mid-worktree?
Chief detects orphaned worktrees on startup and marks them in the picker. You can clean them up with c. Your work on the branch is preserved — git worktrees are just directories with a separate checkout.
Can I automatically push and create PRs?
Yes. During first-time setup, Chief asks if you want to enable auto-push and auto-PR creation. You can also toggle these in the Settings TUI (,). Auto-PR requires the gh CLI to be installed and authenticated.
Technical
Why stream-json?
The agent outputs JSON in a streaming format. Chief uses stream-json to parse this in real-time, allowing it to:
- Display progress as it happens
- React to completion signals immediately
- Handle large outputs efficiently
Why conventional commits?
Conventional commits (feat:, fix:, etc.) provide:
- Clear history of what each story added
- Easy to review changes per-story
- Works with changelog generators
What if the agent makes a mistake?
Git is your safety net. Each story is committed separately, so you can:
# See what changed
git log --oneline
# Revert a story
git revert HEAD
# Or reset and re-run
git reset --hard HEAD~1
chief # then press 's' to startDoes Chief work with any language?
Yes. Chief doesn't know or care what language you're using. It passes your PRD to the agent, which handles the implementation.
How does Chief handle tests?
Chief instructs the agent to run quality checks (tests, lint, typecheck) before committing. The agent infers the appropriate commands from your codebase (e.g., npm test, pytest).
Troubleshooting
See Common Issues
For specific problems and solutions.
Getting Help
Where can I report bugs?
Is there a community chat?
Use GitHub Discussions for questions and community support.
Can I contribute?
Yes! See CONTRIBUTING.md in the repository.