Skip to content

Configuration

Chief is designed to work with zero configuration. All state lives in .chief/ and settings are passed via CLI flags.

CLI Flags

FlagDescriptionDefault
--max-iterations <n>, -nLoop iteration limit10
--no-soundDisable completion soundfalse
--verboseShow raw Claude output in logfalse
--mergeAuto-merge progress on conversion conflictsfalse
--forceAuto-overwrite on conversion conflictsfalse

Claude Code Configuration

Chief invokes Claude Code under the hood. Claude Code has its own configuration:

bash
# Authentication
claude login

# Model selection (if you have access)
claude config set model claude-3-opus-20240229

See Claude Code documentation for details.

Permission Handling

By default, Claude Code asks for permission before executing bash commands, writing files, and making network requests. Chief automatically disables these prompts when invoking Claude to enable autonomous operation.

WARNING

Chief runs Claude with full permissions to modify your codebase. Only run Chief on PRDs you trust.

For additional isolation, consider using Claude Code's sandbox mode or running Chief in a Docker container.

No Global Config

Intentionally, Chief has no global configuration file. This ensures:

  1. Portability: Project works the same on any machine
  2. Reproducibility: No hidden state affecting behavior
  3. Simplicity: One place to look for all settings