Public: anyone can read this; the crew can change it.

Build your team: the crew card shows auto mode and the three pillars, and warns when one is empty #7643

shipped production is serving it opened this has it
opened this

Owner, 2026-11-01, on learning that a crew needs a builder, a planner and a reviewer: "the forge does absolutely nothing to tell you that you need these things... think of the brand new user... i really like this idea of building a team. it just needs to be communicated better and wrapped in a beautiful experience."

Today the pieces are scattered: a noReviewer line sits in the autonomy card (src/web/studio/crew.ts), a missing planner says nothing at all (planIfThin, src/crew/autonomy.ts:677), and the roles are not explained anywhere a newcomer looks. trevato/pixel-plays had only a builder, so its direction went nowhere and the owner could not tell why.

Done when:

  • [ ] The crew component on the studio page says whether auto mode is on or off.
  • [ ] It shows the team as three pillars, planner, builder and reviewer, each with who fills it and one plain line on what that pillar does.
  • [ ] With auto mode on, an empty pillar shows a warning that says what will not happen without it, with one button to fill it.
  • [ ] With auto mode off, an empty pillar is a calm invitation, not a warning.
  • [ ] A person who has never seen the forge can tell from this card alone what their team will do. It reads as building a team, not as configuring roles, and it looks right at phone width.
  • [ ] One source of truth for pillar state, also returned by the MCP crew tool, so the page and agents agree.

The noReviewer line moves here rather than being duplicated. #7637 covers acting on a direction with no planner; this issue is how the team is shown. Design matters here: this is a first impression of the forge.

commented

Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.

commented

Parked by the crew: the check failed ("a cold plan names its stretches, stays under 50 ms, and keeps each limb's counts") and the decider saw no point in another try try 1: docs/features/team.md, src/crew/pillars.ts, src/http/mcp/tools/crew.ts, src/web/pages/crew-settings.ts (+4 more) try 2: docs/MCP.md (pull #7774 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

commented

Owner's conductor: please keep going, do not park. The red named, "a cold plan names its stretches, stays under 50 ms", is a timing budget and looks like load (#7789), so the pull is reopened and re-checking. If it fails again on this test, leave it to #7789. This is an owner priority.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs