Skip to content

feat: create every crewmate from one card and let it ask its goal - #17617

Merged
buluoray merged 1 commit into
feat/crewmate-assistant-integrationfrom
feat/crewmate-quick-create
Oct 9, 2026
Merged

buluoray merged 1 commit into
feat/crewmate-assistant-integrationfrom
feat/crewmate-quick-create

Conversation

@buluoray

@buluoray buluoray commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

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

  • Changing what a crewmate is, how it is stored, or its permissions.
  • Removing any create field: everything the old form offered stays under "Advanced settings".
  • Changing Captain's own first greeting.
  • Model or template recommendations.

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.

  • Dialog (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.
  • Default template: new crewmates default to kirocrew (DEFAULT_CREWMATE_TEMPLATE); the template name shows only inside Advanced settings.
  • First greeting: create records a first_greeting owed marker (crew_records.py). When the thread opens, useMemberFirstGreeting calls POST /api/members/{slug}/greet, which now serves crewmates as well as Captain (maybe_start_member_greeting in captain_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.
  • Change card: a crewmate created from a Captain card sends first_greeting too, so it greets the same way.
  • Doors: the roster "+" menu holds only New crewmate and New team; New crewmate, the empty-state hero and the switcher open this card folded, and the hero's Advanced link opens it unfolded. On the base branch those doors opened the guided goal-and-schedule flow (MeetCrewmatesFlow), and the "+" menu also had an Advanced row. The guided flow still opens for a drafted proposal (a Captain card or a name/goal link). The members.add-menu.advanced guide location goes with the row; "advanced crewmate setup" now finds the "+" menu itself.
  • Greeting: this replaces the base branch's visible seeded first message (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.tsx drops its inline create form and opens the dialog; i18n for all 13 locales; crew-mode.md, crew-members.md and 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.

  • Removed: MeetCrewmatesFlow.tsx, useMeetCrewmatesGate.ts and their tests, the START_MEET_CREWMATES_EVENT / CREWMATES_PAGE_ENTERED_EVENT events, the creation receipt, and the dead components.meetCrewmatesFlow.* strings in every locale. hasNoCrewmates moves to rosterFilter.ts with its test.
  • Doors: a Captain create link (/members?create=1&name=&goal=, clicked in chat or opened as a deep link) and the crewmate.create guide 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.
  • Guide: crewmate.create is a single create step on the card's Create button.
  • Greeting: the crewmate's hidden first turn still asks for the goal (or confirms a written one); once the goal is clear and the work should run on its own, it offers a schedule in plain words and sets it up only after the person agrees, never silently (captain_greeting.py).
  • Docs: crew-mode.md, config.md, crew-members.md and the feature map describe the single card.
  • The two manual pod scripts (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_greeting field; existing callers that omit it get no greeting, exactly as today. /greet keeps 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.py pins "advanced crewmate setup" to members.add-menu, and MembersPage.test.tsx pins the menu to New crewmate and New team
Reader: website/src/pages/members/MembersPage.tsx:handleCreated -- crew page -- the visible greeting_seed turn and its retry notice are replaced by /greet; MembersPage.test.tsx pins one greeting per created crewmate
Reader: website/src/pages/members/useMemberFirstGreeting.ts -- crew page -- renamed from useCaptainFirstGreeting; its one caller and the comment that named it are updated
Reader: website/src/pages/members/MembersPage.tsx:openGuided -- crew page -- replaced by the prefilled card open; MembersPage.test.tsx and NewCrewmateDialog.guided.test.tsx pin the create link, the deep link and the guide door
Reader: src/kiro_crew/guide_catalog.py:crewmate.create -- chat (Captain guides) -- now one create step; test_guide_* pin it
Reader: 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 it
Reader: website/src/hooks/useTheme.tsx:crewmatesOnboarded -- crew page -- frontend state removed, no reader left; the backend crewmates_onboarded field stays

Every 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 /greet route 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 sends first_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.tsx also 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 sends first_greeting: true and opens the new crewmate; the rules for a newer proposal replacing the card.
  • NewCrewmateDialog.test.tsx (+5) and NewCrewmateDialog.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 that crewmate.create is one commit step; guide prefill length caps fit the card's fields. GuideLayer.test.tsx and test_guide_runs.py move their generic multi-step fixtures to mcp.open_add.
  • Mutation check: unfolding Advanced for a goal, the dirty-vs-initialDraft comparison, the guided headers, the refused callback, the draft kept on link click, passing initialDraft, 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

New crewmate dialog, collapsed

Advanced settings expanded

Phone, collapsed

toggle.mp4
More: tooltip, end of the expansion, dark mode, phone expanded

Refresh-look tooltip

End of Advanced settings with the second Create

Dark, collapsed

Dark, expanded

Phone, expanded

Phone, end of the expansion

The roster "+" menu holds New crewmate and New team only:

Crew page, "+" menu open

Phone, "+" menu open

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):

First greeting in a new crewmate's chat

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.

Prefilled card from a Captain link

The crewmate.create guide pointing at Create

More: end of Advanced settings, phone, empty create link

End of Advanced settings with the second Create

Phone, prefilled

Empty create link: folded and empty

Not capturable as images:

  • The leave guard on an edited card is the browser's native 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.
  • The crewmate's first message offering a schedule needs a running agent; the isolated test gateway in this environment cannot start agent processes, so it is covered by test/test_captain_greeting.py only.

Related Issues

Stacked on #15326 (Captain); base branch feat/crewmate-assistant-integration.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

Contribution License Agreement

Contributions are accepted under the project's Apache-2.0 license; see the Licensing section of CONTRIBUTING.md.

@buluoray
buluoray requested a review from a team as a code owner October 7, 2026 06:03
@buluoray
buluoray requested review from chenmingwei23 and removed request for a team October 7, 2026 06:03
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 7, 2026
@github-actions

github-actions Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 3f4a0bca69f1247889d4a3d5664df6dbc398145c — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

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 MeetCrewmatesFlow. Only the later part matches the diff.

[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 .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — 🔴 BLOCK

Premise-level review of 3f4a0bca69f1247889d4a3d5664df6dbc398145c — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

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 rfc-crewmates-launch §02/§08 record differently.

Not justified as shipped

  • Item 1 — product shape, no recorded decision: the accepted RFC §02 says New crewmate "opens a dialog with four things: Name; Built from …; What it looks after (optional); Advanced, folded". The diff moves Built from and What it looks after behind Advanced.
  • Item 2 — product shape, no recorded decision: the diff removes MeetCrewmatesFlow.tsx, but RFC §08 says "Decided: a four-step flow … The Crewmates page keeps its on-demand Meet CrewMates entry." The description also contradicts itself. It says "The guided flow still opens for a drafted proposal", then lists "Removed: MeetCrewmatesFlow.tsx".

What this change ships

Inventory (8 items) — 6 justified

Intent: 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.

  1. New crewmate card shows avatar and name; Built from and What it looks after are folded into Advanced — product shape, not covered by RFC §02
  2. Four-step guided Meet CrewMates flow (goal, name, schedule, ready) removed; every door opens the card — product shape, contradicts RFC §08
  3. New crewmate greets first through a hidden kickoff turn — justified
  4. Visible seeded first message and its "Send it again" retry replaced — justified
  5. Greeting offers a schedule and sets it up only after consent — justified
  6. "+" menu Advanced row and its guide location removed — justified
  7. Captain change card and create link open the prefilled card with a greeting — justified
  8. crewmate.create guide reduced to one create step — justified

Blockers

  • Product-shape change without accepted RFC: dialog fields and Meet CrewMates removal. rfc-crewmates-launch.md is accepted on base. Its §02 and §08 text decide the opposite shapes, and the diff does not amend them. docs/decisions/ has no entry for either.
    Clears when: an RFC amendment covering the folded card and removing the guided flow merges non-draft on base (then push or rebase), or a maintainer posts /ai-review override first-principles 3f4a0bca69f1247889d4a3d5664df6dbc398145c: <decision>.

[FIRST-PRINCIPLES-REVIEWED] 3f4a0bc

Description read

[DESCRIPTION-READ] 597e5ced7369edb8f9c0b7c05132f36dfe0ae5132f24e2be5c6a9b0508c4b41c

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — 🟡 CONCERNS

UX-level review of 3f4a0bca69f1247889d4a3d5664df6dbc398145c — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

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

  • Most screenshots are older than the copy in this diff. Shots 02, 07 and 08 show "add a schedule after creating, on the Schedule page". The diff replaces that create_job_hint with "your crewmate can set up a schedule with you once it's created". The blind reader saw both versions and said it "can't tell which is true", which means the folded and advanced views in 01–09 were not captured at this HEAD. Severity: medium. It is reviewer friction only, but the current shots for those states are missing. Fix: retake 01–09 at HEAD.
  • "Built from" lost its plain wording. built_from_default went from "{{agent}} — the standard setup (default)" to "{{agent}} (default)". The reader saw "kirocrew in lowercase looks like a technical name", said they would "probably not" change it, and listed "default" as meaning five different things on one form. Severity: low. It sits inside Advanced settings, but it shows up every time someone unfolds them. Fix: keep "the standard setup" in the option label itself rather than only in the hint.
  • Avatar re-roll was read correctly but only as a guess. The caption says "Tap the picture" while the "Try another look" tooltip sits on the badge, so the reader could not tell whether the whole picture or just the badge is the control. Severity: low. This is the first control on the card, but nothing breaks if it's misread. Fix: make the caption and tooltip name the same target (the whole tile is the button).

Suggestions

  • create_avatar_caption: change it to "Tap for another look" so it no longer points at a different spot from the badge's tooltip.

[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 .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 3f4a0bca69f1247889d4a3d5664df6dbc398145c — this comment is updated in place on each push.

Review details

No findings that block the merge.

FINDING — src/kiro_crew/dashboard/captain_greeting.py:87 — when a confirmed crewmate.create card carries a schedule, it sets "first_greeting": True and also POSTs /api/crons. The crewmate's hidden first turn then tells it to "offer a schedule … Set it up with your schedule tool". crewmate_goal_kickoff gets only the description, so the crewmate doesn't know a schedule already exists. It asks the user to schedule work that's already scheduled, and a "yes" creates a second recurring job → Fix: in change_card_catalog.py's create branch, leave out first_greeting when there's a schedule, or pass the schedule into the kickoff so it says the crewmate already runs on <cron_expr> and shouldn't offer another.

[OPUS-REVIEWED] 3f4a0bc

Verdict parsed from the review's SHA-scoped output markers for commit 3f4a0bca69f1247889d4a3d5664df6dbc398145c.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 3f4a0bca69f1247889d4a3d5664df6dbc398145c: <one-sentence reason>

@github-actions

github-actions Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 3f4a0bca69f1247889d4a3d5664df6dbc398145c and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 3f4a0bc

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 3f4a0bca69f1247889d4a3d5664df6dbc398145c: <one-sentence reason>

@buluoray
buluoray force-pushed the feat/crewmate-quick-create branch 2 times, most recently from 2e6207f to 8945a17 Compare October 7, 2026 06:32
@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 7, 2026
@buluoray
buluoray force-pushed the feat/crewmate-quick-create branch from 8945a17 to d212678 Compare October 7, 2026 07:37
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 7, 2026
@buluoray
buluoray force-pushed the feat/crewmate-quick-create branch from d212678 to bbc1dc4 Compare October 7, 2026 09:54
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 7, 2026
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.
@buluoray buluoray changed the title feat: create a crewmate from a name and a look, then let it ask its goal feat: create every crewmate from one card and let it ask its goal Oct 7, 2026
@buluoray
buluoray force-pushed the feat/crewmate-quick-create branch from bbc1dc4 to 3f4a0bc Compare October 7, 2026 18:47
@buluoray

buluoray commented Oct 7, 2026

Copy link
Copy Markdown
Contributor Author

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 crewmate.create guide open this same card prefilled with the name and goal; the crewmate offers a schedule in its first chat and creates it only after the person agrees. The "Not a goal" line about create options now reads "create field", because every field of the old form is still reachable under Advanced settings while the separate guided chapter is gone. #17677 is closed in favour of this PR.

@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 7, 2026
@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 7, 2026
@buluoray
buluoray merged commit 49801cb into feat/crewmate-assistant-integration Oct 9, 2026
23 of 25 checks passed
@buluoray
buluoray deleted the feat/crewmate-quick-create branch October 9, 2026 05:27
@github-actions github-actions Bot removed the readiness: action required A blocking check or review needs attention label Oct 9, 2026
buluoray added a commit that referenced this pull request Oct 10, 2026
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
buluoray added a commit that referenced this pull request Oct 11, 2026
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
buluoray added a commit that referenced this pull request Oct 11, 2026
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
buluoray added a commit that referenced this pull request Oct 11, 2026
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
buluoray added a commit that referenced this pull request Oct 11, 2026
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
buluoray added a commit that referenced this pull request Oct 11, 2026
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
buluoray added a commit that referenced this pull request Oct 11, 2026
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
buluoray added a commit that referenced this pull request Oct 12, 2026
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
buluoray added a commit that referenced this pull request Oct 12, 2026
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
buluoray added a commit that referenced this pull request Oct 12, 2026
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
buluoray added a commit that referenced this pull request Oct 12, 2026
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
buluoray added a commit that referenced this pull request Oct 12, 2026
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
buluoray added a commit that referenced this pull request Oct 12, 2026
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
buluoray added a commit that referenced this pull request Oct 12, 2026
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
buluoray added a commit that referenced this pull request Oct 12, 2026
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
buluoray added a commit that referenced this pull request Oct 12, 2026
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
buluoray added a commit that referenced this pull request Oct 12, 2026
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
buluoray added a commit that referenced this pull request Oct 12, 2026
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
buluoray added a commit that referenced this pull request Oct 12, 2026
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
buluoray added a commit that referenced this pull request Oct 13, 2026
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant