Set up

Set up is the half of crew's page where crew is configured: projects, workspaces, worktrees, machines and crew's own settings. Every form runs a crew command, so nothing here is out of reach of the terminal (or of an agent). The other half is Voice OS, where you talk to the sessions.

The examples use a store: store-front (the web app), store-api, checkout-api and signals. Use your own repos.

Contents

Opening it

crew

Bare crew starts crew's server if it is not running and opens the page in your browser. With no terminal, over SSH or with --no-open, it prints the link instead. The page opens on Home:

Home: Voice OS (3 active, 1 waiting on you) and Set up (2 projects on This Mac) side by side, and "Always open Voice OS" under them

Pick Set up. Each card says what is waiting there ("2 things need you" is the board's problems strip). Enter opens the highlighted one. Ticking Always open Voice OS skips Home when you open the page fresh, once there is a worktree to talk to (the very first time, Home is the first run); the crew mark at the top left always brings you back to it, and Voice OS's settings turn it off.

Set up shows one machine at a time. The bar along the top has the crew mark, the machine picker (This Mac, and any other machines — one with something broken shows it when you open the menu) and the breadcrumbs of where you are. Esc goes up one breadcrumb.

The board

The board is the machine's front page: what it has, and what needs you.

The board on This Mac on its Projects tab: Setup with Claude, then store-front with web :5173 and store-api with api :8000 and worker, both in store

From the top:

Workspaces lists each workspace with its projects and its worktrees as chips: green when ready, red with what failed, "+N" for the rest, and + new to make another. New workspace opens the form. With no workspace yet, the tab offers the three ways to start instead: New workspace, Import (from another machine's export) and Ask Claude.

The Workspaces tab: the store workspace with store-front and store-api, its worktrees main and wrk1 as chips, and + new

Projects lists every project on the machine, one line each: its install, its dev servers with their ports, the workspaces it is in, and its state — Check (never checked), check failed, or ready. A long cell ends in "…" and shows the whole of it on hover; a list says its first entries and how many more ("web :3000 · api :4000 +2", "store-front +1"). A click anywhere on a row opens the project; its own buttons do only their own thing. Add project clones a git URL into crew's own folder; Use a folder on this Mac is there for a repo with no remote, and crew's worktrees then branch from your checkout.

A project with no dev servers (a library, infra) is a whole project: nothing flags it, and its sessions read, change and test its code like any other.

A project

Click a project for its page: what crew recorded, one line per fact — its install and env command, each dev server, each Environment variable, the workspaces it is in, where its code comes from and where it is. A long value ends in "…" with the whole of it on hover.

store-api's page, not checked yet, with Edit setup, Ask Claude and Check; under it what crew recorded, one line per fact: the env command, the api and worker dev servers, CORS_ORIGIN from store-front's URL, the store workspace, its remote and its path

When its last check failed, the page opens on that: the step it stopped at (checkout, install or servers), the end of the log, and what it means ("its worktrees keep their code, and the project stays as it was set up"). Fix with Claude, Edit setup, Check again and Full log sit under it.

Remove project at the bottom takes it out of crew. It asks first, and says what goes with it: a clone crew made goes to crew's trash, a folder you added is never touched.

Edit setup

Edit setup opens the project's form:

The form for store-front: the install detected from the lockfile, no env command, one dev server web running npm run dev on port 5173, and VITE_API_URL from store-api's URL in its Environment

Save records it. Stuck? Ask Claude sends the form's project to Setup with Claude, which picks up from there. In the terminal, the Environment is crew add binding.

Checking a project

Check (on the board) or Check again (on the page) proves the project works from nothing: a clean checkout, the install, then every dev server has to answer. The check page follows it step by step while it runs. A pass is a green line on the project; a failure stays on the project page with its evidence until you fix it and check again. It touches nothing you work in — the check has its own scratch checkout, cleared once it passes. Terminal: crew check project store-api --wait.

Workspaces

A workspace is the projects you work on together. Each worktree gets a copy of every one, wired to each other.

New workspace asks for a name and the projects. Each project is in a worktree of its own (worktree, the default) or direct — its one checkout, shared, for a project you never branch. One that can't be direct (it is already direct in another workspace, or has worktrees) says why when you save. How they connect lists which Environment lines between the ticked projects resolve. Creating it also makes its first worktree, main, with every server tried.

A workspace's page is its worktrees, one card each: its state, its size on disk and its dev servers as chips (red for one that died), with Start and Open in Voice OS. The gear beside the name opens the workspace's settings: its projects, where you add or take one out (every worktree gets the change), and Remove workspace. Taking a project out, or removing the workspace, opens a confirm that says, per checkout, what would go — uncommitted files, commits that are not on the base branch and the space on disk — before anything is removed.

Worktrees

A worktree's page is one working copy of the workspace:

store/wrk1: rename and duplicate beside its name, Open in Voice OS; the Dev servers card stopped, with Start and Verify over web, api and worker; the Environment card for values set for this worktree

Rename moves its checkouts and renames crew's branches; it is refused while its servers run or setup is busy with it. Duplicate makes fresh checkouts of the same projects on new ports, with the values set for this worktree copied across. Remove worktree shows what would go first, like a workspace; removing a workspace's last worktree removes the workspace too.

A new worktree

+ new on a workspace, or New worktree on its page:

New worktree in store: a name, the branch it makes, and the base branch of each project (store-front 3 behind main, store-api up to date) with "pull first" ticked

Start from shows each project's base branch and how far it is behind origin. Pull first fast-forwards the bases before branching (it never touches a branch you have checked out). Each project gets a crew/store-front/<name>/<project> branch.

Create worktree takes you to the new worktree's page, where its Dev servers card follows crew's runners: each project with the step it is on (checkout, install, servers tried), then its servers as they answer. A project that fails stops there with its output and Fix with Claude; the others keep what they have.

Setup with Claude

Each machine has its own Claude for setting up: a Claude Code session in your home folder with the crew CLI, always on, one conversation.

Setup with Claude adding store-front and store-api: each crew command it ran, a green "recorded" line under the ones that recorded something, and its answer that store/main is set up

Ask it anything you would do in the forms, or what you don't know how to do: "add the signals repo to crew and give it a worktree", "why does store-api's install fail?", "check this machine". It reads the repo, works out the install and the dev servers, asks only what it can't know, and records it with crew commands. Each crew command that recorded something gets a ✓ recorded line, taken from the command it ran — not from what Claude says about it.

It is drawn with the same pieces as a session in Voice OS: its steps, the reply as it arrives (with a caret), a bar while it compacts its context, and the sub-agents it has running. What it waits on is docked at the foot of the card, right above where you type, as Voice OS docks it above the voice bar: a question with its options as rows, Something else… for your own answer and ✕ to decline it; a plan to approve or change; a permission as Allow / Always allow … / Deny (or Deny and say why…); a /clear or /compact to confirm. Words you send while it works wait in the queue under the ask — ▲ now sends one at once, ✕ cancel drops it — and go in order when the turn ends; Stop stops the turn. Fix with Claude and Ask Claude anywhere in Set up start here, with the failure or the form already said.

While Claude works on a worktree, that worktree shows beside the chat: its Dev servers card, live, so you see servers stop, restart and answer as Claude changes things, and their logs a click away. It picks the worktree up from the crew commands Claude runs and the messages you send, and moves when Claude moves to another one; Fix with Claude from a worktree opens it at once. × closes it until the next worktree is named.

Type @ in the box for this machine's worktrees and projects: pick one and its name goes into your message, spelled as crew spells it.

It is not part of voice: what you type goes straight to the setup session, never through Voice OS's kernel; Voice OS never routes your words to it, speaks for it or shows its questions, and no button here has a word to say. On another machine, its chat is that machine's setup session, and its questions are answered the same way.

Machines

The machine picker's Add a machine… sets one up: install crew on that computer or VM (crew server remote there checks it is ready); then give its SSH address (what ssh <host> logs into with no password) and a Name, and press Connect without Claude, or Connect with Claude to have Setup with Claude do it. A remote machine has the whole path.

A machine's page says how it is reached, which crew it runs and what is on it — each project with its state and worktree count. Check with Claude asks that machine's Claude to look at the connection, tools, disk and projects; Rename and Remove machine are there too. Everything else in Set up — the board, the forms, Setup with Claude — works on another machine the same way as on this one: pick it in the picker. A machine that runs an older crew says so in place; crew updates it from here.

This Mac's machine page: crew 6.10.0 runs here, Check with Claude, and store-front and store-api with 2 worktrees each

Settings

Settings on This Mac: crew v6.10.0 up to date; This machine with Server IP 192.168.1.20, SSH host dev-mac, an empty Proxy domain, HTTP port 80 and HTTPS 443, proxy answering, Save and Trust on other devices; Disk with Trash (3 removed checkouts, 2.1 GB) and Empty now, Left behind and Clean up; Move to another machine with Export… and Import…; crew's log

Moving to another machine

Export… (Settings) is its own page: tick workspaces and the projects in them come along; projects in no workspace are ticked on their own. A project with no git remote goes as setup only, and the other machine points it at a folder. The page says what goes with the file (projects by remote, their install and env commands, dev servers, bindings, workspace membership) and what stays (worktrees, ports, worktree values, .env files), and Save crew-export.json downloads it.

Export: the store workspace ticked with store-front and store-api under it, each going by its remote, what goes with the file and what stays on This Mac, and Save crew-export.json

Import… on the other machine takes the file (drop it, or choose it) and shows crew's plan with every choice up front:

Import's first step: drop crew-export.json here, or Choose a file, with the File, Choose and Getting it ready steps above

Import stays off until every choice is made (Skip counts), then runs everything at once: the projects, then each workspace, with its install shown the way the first run shows it. A replace asks first. It ends on Open Voice OS (the first workspace's session) or Go to the board. Terminal: crew import <file> prints the same plan (found is a checkout you already have), and crew import <file> project <name> --path=<dir> uses it instead of a clone.

First run

The first time crew's page opens on a machine, Home is the first run: the crew wordmark and three ways in.

The first run shows once. Whichever way you pick, Home is the launcher from then on, even if you later remove every workspace. A machine that already had worktrees when crew got this never sees it.

The first run's projects step: store-front and store-api found as git checkouts on this Mac, both ticked, each cloned from its remote

  1. Pick your projects. crew lists the git checkouts in your usual code folders (~/code, ~/projects, ~/dev, ~/src, ~/Developer, ~/work, ~/repos). Tick the ones you work on: each is cloned fresh from its remote into crew's own folder, and yours is never touched (one with no remote is used where it is). Add by URL or Use a folder on this Mac for anything else.
  2. Make a workspace. Name it and tick its projects; the page shows the session it makes (<name>/main).
  3. Getting it ready. Its main worktree is checked out, its .env copied and each project installed, one row per project. It moves on by itself; an install that fails stays on screen with its last lines, Fix with Claude, Retry and Continue.

The first run's last screen: store/main is ready, 2 projects checked out and installed, with Open Voice OS and Go to Set up

Then Open Voice OS opens that worktree's session, or Go to Set up opens the board. A project's dev servers, when it has any, go on its Edit setup form, or Setup with Claude works them out. crew's own state says where the steps start, so projects added with a terminal crew add project are already there, and reopening the page while the worktree installs comes back to its progress.

On a phone

The page works at phone width: the toolbar, the strip and the forms stack, and the tables scroll sideways.

The board on a phone: Setup with Claude stacked under the tabs and the projects table scrolling sideways

To reach it from a phone, set the proxy domain in Settings and trust crew's certificate on the phone (Other devices has the details).

More: Tutorial 1 (the same steps, on the page and as commands) · Voice OS · every command