Crews & shapes
The team is the operator’s decision, never the calling model’s. A crew is a name, a set of seats, and a policy that says how the team works.
The nine seats#
These are the roles Wednesday actually runs, in pipeline order. A seat is not a tool: it cannot be called from MCP.
| Seat | Job | Routing slot |
|---|---|---|
architect | System shape, boundaries, interfaces. | planner |
planner | Turns the request into files, steps, and a verification plan. | planner |
coder | Writes the change inside the sandbox. | coder |
tester | Runs the declared commands; a failing gate blocks. | coder |
reviewer | Reads the result against acceptance criteria. | coder |
vision | Reads UI and screenshots when the request is visual. | vision |
autocomplete | Fast, cheap completions for the small loops. | coder |
bug-hunter | Looks for the failure the happy path hides. | coder |
security-audit | Checks secrets, dangerous calls and the boundary. | coder |
A crew may seat fewer than nine. A seat that shares a routing slot with another seat uses the slot’s model unless it is given its own endpoint or model. A seat that is not staffed falls back to the slot; a smaller crew clears the slots it does not fill.
The five shapes#
| Shape | How the team works |
|---|---|
solo | One model, one job. The simplest run. |
duel | Two attempts, one answer. |
vote | The crew proposes and the answer is chosen. |
relay | Seats hand the work to each other. |
auto | The task difficulty decides. This is the default when a crew declares no shape. |
The shape is crew policy, not a per-request hack. The calling model cannot change it.
Crew policy#
Policy decides how the team works, as opposed to who is in it.
| Setting | Meaning |
|---|---|
shape | solo, duel, vote, relay, or auto. |
repairs | How many times a failing verification may be repaired. |
tokens | A token ceiling for one run. |
usd | A USD ceiling for one run. |
test | The verification command this crew always runs. |
files | Extra files every task in this crew must produce. |
Staff the crew from the CLI#
wednesday team # list crews, active marked
wednesday team add demo coder=qwen/qwen3-coder reviewer=local/qwen2.5-coder-3b --shape auto
wednesday team use demo # make it the active crew
wednesday team seat coder another-model # swap one seat of the active crew
wednesday team set shape solo # shape | repairs | tokens | usd | test | files
wednesday team set test "npm test" # the verification command
wednesday team show # seats, models, policy
wednesday team delete demo # remove a crew
Every mutating verb prints the honest consequence: Restart the MCP server (or reconnect your client) to adopt it.
Adoption and in_sync#
A crew is adopted when the MCP server starts. The server applies the same env slots the engine reads, so the engine has one truth regardless of which client is attached. A crew changed while a server is running does not change that server.
wednesday_team reports both adopted (what this process is running with) and selected (what is on disk now). If they differ, in_sync: false means reconnect — never silently run a stale roster.
Where a crew lives#
A crew is plain JSON in ~/.wednesday/state/crews.json. The shape is stable enough to inspect, and the CLI is the supported writer.
{
"crews": [
{
"id": "mwhj41z3_6bxu",
"name": "demo",
"seats": [
{ "role": "planner", "model": "local/qwen2.5-coder-3b" },
{ "role": "coder", "model": "local/qwen2.5-coder-3b" },
{ "role": "reviewer", "model": "openrouter/another-model" }
],
"policy": { "shape": "auto", "maxRepairAttempts": 2 }
}
],
"active": "mwhj41z3_6bxu"
}