One Claude
Code chat.
A crew in
tmux.

Your Claude Code chat hands out the work, and every member gets its own tmux window. You just say what you need.

brew install rafi-ramdhani/cadrei/cadrei

Then run cadrei in a repo. macOS or Linux, with Claude Code, git and tmux.

New here? Read Getting started
The orchestrator, the crew's lead, smiling in its headset

See it in motion.

A 45-second animated tour of the first run: one command, a hello, and a crew getting to work in tmux.

One command.~/code/my-app~/code/my-app $ cadreiIt checks your tools,then shows the whole plan.~/code/my-app$ cadreicadrei v0.2.1A team of Claude Code helpers you lead from one chat.~/code/my-appClaude Code 2.1.300 (logged in), git and tmux are readyHere'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 leavePress Enter to set this up.Or press p for the plain terminal, r to restore from GitHub, q to quit.Press Enter.That's the setup.~/code/my-appPress Enter to set this up.Created your crew mainAdded my-app as a projectTrusted both in Claude CodeLinked cadrei's instructions into Claude CodeOpening your orchestrator in tmux.Your orchestrator says hi.cadrei-mainHi! I'm the orchestrator for your crew main. You tell me what you need, and I hand the work to your team. Right now that's an engineer and a reviewer, set up for my-app.Three ways to start: 1. I'll have the reviewer read my-app and tell you the top 3 things to fix. Read-only, nothing changes. 2. I'll have the engineer add a small feature to my-app on a branch, and the reviewer check it. 3. I'll set up another team for you, like research, study or job search.Type a number, or just tell me what you need.New to tmux? Ask me how to get around.mainorchestratorCtrl-b s switch · Ctrl-b d leaveMeet your crew.cadrei-mainwhat's running?Bash(cadrei ls) main ~/.cadrei/main Orchestrator open in tmux since 14:02 · reopen with cadrei Teams Nothing running. Ask your orchestrator to start a team. Projects my-app ~/code/my-appNobody's working yet. Your dev team has an engineer and a reviewer, set up for my-app. Tell me what you need.mainorchestratorCtrl-b s switch · Ctrl-b d leaveJust say what you need.cadrei-mainNobody's working yet. Your dev team has an engineer and a reviewer, set up for my-app. Tell me what you need.Add a dark mode toggle to my-appmainorchestratorCtrl-b s switch · Ctrl-b d leaveA team starts,in its own tmux windows.cadrei-main-dev-my-appAdd a dark mode toggle to my-app, on a new branch. Tell the reviewer when it's ready.Reading the routes… (3s)maindev on my-appengineerreviewerC-b s · C-b dcadrei-mainAdd a dark mode toggle to my-appOn it. I started the dev team on my-app: the engineer builds it on a branch, and the reviewer checks it when it's ready.Team: engineer working just now · reviewer idle(Say "hide the team line" if you'd rather not see this.)mainorchestratorCtrl-b s switch · Ctrl-b d leaveEach member worksin its own window.dev on my-app: engineerAdd a dark mode toggle to my-app, on a new branch. Tell the reviewer when it's ready.Bash(git switch -c dark-mode) Switched to a new branch 'dark-mode'Read(src/app.tsx) Read 84 linesWrite(src/theme.ts) Wrote 42 lines to src/theme.tsBuilding… (2m 4s)maindev on my-appengineerreviewerC-b s · C-b ddev on my-app: reviewerReview the dark-mode branch when the engineer says it's ready.I'll wait for the engineer's note, then review the branch.maindev on my-appengineerreviewerC-b s · C-b dPeek anytime:Ctrl-b sThe reviewer checksthe work.dev on my-app: reviewerReview the dark-mode branch when the engineer says it's ready.Bash(git diff main...dark-mode --stat) 4 files changed, 96 insertions(+), 3 deletions(-)One small fix: the toggle forgets your choice after a reload. I sent it to the engineer.Fixed, and checked again. Approved.maindev on my-appengineerreviewerCtrl-b s switch · Ctrl-b d leaveOne answer comesback to you.cadrei-mainAdd a dark mode toggle to my-appDone! The engineer added a dark mode toggle on the branch dark-mode, and the reviewer approved it after one small fix (it now remembers your choice). Want me to open a pull request?Team: engineer idle · reviewer idlemainorchestratorCtrl-b s switch · Ctrl-b d leaveCadrei lockupA team of Claude Code helpersyou lead from one chat.$ brew install rafi-ramdhani/cadrei/cadreicadrei.devmainorchestratorengineerreviewerCtrl-b s switch · Ctrl-b d leaveOne command.~/code/my-app~/code/my-app $ cadreiIt checks your tools, thenshows the whole plan.~/code/my-appcadrei v0.2.1A team of Claude Code helpers you lead from onechat.~/code/my-appClaude Code 2.1.300 (logged in), git and tmux are readyHere'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 leavePress Enter to set this up.Or press p for the plain terminal, r to restore from GitHub, q to quit.Press Enter. That's thesetup.~/code/my-appPress Enter to set this up.Created your crew mainAdded my-app as a projectTrusted both in Claude CodeLinked cadrei's instructions into Claude CodeOpening your orchestrator in tmux.Your orchestrator says hi.cadrei-mainHi! I'm the orchestrator for your crew main. You tell me what you need, and I hand the work to your team. Right now that's an engineer and a reviewer, set up for my-app.Three ways to start: 1. I'll have the reviewer read my-app and tell you the top 3 things to fix. Read-only, nothing changes. 2. I'll have the engineer add a small feature to my-app on a branch, and the reviewer check it. 3. I'll set up another team for you, like research, study or job search.Type a number, or just tell me what you need.New to tmux? Ask me how to get around.mainorchestratorC-b s · C-b dMeet your crew.cadrei-mainwhat's running?Bash(cadrei ls) main ~/.cadrei/main Orchestrator open in tmux since 14:02 · reopen with cadrei Teams Nothing running. Ask your orchestrator to start a team. Projects my-app ~/code/my-appNobody's working yet. Your dev team has an engineer and a reviewer, set up for my-app. Tell me what you need.mainorchestratorC-b s · C-b dJust say what you need.cadrei-mainNobody's working yet. Your dev team has an engineer and a reviewer, set up for my-app. Tell me what you need.Add a dark mode toggle to my-appmainorchestratorC-b s · C-b dA team starts, in its owntmux windows.cadrei-main-dev-my-appAdd a dark mode toggle to my-app, on a new branch. Tell the reviewer when it's ready.Reading the routes… (3s)maindev on my-appengineerreviewerC-b s · C-b dcadrei-mainAdd a dark mode toggle to my-appOn it. I started the dev team on my-app: the engineer builds it on a branch, and the reviewer checks it when it's ready.Team: engineer working just now · reviewer idle(Say "hide the team line" if you'd rather not see this.)mainorchestratorC-b s · C-b dEach member works in its ownwindow.dev on my-app: engineerAdd a dark mode toggle to my-app, on a new branch. Tell the reviewer when it's ready.Bash(git switch -c dark-mode) Switched to a new branch 'dark-mode'Read(src/app.tsx) Read 84 linesWrite(src/theme.ts) Wrote 42 lines to src/theme.tsBuilding… (2m 4s)maindev on my-appengineerreviewerC-b s · C-b ddev on my-app: reviewerReview the dark-mode branch when the engineer says it's ready.I'll wait for the engineer's note, then review the branch.maindev on my-appengineerreviewerC-b s · C-b dPeek anytime:Ctrl-b sThe reviewer checks thework.dev on my-app: reviewerReview the dark-mode branch when the engineer says it's ready.Bash(git diff main...dark-mode --stat) 4 files changed, 96 insertions(+), 3 deletions(-)One small fix: the toggle forgets your choice after a reload. I sent it to the engineer.Fixed, and checked again. Approved.maindev on my-appengineerreviewerC-b s · C-b dOne answer comes back toyou.cadrei-mainAdd a dark mode toggle to my-appDone! The engineer added a dark mode toggle on the branch dark-mode, and the reviewer approved it after one small fix (it now remembers your choice). Want me to open a pull request?Team: engineer idle · reviewer idlemainorchestratorC-b s · C-b dCadrei lockupA team of Claude Code helpersyou lead from one chat.$ brew install rafi-ramdhani/cadrei/cadreicadrei.devmainorchestratorengineerreviewerCtrl-b s switch · Ctrl-b d leave

4 of 11Your orchestrator says hi.

Transcript

Every shot's caption and what happens in it, as text.

  1. One command.An empty terminal in ~/code/my-app. cadrei types itself while the lead waits in the corner.
  2. It checks your tools, then shows the whole plan.The real first-run screen: the check line, then the plan, one line at a time.
  3. Press Enter. That's the setup.Enter is pressed and four check lines tick in.
  4. Your orchestrator says hi.Cut to tmux, with the crew on its clay block in the green status bar. The greeting types out three ways to start: “I'll have the reviewer read my-app and tell you the top 3 things to fix.”, “I'll have the engineer add a small feature to my-app on a branch, and the reviewer check it.” and “I'll set up another team for you, like research, study or job search.” It ends with “New to tmux? Ask me how to get around.”, and the lead says hi.
  5. Meet your crew.You ask what's running. The dev team shows as idle, and the engineer and the reviewer hop in.
  6. Just say what you need.You type one line to the orchestrator: add a dark mode toggle to my-app.
  7. A team starts, in its own tmux windows.The orchestrator replies with the team line, and the dev team's session slides in with the engineer's window current.
  8. Each member works in its own window.The engineer ticks through its steps while the reviewer waits. Peek anytime with Ctrl-b s.
  9. The reviewer checks the work.The reviewer reads the diff, asks for one small fix, then approves.
  10. One answer comes back to you.Back in the orchestrator: one plain answer and an offer to open a pull request. Both members are idle again.
  11. cadrei.devThe end card: the logo, the tagline, the install command and the crew on a status bar.

Ready? Install it with one line, then follow the guide. Getting started

You ask once. The crew splits it up.

Each member is its own Claude Code with one job, and the orchestrator only wakes the ones a task needs.

  1. The lead hears: ship the new login page.

    1You ask the lead

    Say what you want in one chat.

  2. The lead starts the engineer, the reviewer and the writer, each in its own window.

    2The lead splits it

    Each member gets its own tmux window and a clear task.

  3. The lead cheers next to a checklist: login page, reviewed, release notes.

    3You get one answer

    The lead checks the work and reports back to you.

Your crew, the way tmux sees it.

Crew

Your folder, ~/.cadrei/main, kept in git. Back it up, take it to a new machine.

Team

One tmux session. Open it with cadrei attach dev my-app.

Member

One window, one Claude Code. cadrei ls shows who's busy and who's waiting on you.

Any team you can describe.

A member is a short Markdown file, so a team can be anything you can write down.

A dev team on your repo

dev · 3 members
“Add a settings page to my-app.”

The PM plans it, the engineer builds it on a branch, the designer checks the screens.

A tutor that remembers

study · 1 member
“Quiz me on what I got wrong last week.”

One tutor per subject, keeping tabs on your progress and your mistakes.

The review loop

dev · 2 members
“Fix the login bug, and have it reviewed.”

The engineer fixes, the reviewer checks, back and forth until it passes.

You're the boss.

Only your words count as consent.

Members ask you before anything risky. A message from your orchestrator never counts as your yes.

Permissions go through cadrei allow.

Grant narrow rules, like npm test, one folder or one MCP tool, or a sentence for auto mode. Wildcards come with a warning, catch-all rules are refused, and every change is committed.

Everything stays on your machine.

Your crew is a folder in git. Cadrei has no server and no account of its own. Back it up to GitHub only if you want to.

Easy to leave, easy to come back.

cadrei uninstall asks first and keeps your crews. Reinstall, and they plug right back in.

Questions?

Do I need to know tmux?

Nope. Two keys get you around, and they're printed right in the status bar: Ctrl-b then s to switch, Ctrl-b then d to leave. Still not into it? Press p on the first run, and your orchestrator opens in your plain terminal.

Does it use more of my Claude limits?

Yes, honestly. Each member is its own Claude Code, so three members use about three times as much of your plan as one. Your orchestrator only wakes the members a task needs.

How is this different from subagents?

Subagents live inside one chat and vanish with it. Members stick around: open one, chat with it, and it's still on the job tomorrow.

What do I need?

A Mac or a Linux box, Claude Code, git, and tmux 3.2 or newer. Homebrew brings tmux along for you.

How do I remove it?

cadrei uninstall shows what it'll remove and asks first. Your crews stay put, so if you come back, they plug right back in. No hard feelings.