Where things live

~/.cadrei/
  <name>/                     a crew (a git repository)
    playbook.md               teams, pipelines, routing rules and your preferences
    projects.yaml             each project's repo, team and about (no local paths)
    cadrei.conf               settings (KEY=VALUE lines)
    protocol.md               optional house rules for every member
    members/<team>/<role>.md  one member per file
    teams/<team>/             working folders of teams without a project (tracked)
    .claude/
      member-settings.json    the grants every member starts with (tracked)
      member-settings.once    which grants are one-time (tracked)
      local/                  this machine's notes about the crew (ignored)
        places.json           where each project is on this machine
        state.json            your orchestrator's chat record
        cadrei.conf           optional: settings for this machine only
      build/                  generated: prompts, settings copies, chat records, member states, locks (ignored)
  config/                     this machine only, in no repository
    default                   the default crew's name
    projects-dir              where new clones go
    member-settings.sha256    fingerprints of the grants files
    state.json                the health check's notes and your one-time answers
    team-line-hint            there once the team line's one-time hint was shown
  framework/                  cadrei's instructions and prompts, written out by the program, with a VERSION file
~/.cadrei-archive/            setups you packed away with cadrei uninstall --archive

config and framework are reserved names; a crew’s name may use letters, digits, - and _.

Everything in ~/.cadrei/config can be rebuilt or asked again, so deleting it loses nothing: the next cadrei plugs your crews back in.

Everything cadrei puts on your machine

Here’s the full list, and what cadrei uninstall does with each. If you’ve set CLAUDE_CONFIG_DIR, read that folder wherever this says ~/.claude (it holds .claude.json too, then).

What	Where	Added when	`cadrei uninstall`
The `cadrei` program	Homebrew’s `bin`, or `~/.local/bin/cadrei`	you install it	Kept: it prints the command that removes it
Your crews: members, playbook, projects list, `cadrei.conf`, permissions and `teams/`	`~/.cadrei/<name>/`, each one a git repo	the first run, `cadrei new`, or when you ask your orchestrator	Kept
This machine’s notes about a crew: where its projects are, and its chat record	`~/.cadrei/<name>/.claude/local/`, left out of git	every crew	Kept, with the crew
Files made for each start: prompts, settings copies, chat records, member states, locks	`~/.cadrei/<name>/.claude/build/`, left out of git	every start	Kept, with the crew
A check that stops passwords, keys and files over 50 MB from going into your backup (a git pre-push hook)	`~/.cadrei/<name>/.git/hooks/pre-push`	the first run, and put back by every `cadrei`	Removed
This machine’s settings: the default crew, the projects folder, the permissions fingerprint, the health check’s notes, your one-time answers	`~/.cadrei/config/`	`cadrei`	Removed
cadrei’s instructions for Claude Code and its prompts	`~/.cadrei/framework/`, rewritten when they don’t match the program	every `cadrei`	Removed
A link so Claude Code can find those instructions	`~/.claude/skills/cadrei`, pointing at `~/.cadrei/framework/skills/cadrei`	the first run	Removed, if it points at this program
Optional: the every-chat hook, so every new Claude Code chat starts as your orchestrator (a SessionStart hook)	one entry in `~/.claude/settings.json`	your yes when your orchestrator offers it, or `cadrei hook on`	Removed, if it runs this program (your other hooks stay)
“Trusted folder” marks for your projects and new crews	entries in `~/.claude.json`	adding, linking or downloading a project; the first run and `cadrei new`, for the new crew’s folder	Kept: your own Claude Code uses them too
Your projects	wherever you keep them; new downloads go in your projects folder	you, or your orchestrator	Kept
Members’ chats	Claude Code’s own folder	Claude Code	Kept
Archives of your setup	`~/.cadrei-archive/<date-time>/`	`cadrei uninstall --archive`	Kept: yours to delete

Your crews live in ~/.cadrei/<name>. They’re your setup, so don’t delete them to reset cadrei. To reset the program, run cadrei uninstall (or delete ~/.cadrei/config and ~/.cadrei/framework): your crews stay, and the next cadrei plugs them back in. To try cadrei as a brand-new user, run cadrei uninstall --archive, which packs your crews away safely.

Want a plain Claude Code chat while the every-chat hook is on? Start it with CADREI_OFF=1 claude. The every-chat hook has the rest.

Before cadrei first changes ~/.claude/settings.json or ~/.claude.json, it saves a copy next to it (settings.json.bak-cadrei, .claude.json.bak-cadrei) and never overwrites that copy.

The backup check, the every-chat hook, the team status line and the hooks in each member’s settings only run the cadrei program when it sits in a folder only you can write to, which is where Homebrew and install.sh put it. Run it from a temporary folder and it sets none of them up; the health check tells you so.

Every hook command cadrei writes checks that the program is still there first (test -x <program> && <program> hook ... 2>/dev/null; exit 0). So if the program is gone, for example after brew uninstall cadrei without cadrei uninstall, a leftover hook does nothing and shows nothing.