Repository navigation
fix(crew-mode): the dispatch notice names the Board and opens it - #27454
Conversation
The notice a chat shows after crew members are dispatched still said "Crew tab" with a people icon. The side-panel tab is the Board with a bolt icon, so the text now says "listed on the Board in the side panel" and the button reads "Open Board" with the same bolt glyph. The button keeps the existing host reveal, which opens the side panel on the Board (view workers), never Dashboard. The catalog key moves from openCrewTab to openBoard in every locale, each using that locale's Board tab label; the gateway's plain-English fallback matches. Closes #27408
UX Review (Opus 5.5) — ✅ PASSUX-level review of UX-Verdict: PASS Nothing blocks. The notice and its button are both shown before and after, and the blind reader correctly read "Open Board" as opening the Board in the side panel. Notes
[UX-REVIEWED] 2574bf2 Description read[DESCRIPTION-READ] 44e72b353acb92e140a20ef88c0f7fcbad160d6e8a9fe505afb985893f413082 That sha256 names everything this verdict read: the PR description, plus the 5 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) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS This fixes copy that sent people to a "Crew tab" the tab strip no longer shows. Only the wording, the icon and one catalog key change. What this change shipsInventory (6 items) — 6 justifiedIntent: after a dispatch, the notice should send the person to the side-panel tab that really exists, so they can find the crew members that were started. FIX (closes #27408).
[FIRST-PRINCIPLES-REVIEWED] 2574bf2 Description read[DESCRIPTION-READ] dfc0b390d25944f684853080348d97fd0d8ce78a602b12d2f1ef753e74a14179 That sha256 names the PR description this verdict read. Recompute it with |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Nothing blocks: a copy and icon fix that brings one stale notice in line with the renamed Board tab. No other code still reads the removed [DESIGN-REVIEWED] 2574bf2 Description read[DESCRIPTION-READ] 7f6dbe71912281f4ae73e1a9cc475167780b928ebddff1ad29ada6d0a529df41 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 |
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: |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
Problem / Motivation
Goal: The notice shown after crew members are dispatched names the Board, with the Board's bolt icon, and its button opens the Board.
After a dispatch, the chat shows "Crew members were started — they're listed in the Crew tab of the side panel, not the session list." with an Open Crew tab button and a people icon. That tab is now called Board and wears a lightning bolt (#26291, #26882), so the notice points at a tab name nobody sees.
Why it matters
Every Ultra Mode user sees this notice on their first dispatch. It sends them looking for a "Crew tab" that does not exist on the strip.
Not a goal
workers, theonOpenCrewTab/handleOpenCrewTabprop and callback names, or thecrew_dispatch_noticewire kind.What changed (motivation → approach → change)
The notice now reads "Crew members were started — they're listed on the Board in the side panel, not the session list." Its button says Open Board and uses the Board tab's own glyph, lucide
Zap(the same iconSidePanelTabIconsgivesworkers). The button keeps its existing host reveal,openCrewSession, which opens the side panel on the Board (viewworkers), never Dashboard.pages.chat.crewDispatchNotice.textpages.chat.crewDispatchNotice.openCrewTab→openBoardCREW_DISPATCH_NOTICE_TEXTinsrc/kiro_crew/dashboard/crew_dispatch_notice.py(fallback for channel mirrors and SSE)components.crewMode.ultra_ms_nowtranslator note inwebsite/src/i18n/en.context.jsonEvery locale is updated, each using that locale's existing Board tab label (
commandCenter.workers, e.g. 看板, Tableau, Доска). The oldopenCrewTabkey is removed. The feature map row for the dispatch notice indocs/feature-map/README.mdnames the Board too.A sweep of user-facing strings, catalogs and in-app docs (
src/kiro_crew/docs) found no other "Crew tab". The "Crew page" strings that remain mean the Issue Radar crew page and the crewmate Crew page, not this tab, so they stay.Backwards compatibility
Compatible: the wire kind, view id and reveal are unchanged; only display copy and one catalog key change.
Reader: website/src/pages/chat/CrewDispatchNoticeCard.tsx:CrewDispatchNoticeCard -- chat -- reads the new
openBoardkey;CrewDispatchNoticeCard.test.tsxReader: test/test_crew_dispatch_notice_parity.py:test_english_catalog_defines_the_keys -- release -- pins the new key set
{"text", "openBoard"}Tests
website/src/pages/chat/CrewDispatchNoticeCard.test.tsx"names the Board and its button opens the side panel on the Board tab, not Dashboard": the text names the Board and not the Crew tab, the button is named "Open Board" and carries the bolt glyph, and a click through the realopenCrewSessionmakesworkersthe active tab with nocommand-centertab and the panel open. It fails onorigin/main(2 of 6 tests red there) and passes here.test/test_crew_dispatch_notice_parity.pypins the renamed key in the card and inen.json.website/src/test/TurnBlock.crewDispatchNotice.test.tsxandwebsite/src/test/chatRolesParity.contract.test.ts: only their wording about the button changes.Proof: not provable -- frontend test (prove.py runs Python only)
Local: targeted vitest (notice card,
TurnBlock.crewDispatchNotice,chatRolesParity, all ofsrc/i18nincluding the fr style rules), the parity pytest,tsc -p tsconfig.app.json, eslint,i18n:check,i18n:render,gen:ui --check, feature-map, comment-history and semgrep all pass.Manual verification
Rendered the real
CrewDispatchNoticeCardin dark theme with the Crew Mode preview on, once fromorigin/mainand once from this branch, in a local loopback Vite page (not committed).Screenshots / video
Before (dark,
origin/main):After (dark, this branch):
Related Issues
Closes #27408
Sibling sweep
Swept: git grep -n -i -E "crew tab|openCrewTab" -- website/src/i18n src/kiro_crew website/src
Sibling: src/kiro_crew/dashboard/crew_dispatch_notice.py -- changed here
Sibling: website/src/i18n/en.context.json -- changed here
Sibling: website/src/components/CrewModeWelcome.tsx -- not affected -- its button already says Board and opens it, fixed in #26882
Pattern harvest
Not generalizable: a one-time tab rename left one notice string behind; the rename PRs already swept the rest.
Checklist