Repository navigation
feat: create every crewmate from one card and let it ask its goal - #17617
Conversation
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Before merge, fix the description: one part says the guided flow "still opens for a drafted proposal", but a later part deletes [DESIGN-REVIEWED] 3f4a0bc Description read[DESCRIPTION-READ] 8e4250671d18f6b1c09565cc3ba739aa321950b69c26ba6e75b588967361b7e3 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
First Principles Review (Opus 5.5) — 🔴 BLOCKPremise-level review of First-Principles-Verdict: BLOCK Product-shape change without accepted RFC: this replaces the four-step Meet CrewMates flow and the New crewmate dialog's field set, both of which accepted Not justified as shipped
What this change shipsInventory (8 items) — 6 justifiedIntent: a person creates a crewmate from a name and a look, and the new crewmate asks what it should work on. This is an ADDITION.
Blockers
[FIRST-PRINCIPLES-REVIEWED] 3f4a0bc Description read[DESCRIPTION-READ] 597e5ced7369edb8f9c0b7c05132f36dfe0ae5132f24e2be5c6a9b0508c4b41c That sha256 names the PR description this verdict read. Recompute it with |
UX Review (Opus 5.5) — 🟡 CONCERNSUX-level review of UX-Verdict: CONCERNS Screenshots 01–09 still show the old Schedule-page hint, and the "Built from" picker shows a bare "kirocrew (default)" that the blind reader would not touch. Watch
Suggestions
[UX-REVIEWED] 3f4a0bc Description read[DESCRIPTION-READ] 02bb00d989097b282b04c278392a23ff59f7873e7d5f63ed6758738e6388653e That sha256 names everything this verdict read: the PR description, plus the 20 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Opus 5.5 Review — ✅ no blocking findingsReviewed Review detailsNo findings that block the merge. FINDING — src/kiro_crew/dashboard/captain_greeting.py:87 — when a confirmed [OPUS-REVIEWED] 3f4a0bc Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
2e6207f to
8945a17
Compare
8945a17 to
d212678
Compare
d212678 to
bbc1dc4
Compare
A person creates a crewmate from a name and a look; template, role, model and workspace stay under Advanced settings. Captain's create proposals, create links and the crewmate.create guide open the same card prefilled with the name and goal. The new crewmate opens its chat with a hidden first turn that asks for its goal and offers a schedule only when the person agrees. The guided goal, name and schedule chapter is removed.
bbc1dc4 to
3f4a0bc
Compare
|
Scope note: at the owner's request this PR now also carries what was #17677 (one create flow). The guided goal → name → schedule chapter is removed, and Captain's create proposals, create links and the |
49801cb
into
feat/crewmate-assistant-integration
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Port of #17617 onto main. The Crewmates page creates a crewmate on one New crewmate card (Name, Avatar with Try another look, Create), with everything else under an inline Advanced settings fold, instead of the guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the switcher, a crewmate's create link and the crewmate.create guide all open that card; the guide's crewmate.create action is one commit step. The card's create sends first_greeting. POST /api/agents then records a goal welcome (welcome_owed.json, kind "goal"), and the existing POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden goal kickoff: the crewmate introduces itself and asks what it should do, or confirms the job written under Advanced settings. The page asks for the greeting on dashboard-created rows as well as Mate's. Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter mount, the created-crewmate receipts, the seeded first-turn send and its retry notice, and the theme's crewmates_onboarded reads and writes (the gateway keeps carrying the flag for compatibility). Docs: RFC crewmates-launch section 02 amended (08 marked superseded), crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members and gui-user-test updated; UI index regenerated. Part of #18300
Problem / Motivation
Goal: A person creates a crewmate from just a name and a look, and the new crewmate greets them and asks what it should work on.
Today "New crewmate" opens a long form: template, role, model, workspace and description all compete for attention before the person has decided anything, and the crewmate then waits silently in an empty thread. Most people only want a name and a face, and they do not know which template or role to pick.
Why it matters
Creating a crewmate is the first thing a new user does after Captain. A heavy form at that moment makes the feature feel like configuration work, and an empty thread afterwards gives no hint what to say. A two-field create plus a greeting that asks for the goal turns it into a conversation.
Not a goal
What changed (motivation → approach → change)
Goal → keep the dialog to the decisions a person actually makes (look, name) → move the rest behind one inline disclosure, and let the crewmate open the conversation.
NewCrewmateDialog.tsx): a large centred avatar tile with a refresh badge (with tooltip and caption) picks a random look; then the name field, a hint and a full-width Create. A centred "Advanced settings" toggle expands inline (template, role, model, workspace, description), with a second Create at the end of the expansion. Cancel is the X in the header. Icons only, no emoji.kirocrew(DEFAULT_CREWMATE_TEMPLATE); the template name shows only inside Advanced settings.first_greetingowed marker (crew_records.py). When the thread opens,useMemberFirstGreetingcallsPOST /api/members/{slug}/greet, which now serves crewmates as well as Captain (maybe_start_member_greetingincaptain_greeting.py). The greeting is a hidden kickoff turn (crewmate_goal_kickoff) — no visible user bubble — and asks the person for the crewmate's goal. It starts once, only while the thread is empty. Captain's path (maybe_start_captain_greeting) is unchanged.first_greetingtoo, so it greets the same way.MeetCrewmatesFlow), and the "+" menu also had an Advanced row. The guided flow still opens for a drafted proposal (a Captain card or aname/goallink). Themembers.add-menu.advancedguide location goes with the row; "advanced crewmate setup" now finds the "+" menu itself.greeting_seed, sent as a user turn with a "Send it again" retry) with the hidden kickoff above, so the thread opens with the crewmate speaking, not with words put in the person's mouth. When "What it looks after" is filled, the crewmate confirms that job instead of asking, and the hint under the name says so.MembersPage.tsxdrops its inline create form and opens the dialog; i18n for all 13 locales;crew-mode.md,crew-members.mdand the feature map describe the new flow.One create flow, so every door opens this card:
Goal → one create surface → every former door of the guided chapter now opens the card, and the schedule question moves into the crewmate's first greeting.
MeetCrewmatesFlow.tsx,useMeetCrewmatesGate.tsand their tests, theSTART_MEET_CREWMATES_EVENT/CREWMATES_PAGE_ENTERED_EVENTevents, the creation receipt, and the deadcomponents.meetCrewmatesFlow.*strings in every locale.hasNoCrewmatesmoves torosterFilter.tswith its test./members?create=1&name=&goal=, clicked in chat or opened as a deep link) and thecrewmate.createguide open the card in place, prefilled: the name in Name, the goal in "What it looks after" with Advanced settings unfolded so it is visible. The chat stays mounted and its draft is kept; closing the card returns to it. An untouched card is replaced by a newer proposal; an edited one asks its own leave guard first.crewmate.createis a singlecreatestep on the card's Create button.captain_greeting.py).crew-mode.md,config.md,crew-members.mdand the feature map describe the single card.verify-assistant-guide.mjs,verify-crewmate-assistant.mjs) drive the card instead of the removed chapter.Backwards compatibility
Compatible: the create API only gains an optional
first_greetingfield; existing callers that omit it get no greeting, exactly as today./greetkeeps its Captain outcomes and answers 200 with a declining outcome for any member that is not owed a greeting.Reader: website/src/uiLocations/areas/members.ts:members.add-menu.advanced -- chat (Captain guides) -- removed with its row;
test_find_ui_members.pypins "advanced crewmate setup" tomembers.add-menu, andMembersPage.test.tsxpins the menu to New crewmate and New teamReader: website/src/pages/members/MembersPage.tsx:handleCreated -- crew page -- the visible
greeting_seedturn and its retry notice are replaced by/greet;MembersPage.test.tsxpins one greeting per created crewmateReader: website/src/pages/members/useMemberFirstGreeting.ts -- crew page -- renamed from
useCaptainFirstGreeting; its one caller and the comment that named it are updatedReader: website/src/pages/members/MembersPage.tsx:openGuided -- crew page -- replaced by the prefilled card open;
MembersPage.test.tsxandNewCrewmateDialog.guided.test.tsxpin the create link, the deep link and the guide doorReader: src/kiro_crew/guide_catalog.py:crewmate.create -- chat (Captain guides) -- now one
createstep;test_guide_*pin itReader: website/src/components/MeetCrewmatesFlow.tsx:scheduleFor -- none -- no caller outside the removed file
Reader: website/src/hooks/useMeetCrewmatesGate.ts:hasNoCrewmates -- crew page -- moved to
rosterFilter.ts, test moved with itReader: website/src/hooks/useTheme.tsx:crewmatesOnboarded -- crew page -- frontend state removed, no reader left; the backend
crewmates_onboardedfield staysEvery field of the old form stays reachable under Advanced settings.
Tests
test/test_captain_greeting.py: a send that lands while the description is read wins over the greeting (no await between the last recheck and dispatch); an owed crewmate gets one hidden kickoff turn with no transcript row; a crewmate not owed a greeting, one with messages, or one whose slot runs as another member never greets; Captain is routed to its own greeting; the kickoff asks for the goal, carries the description and never names the template; the/greetroute greets an owed crewmate and still refuses app tokens and bad slugs.test/test_api_agents_create_template.py: a flagged create marks the greeting owed by member id; a create without the flag owes nothing.test/test_change_cards.py: the crewmate change card sendsfirst_greeting.NewCrewmateDialog.test.tsx: folded by default (look, name, hint, Create; template never named); unfolding shows Built from = kirocrew; values survive folding; Create builds from kirocrew with the shown look and asks for the greeting; re-roll changes the look and shows the tooltip; reading order and the X beside the heading; 44 px touch targets on a phone; Advanced ends with a second Create that submits once; controls lock while a create is in flight; a written job turns the hint into "will confirm this job".MembersPage.test.tsxalso pins the "+" menu to New crewmate and New team.MembersPage.test.tsx: the roster "+" and empty-state entries open the card folded or unfolded; Create from a name alone builds from the built-in agent, opens the chat and asks for the greeting; no greeting for crewmates not created on the dashboard, after leaving the page, or twice; a failed open frees the "+".MembersPage.test.tsx("create links open the New crewmate card"): a create link opens the card prefilled with the name and the goal in an unfolded Advanced settings, without remounting the chat; an empty link opens it folded and empty; a deep link is stripped after reading; malformed escapes do not throw; a prefilled Create sendsfirst_greeting: trueand opens the new crewmate; the rules for a newer proposal replacing the card.NewCrewmateDialog.test.tsx(+5) andNewCrewmateDialog.guided.test.tsx(new, 4): the guided door's request headers and lifecycle; an unguided door never touches the guide.test/test_captain_greeting.py: a kickoff carrying a goal still starts with the full kickoff and stays a hidden gateway turn with no transcript row.test_guide_routes.py: frontend and backend agree thatcrewmate.createis one commit step; guide prefill length caps fit the card's fields.GuideLayer.test.tsxandtest_guide_runs.pymove their generic multi-step fixtures tomcp.open_add.initialDraftcomparison, the guided headers, the refused callback, the draft kept on link click, passinginitialDraft, the goal kickoff prefix, the single-step catalog and the field length caps each turn a named test red.Manual verification
Against an isolated test-mode gateway (own
KIROCREW_HOME): created a crewmate with only a name, saw the dialog close into the new thread, and watched the crewmate greet and ask for its goal with no user bubble. Checked light, dark and a 390 px phone width; toggled Advanced settings open and closed.Screenshots / video
toggle.mp4
More: tooltip, end of the expansion, dark mode, phone expanded
The roster "+" menu holds New crewmate and New team only:
The first chat turn after a create: the crewmate opens by asking what it should own, with no user bubble above it (captured on an earlier build of this branch; the greeting path is unchanged since):
Opened from a Captain create link (
/members?create=1&name=Scout&goal=…): the name is prefilled, Advanced settings unfolds with the goal in "What it looks after", and the hint under the name says the crewmate will confirm this job.More: end of Advanced settings, phone, empty create link
Not capturable as images:
window.confirm("Leave this page? Your unsaved crewmate draft will be lost."). Reproduced on a test gateway: edit the name, open a second create link, the prompt appears; Cancel keeps the edited draft.test/test_captain_greeting.pyonly.Related Issues
Stacked on #15326 (Captain); base branch
feat/crewmate-assistant-integration.Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Contribution License Agreement
Contributions are accepted under the project's Apache-2.0 license; see the Licensing section of CONTRIBUTING.md.