Uninstalling

cadrei uninstall --dry-run prints the plan. cadrei uninstall prints it, asks, then:

stops every team member, and your orchestrator in tmux last;
removes cadrei’s instructions link and the every-chat hook, only where they point at this program (other hooks and settings stay; the backup made before cadrei first changed the settings file, settings.json.bak-cadrei, is kept, and no new one is written);
removes each crew’s pre-push hook;
removes ~/.cadrei/config and ~/.cadrei/framework.

It keeps every crew and project, trust entries and backups, and ends like this:

✓ Uninstalled. Your crews and projects are still here.
  Your crews in ~/.cadrei are your setup, so keep them. Reinstall and run
  cadrei to plug them back in.
  To finish: brew uninstall cadrei

For an install.sh install, the last line is the rm that removes the program. Since each crew keeps its own notes, a reinstall and cadrei plug your crews back in, with their projects and chats as they were. An orchestrator open in a terminal is named so you can close it. Members can’t run it.

With Homebrew, run cadrei uninstall before brew uninstall cadrei: Homebrew can’t run cadrei’s cleanup for you. If you forgot, the leftover hooks do nothing, and reinstalling puts them right.

Archive everything

cadrei uninstall --archive does what cadrei uninstall does, and also moves every crew and ~/.cadrei/config into one new folder, ~/.cadrei-archive/<date-time>/. Nothing is deleted. Afterwards ~/.cadrei is gone, so a reinstall and cadrei is exactly a brand-new user’s first run. Use it to try cadrei fresh, or to start over and keep your old setup.

cadrei uninstall --archive --dry-run shows the plan first, with how each crew’s GitHub backup stands:

cadrei uninstall --archive will:
  · stop 3 team members: main-dev-my-app-engineer, main-dev-my-app-reviewer,
    main-research-scout
  · stop your orchestrator in tmux
  · remove cadrei's instructions link (~/.claude/skills/cadrei)
  · remove the every-chat hook from ~/.claude/settings.json (your other hooks
    stay)
  · remove cadrei's pre-push check from main, work and life
  · move your crews (main, work, life) and this machine's cadrei settings
    into ~/.cadrei-archive/2026-10-10-1432
  · remove ~/.cadrei/framework, then ~/.cadrei

Backups
  ✓ main is backed up to github.com/you/cadrei-main, and up to date
  ! work has 2 commits that aren't on github.com/you/cadrei-work yet
  ! life has no backup. After this, it's only in the archive.

It keeps your projects, Claude Code's trusted-folder marks, your Claude Code
chats, and your own Claude Code settings.

Bring it all back later with cadrei restore, or press o on cadrei's first run.

Without --dry-run, it offers to commit and push each crew whose backup is behind, then asks Archive and uninstall? [y/N]. A push that fails doesn’t stop it: the crew is still safe in the archive.
--yes skips the question and pushes nothing.
Run it in a terminal, not from your orchestrator, and close an orchestrator that’s open in a terminal first: it moves your orchestrator’s own folder.
A crew outside ~/.cadrei (one you reach only through CADREI_HOME) stays where it is.
If it stops halfway, run the same command again to finish.
Each archive has a README.txt that says what it is and how to bring it back. Members can’t read or change the archive.

Bring back an archived setup

Run cadrei restore, or press o on the first run (it shows up whenever an archive is waiting). With several archives, cadrei restore lists them and you pick one by number; cadrei restore <folder> takes an archive folder directly. Then:

  Bring back your setup from Oct 10, 14:32

  Here's the plan
  · Put main, work and life back in ~/.cadrei, with main as your default
  · Bring back this machine's cadrei settings: where your projects are,
    your tmux choice and the rest
  · Link cadrei's instructions into Claude Code (~/.claude/skills/cadrei)
  · Turn the every-chat hook back on (it was on before)
  · Open your orchestrator in tmux, as before

  Press Enter to bring it back, or q to quit.

Everything goes back to the same paths, so your orchestrator picks up its last chat, and members pick up theirs on their next start. A restore writes no trust marks: your projects keep the ones they had, and Claude Code still knows your crews’ folders from before.

A restore needs an empty ~/.cadrei. If you have a crew set up here (say, the one you made while trying a new version), it stops: Archive it first, so nothing is lost: cadrei uninstall --archive. Then run cadrei restore and pick the setup you want back. The trial gets its own archive, which you can bring back the same way.
An archive that was already brought back isn’t offered again.
From another home folder, projects show as not on this machine until you link or clone them. For a second computer, a GitHub backup (r) is the better way.
Once you’re sure you don’t want an archive, delete its folder. Claude Code doesn’t need anything in it.