Troubleshooting

• A member never replies. Run cadrei ls. ! waiting on you means it needs your approval in its window: cadrei attach <team> [project] (or Ctrl-b then s in tmux). ✗ stopped by safeguards means Claude’s safeguards stopped its reply: open its window, type /model and pick the model again, or ask your orchestrator to restart it fresh. Otherwise look at its window; a new folder may show Claude Code’s trust prompt, and cadrei project trust <name> avoids it next time.
• The trust prompt still shows for a project. Run cadrei project trust <name>. A Claude Code session running during the change may have written its own copy of ~/.claude.json over it; accept the prompt once, or run the command again with no sessions running. If you set CLAUDE_CONFIG_DIR, members use the value the tmux server started with.
• Claude Code asks to trust your crew’s folder. Claude Code hadn’t run on this machine before your first run, or the crew was restored. If it’s your crew, say yes.
• A member reports a blocked action. Decide whether to allow it. If yes, tell your orchestrator to allow that exact action; it restarts the member when needed.
• Messages wait for approval. The member runs in a different permission-mode class from your orchestrator. Set PERMISSION_MODE in cadrei.conf to the mode you want for both.
• “Your orchestrator is already open in another terminal”. Switch to that one, or close it first. Or move it to tmux with cadrei tmux on, so cadrei always takes you back to it.
• You left tmux and want back in. Run cadrei.
• A project shows as missing. Ask your orchestrator to clone it again or point to its new folder, or run cadrei project sync or cadrei project link <name> <dir>.
• After switching Claude accounts. Run cadrei stop, close your orchestrator, and run cadrei again. Chats resume.
• You want to start over. Don’t delete ~/.cadrei/<name>. Run cadrei uninstall to reset the program and keep your crews, or cadrei uninstall --archive to start like a new user and keep everything in an archive.