Getting started

Install cadrei, run it in a repo, and press Enter. Your orchestrator opens in tmux and says hi.

Install

With Homebrew

brew install rafi-ramdhani/cadrei/cadrei
cadrei

No Homebrew? Use the install script instead:

With the install script

curl -fsSL --proto '=https' https://raw.githubusercontent.com/rafi-ramdhani/cadrei/main/install.sh | sh

You’ll need

macOS or Linux, Claude Code, git, and tmux 3.2 or newer. Homebrew installs tmux for you. If Claude Code isn’t logged in yet, it asks you when it opens.

Your first run

Run cadrei inside a repo you want your team to work on, like ~/code/my-app. It checks your tools, shows the whole plan on one screen, and waits for one key. Here’s that screen, in full:

  cadrei v0.2.1
  A team of Claude Code helpers you lead from one chat.
  ~/code/my-app

  ✓ Claude Code 2.1.300 (logged in), git and tmux are ready

  Here's the plan
  · Create your crew main in ~/.cadrei/main, with an engineer and a reviewer
  · Add my-app as your first project
  · Trust both in Claude Code
    Your team works there without Claude Code asking first.
  · Link cadrei's instructions into Claude Code (~/.claude/skills/cadrei)
  · Open your orchestrator in tmux (recommended)
    It keeps going if you close this window. Ctrl-b s switch, Ctrl-b d leave

  Press Enter to set this up.
  Or press p for the plain terminal, r to restore from GitHub, q to quit.

Key	What it does
Enter	Sets up the whole plan.
p	The same plan, but your orchestrator opens in this terminal instead of tmux.
r	Restores a crew you backed up to GitHub.
q	Quits and changes nothing.

Your first run has every key and what each step does.

Getting around in tmux

Your orchestrator and every member run in tmux, so they keep going when you close the window. Two keys are all you need, and they stay in the status bar at the bottom.

• Ctrl-b then s lists your orchestrator and every team. Pick one, then Enter.
• Ctrl-b then d leaves. Everything keeps running. Run cadrei to come back.

Here’s what Ctrl-b then s shows, with pane titles left out. Each team is a session, and each member is a window in it. The * marks each session’s current window:

(0) + cadrei-main: 1 windows (attached)
(1) - cadrei-main-dev-my-app: 2 windows
(2) ├─→ + 0: engineer*
(3) └─→ + 1: reviewer

tmux only knows the windows. To see what each member is doing, and who’s waiting on you, run cadrei ls. Here’s part of what it shows:

Teams
  dev on my-app                                    cadrei attach dev my-app
    ● engineer   working for 4m
    ! reviewer   waiting on you · approve it in its window

Never used tmux? New to tmux? covers the rest in two minutes.

Just ask

Everything after cadrei is a chat with your orchestrator. Try:

• “add a designer to the dev team”
• “allow the members to run npm test”
• “back up my crew to GitHub”

Want to know what happens underneath? Start with Concepts.