Skip to content

feat(crewmate-chat): colour the two speakers like iMessage - #17918

Merged
buluoray merged 1 commit into
mainfrom
feat/crewmate-bubble-colors
Oct 8, 2026
Merged

buluoray merged 1 commit into
mainfrom
feat/crewmate-bubble-colors

Conversation

@CrysisDeu

@CrysisDeu CrysisDeu commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: In a crewmate's chat, the user's bubble is filled with the theme accent and the crewmate's bubble is a neutral gray, so the two speakers are told apart by colour the way iMessage does it.

Today both bubbles sit on the same neutral surface: the user's is the filled bg-card one, the crewmate's an outlined bg-transparent one, and only alignment separates the two. Zezhen asked for the iMessage / Metamuse pairing (#17839) and chose option A (solid theme accent) after real-theme screenshots of three options across eight themes.

Why it matters

A crewmate DM is a 1:1 thread the user reads at a glance between other work; two same-coloured bubble columns make the eye re-derive "who said this" from the margin every time. The accent/gray pairing is the convention every messaging app has trained users on, and it carries the theme (amber goes yellow, dracula goes purple) the way the Settings selected state already does.

Not a goal

  • The single-chat page's user bubble (bg-card, the kiro-light --bg-hover tint) is untouched: the tone prop defaults to default and only the crewmate user entry sets accent.
  • The steer tint (bg-accent-subtle) a steer draws WITH its badge on the single-chat page is unchanged and wins over the tone.
  • Slack / Discord renderings; the reply-thread panel's own quote styling.
  • A fixed iOS blue (option C): it fell below 4.5:1 against the page in six of the eight light themes probed; the theme accent passes everywhere.

What changed (motivation → approach → change)

Goal → the two speakers need two surfaces that read as "mine" and "theirs" in every one of the ~30 shipped themes, light and dark, without a per-theme table → tokens the themes already keep readable: --accent / --accent-fg (the button pair, 4.64:1 or better in every probed theme) for the user, and --bg-hover for the crewmate.

  • website/src/pages/chat/UserMessage.tsx: new tone?: 'default' | 'accent' prop. accent swaps bg-card text-card-fg for bg-accent text-accent-fg and adds the user-bubble-accent hook; the user-bubble class stays (PinnedPrompt and the theme rules key on it).
  • website/src/pages/chat/transcriptRenderers.tsx: the crewmate user entry passes tone={crewmate ? 'accent' : 'default'}; hideSteerBadge alone (no crewmate) keeps the neutral surface.
  • website/src/index.css: under .msg-content.user-bubble.user-bubble-accent the theme TOKENS are redefined for the bubble's subtree — --text / --text-strong / --card-fg = --accent-fg, --muted = 90% --accent-fg, --accent = --accent-fg (a quote bar or chip must not paint accent-on-accent), --border = 45% --accent-fg, and the surfaces --bg / --bg-elevated / --bg-hover / --card / --accent-subtle = translucent black. Utilities compile to var(--text) etc. (tailwind-theme.css, @theme inline), so inline code, link pills, the sent quote card and whatever user-message rendering gains later inherit readable colours with no per-element rule (Design review R2 suggested exactly this). The fill reads --bubble-accent, snapshotted from the outer accent on the bubble's parent via :has(>…), because a custom property declared in the rule that redefines --accent would already see the new value. Surfaces are black, not an --accent-fg mix, because a lighter patch pulls the fill toward the text colour where contrast is scarcest (white at 88% on a 14%-white card over kiro's #8e48ff measured 3.2:1); darkening moves it away. Three rules stay: Kiro dark's literal purples on code / links (no token reaches them), and the link signal — once a link's colour is the body colour it gets a solid underline, and the two link pills (.mc-md-ref-chip, LinkChip, whose bg-accent/10 + border-border/60 vanish on an accent fill of the same hue) get their label's underline back. Specificity (0,3,0) beats the kiro-light .user-bubble tint (0,2,0) and the Kiro code rules (0,2,2).
  • website/src/components/chat/crewmateBubbles.ts + index.css: BUBBLE_BASE is crewmate-bubble forced-colors:border …, no border. The .message-bubble.crewmate-bubble rule fills with the theme's --bg-hover — --bg-hover, not --bg-elevated or --card, because those equal the page background in kiro-light, highcontrast-light and everforest-light (contrast 1.00, the bubble vanishes), while --bg-hover sits at least 1.09 above the page in all 15 themes probed, the same step iMessage's gray takes (~1.17). The reply's CONTENTS paint with those same tokens (kiro-light's inline-code patch IS var(--bg-hover), as is every hover:bg-bg-hover control; cards are bg-card / bg-bg-elevated), so on a bare utility fill they would vanish (Design review R3). The rule therefore scopes --bg-hover / --bg-elevated / --card one step off the fill for its subtree (color-mix(var(--text) 6–10%, fill)), with the fill itself read from --crewmate-fill snapshotted on the parent; kiro-dark paints code with the literal #28242e (its --bg-hover), which no token reaches, so one scoped rule gives it the same step. Forced-colors mode drops fills, so a border is drawn there and only there.
  • AssistantMessage.tsx / index.css table-breakout comment: data-bordered now reads "framed bubble (a fill counts as much as a border)"; the attribute and the rule are unchanged.
  • docs/system-specs/modules/crew-mode.md: the "How it is drawn" paragraph now states the pairing, the token choice and the user-bubble-accent hook.

Measured text-on-accent contrast per theme (WCAG AA is 4.5): kiro-dark 4.64, kiro-light 4.64, solarized-light 5.15, gruvbox-light 6.12, highcontrast-light 6.62, nord-dark 10.5, dracula-dark 11.2, amber-dark 14.5.

Measured inside the accent bubble after the token redefinition (composited over the fill): quote-card excerpt on its card — kiro 4.97, everforest-light 5.31, solarized-light 5.43, gruvbox-light 6.29, highcontrast-light 6.69, nord-dark 7.39, dracula-dark 7.78, amber-dark 9.93; inline code on its patch — everforest-light 5.04, kiro 6.39, solarized-light 6.95, nord-dark 7.10, dracula-dark 7.55, gruvbox-light 8.05, highcontrast-light 8.63, amber-dark 9.64.

Backwards compatibility

Compatible: tone is optional and defaults to today's classes; no prop, type, key or row kind is renamed or removed.

Removes nothing: the change swaps utility classes on two existing elements and adds CSS; every reader of .user-bubble, .message-bubble and data-bordered still finds them.

Tests

  • website/src/test/UserMessage.accentTone.test.tsx (new): tone default keeps bg-card; accent adds bg-accent text-accent-fg user-bubble-accent and keeps user-bubble; a steer drawn with its badge keeps the steer tint over the tone; the crewmate user entry of createTranscriptRenderers turns accent on, hideSteerBadge alone does not; the index.css hook redefines every token the user-message subtree reads (--text, --muted, --accent, --border, --bg*, --card, …), snapshots the fill on the parent, darkens surfaces (--bg-hover: rgba(0,0,0,.18)), keeps the link underline and pill rules, and sits after the Kiro chip rules.
  • website/src/test/kiroLightShellHooks.test.ts: the source pin on the UserMessage class ternary now spells the tone branch too; both non-steer tones keep user-bubble leading.
  • website/src/components/chat/crewmateBubbles.test.ts: crewmateBubbleClass carries crewmate-bubble with forced-colors:border, no border, no bare bg-* fill utility. UserMessage.accentTone.test.tsx also pins the .crewmate-bubble scope (--crewmate-fill snapshot on the parent, --bg-hover / --bg-elevated / --card re-pointed off the fill, the kiro-dark literal rule).
  • website/scripts/capture-crewmate-run.mjs: the real-browser capture now compares the COMPUTED bubble colours against the theme's own tokens (--accent, --accent-fg, --bg-hover) asserts the crewmate bubble has no border and that inline code in a crewmate reply sits on a patch distinct from the fill, and — the capture page's second user message now carries a quote of the crewmate's reply — asserts the sent quote card's bar is the text colour (not accent-on-accent) and its excerpt and border derive from --accent-fg; run against the pre-change tree it fails all six colour checks (that is how the "before" frames below were taken).

Manual verification

Real-theme mockups of A / B / C across 8 themes, then the capture page on dark and light for the final tree. Not covered by a screenshot: forced-colors mode (the forced-colors:border utility is pinned by test only).

Screenshots / video

Capture page (website/capture/crewmate-run.html): a user message, a two-bubble crewmate run, a second user message carrying inline code, a URL and a quote of the crewmate's reply, a lone crewmate reply.

before (main) after
dark dark before dark after
light light before light after
Option mockups that drove the decision (A / B / C side by side, real theme tokens)

kiro-dark A/B/C
kiro-light A/B/C
amber-dark A/B/C
solarized-light A/B/C

Related Issues

Fixes #17839

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

@CrysisDeu
CrysisDeu requested a review from a team as a code owner October 7, 2026 23:24
@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 08128b08eee3d7c67653ba560e776a173d6488c5 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Check that the accent subtree is safe on surfaces this capture doesn't draw: attachments, file chips, image previews and hover controls inside the user bubble.

Suggestions

  • Redefining tokens for the bubble's subtree (--accent, --bg*, --border under .user-bubble-accent) covers every descendant implicitly. That includes ones that should keep the page's semantics, such as a destructive or warning chip that reads --accent. Add a one-line note in crew-mode.md that colours inside this bubble have to come from tokens, not literals. The kiro-dark #b07fff / #28242e special cases are the first ones that already slipped through.

[DESIGN-REVIEWED] 08128b0

Description read

[DESCRIPTION-READ] e40b6a3772eb59e08fb7c35592462c4b97986052b0dc414ce8b2124924d8ce3c

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) — ✅ PASS

Premise-level review of 08128b08eee3d7c67653ba560e776a173d6488c5 — 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: PASS

Check that #17839 records the maintainer's option-A choice. It is the only provenance for deleting the pin "Outlined, never filled… the two speakers must not share a surface."

What this change ships

Inventory (8 items) — 8 justified

Intent: in a crewmate DM, a user can tell who said what by colour (accent for the user, gray for the crewmate) instead of by alignment. This is an ADDITION.

  1. The user's bubble in a crewmate chat is filled with the theme accent and its text uses --accent-fg — justified
  2. The crewmate's bubble changed from an outlined bubble to a filled --bg-hover gray, with no border — justified
  3. Inline code, link pills, the quote card and controls inside both bubbles are recoloured so they stay visible on the new fills — justified
  4. Links inside the accent bubble get a solid underline, and link pills get their label underline back — justified
  5. In forced-colors mode the crewmate bubble draws a border — justified
  6. New UserMessage tone prop (default | accent); the single-chat page keeps default — justified
  7. The capture script now checks the computed bubble colours against each theme's tokens — justified
  8. The crew-mode spec and the data-bordered comments now describe a fill as a frame — justified

[FIRST-PRINCIPLES-REVIEWED] 08128b0

Description read

[DESCRIPTION-READ] 306020cc4e7ad15a11edf68c9142baa45064386b33a881caf4058e4cedc6df2b

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) — ✅ PASS

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

UX-Verdict: PASS

Check the shipped accent bubble with a quote card and link pill on a light non-Kiro theme. Only Kiro was captured in-product; other themes appear only on comparison sheets.

[UX-REVIEWED] 08128b0

Description read

[DESCRIPTION-READ] 39d42b455b6c6290fd16e7dec35f9e1061e755b316b4e0785293ad21cb3d7cf1

That sha256 names everything this verdict read: the PR description, plus the 11 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

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 08128b08eee3d7c67653ba560e776a173d6488c5 and found no blocking issues.

This comment is updated in place on each push.

Review details

FINDING -- website/src/components/chat/crewmateBubbles.ts:239 -- Replacing the border with crewmate-bubble leaves ThreadPanel’s assistant parent quote borderless and unfilled: its Bubble lacks .message-bubble, so the new fill selector never matches, changing explicitly excluded quote styling -> Fix: add conditional border border-border-strong variants to BUBBLE_BASE for elements without .message-bubble.
[GPT-REVIEWED] 08128b0

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

@github-actions

github-actions Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 08128b08eee3d7c67653ba560e776a173d6488c5 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 08128b0

Verdict parsed from the review's SHA-scoped output markers for commit 08128b08eee3d7c67653ba560e776a173d6488c5.

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

@CrysisDeu
CrysisDeu force-pushed the feat/crewmate-bubble-colors branch from 1ca87ba to 903b267 Compare October 7, 2026 23:59
@CrysisDeu

Copy link
Copy Markdown
Contributor Author

UX Review dispositions (R1 1ca87bad1d → R2 903b267b4d)

  • Watch: repo link pill inside the accent bubble reads as a label → FIXED. Colour was the only link cue and it is now the body colour, so the link gets a different cue: a solid underline (--accent-fg at 75%), and both link pills (.mc-md-ref-chip in MarkdownRenderer, LinkChip in LinkPreview — bg-accent/10 + border-border/60 are invisible on an accent fill of the same hue) get the inline-code patch (26% --accent-fg), a 55% --accent-fg outline and the label's underline back. Computed in the capture page on kiro-dark: pill background: rgba(255,255,255,.26), border: rgba(255,255,255,.55), text-decoration-line: underline. Pinned by UserMessage.accentTone.test.tsx (hook regexes) and the capture script's computed-colour assertions.
  • Suggestion: inline-code patch at 18% is faint → TAKEN. 26% now (color-mix(in srgb, var(--accent-fg) 26%, transparent)).

Also in R2: kiroLightShellHooks.test.ts's source pin on the UserMessage class ternary now spells the tone branch (Frontend Tests shard 3 red on R1; Coverage Gate / Frontend Coverage Merge were downstream of it). The three Backend reds on R1 (test_session_control_doc, test_http_server_bind_ratchet 16 vs 15) are main's own breakage, tracked in #17900 with fix #17847; this PR will rebase once that merges.

@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 8, 2026
@CrysisDeu
CrysisDeu force-pushed the feat/crewmate-bubble-colors branch from 903b267 to 19f1b7d Compare October 8, 2026 00:35
@CrysisDeu

Copy link
Copy Markdown
Contributor Author

Design Review dispositions (R2 903b267b4d → R3 19f1b7dde3)

  • Watch: the recolour list misses content that ships today (sent quote card, and anything added later) → FIXED, by taking the Suggestion. .user-bubble-accent now redefines the theme tokens for its subtree (--text, --text-strong, --card-fg, --muted, --accent, --accent-subtle, --border, --bg, --bg-elevated, --bg-hover, --card) and the per-element code / chip / .text-accent rules are gone; what stays is the fill (read from --bubble-accent, snapshotted on the parent via :has(>…) since --accent is re-pointed inside), the Kiro-dark literal purples on code / links that no token reaches, and the link underline + pill rules UX asked for.
    One correction to the suggestion as written: surfaces are translucent BLACK, not --accent-fg-derived. Deriving them from --accent-fg lightens the fill toward the text colour: the quote-card excerpt (muted at 88% over a 14%-white card over kiro's #8e48ff) measured 3.23:1. With black surfaces and --muted at 90%: excerpt-on-card kiro 4.97, everforest-light 5.31, solarized-light 5.43, gruvbox-light 6.29, highcontrast-light 6.69, nord 7.39, dracula 7.78, amber 9.93; code-on-patch ≥ 5.04 on the same nine themes.
    Clears when met: the capture page's second user message now quotes the crewmate's "Filed it as test: spawn approval crew-log tests take the log lock on the event loop (nightly macOS red) #16628…" reply, the dark and light after frames in the description show the card (readable excerpt, visible bar), and capture-crewmate-run.mjs asserts the bar is the text colour and the excerpt / border are --accent-fg mixes (fails on the pre-change tree).

Also in R3: rebased onto db083f5d3d — main now carries #17909 (the HTTPServer bind ratchet), so one of the two main-red test families on R1/R2 is gone; test_session_control_doc (#17900 / #17847) is still open on main.

@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 8, 2026
In a crewmate's chat both bubbles sat on the same neutral surface (the
user's filled bg-card, the crewmate's outlined), so the two speakers were
told apart by alignment alone. Zezhen chose the iMessage pairing after
real-theme screenshots of three options across eight themes (#17839):
the user's bubble filled with the theme accent, the crewmate's a neutral
gray.

User side: a `tone` prop on UserMessage; `accent` swaps the neutral
surface for bg-accent / text-accent-fg and adds the `user-bubble-accent`
hook. Under that hook index.css redefines the theme tokens for the
bubble's subtree (text and strokes as --accent-fg mixes, surfaces as
translucent black), so inline code, link pills, the sent quote card and
anything user-message rendering gains later inherit readable colours
with no per-element rule; links keep an underline as their link signal
once their colour is the body colour. The crewmate `user` entry of
createTranscriptRenderers turns it on; every other surface keeps the
default tone byte-for-byte.

Crewmate side: BUBBLE_BASE is now the `.crewmate-bubble` fill with no
border, plus a forced-colors border. The fill is --bg-hover rather than
--bg-elevated or --card because those equal the page background in
kiro-light, highcontrast-light and everforest-light (contrast 1.00, the
bubble vanishes), while --bg-hover sits at least 1.09 above the page in
every shipped theme. The reply's contents paint with the same tokens
(kiro-light's code patch IS var(--bg-hover), as is every hover:bg-bg-hover
control), so the rule scopes --bg-hover / --bg-elevated / --card one step
off the fill for its subtree. Measured text-on-accent contrast is >= 4.64
in every probed theme.

The capture script now compares the computed bubble colours against the
theme's own tokens, so the evidence fails on the pre-change tree.

Fixes #17839
@CrysisDeu
CrysisDeu force-pushed the feat/crewmate-bubble-colors branch from 19f1b7d to 08128b0 Compare October 8, 2026 01:20
@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 8, 2026
@CrysisDeu

Copy link
Copy Markdown
Contributor Author

Design Review dispositions (R3 19f1b7dde3 → R4 08128b08ee)

  • Watch: kiro-light inline code loses its patch in crewmate replies (the fill and its contents both paint --bg-hover) → FIXED. BUBBLE_BASE no longer carries a bare bg-bg-hover utility; it carries crewmate-bubble, and the .message-bubble.crewmate-bubble rule in index.css fills with --crewmate-fill (snapshotted from --bg-hover on the parent, same trick as the accent bubble) and scopes --bg-hover / --bg-elevated / --card one step off that fill for its subtree (color-mix(in srgb, var(--text) 6–10%, var(--crewmate-fill))), so kiro-light's var(--bg-hover) code patch, every hover:bg-bg-hover control and any bg-card / bg-bg-elevated card inside a reply land one step off the fill. kiro-dark paints code with the literal #28242e — which is its --bg-hover, the same vanishing — and no token reaches a literal, so one scoped [data-theme="kiro-dark"] .message-bubble.crewmate-bubble :not(pre)>code{background:var(--bg-hover)} gives it the same step.
    Clears when met: the light after frame in the description shows test_spawn_approval_crew_log in the crewmate reply on a visible patch; capture-crewmate-run.mjs now asserts the code patch's computed colour differs from the bubble fill on both themes (20/20 checks), and UserMessage.accentTone.test.tsx pins the scope rule and the kiro-dark literal rule.

Also in R4: rebased onto 1548bfb0aa. The Opus 5.5 Review lane on R3 was a 00:44Z installation rate limit (Failed to check permissions: API rate limit exceeded), not a finding; it re-runs on this head.

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Oct 8, 2026

@buluoray buluoray left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving at 08128b08ee.

What I checked in source

  • The accent tone is reachable only from the crewmate user entry (transcriptRenderers.tsx:590, tone={crewmate ? 'accent' : 'default'}). ChatPage calls createTranscriptRenderers without a crewmate, so the single-chat bubble keeps bg-card / the kiro-light --bg-hover tint. The crewmate entry always sets hideSteerBadge, so isSteer is false there and the tone branch is the one that applies.
  • The edit-mode return (UserMessage.tsx:354-400) is a separate tree with its own bg-card, so the Send button's bg-accent text-accent-fg is not inside the redefined --accent scope and does not go accent-fg on accent-fg.
  • The token redefinition holds for what renderUserContent can put inside the bubble: the knowledge badge and mention/folder chips are text-accent bg-accent/10 border-accent/25, which now resolve to --accent-fg mixes on the fill rather than accent-on-accent.
  • The fill snapshots (--bubble-accent, --crewmate-fill) are declared on the parent via :has(> …) and the rules are unlayered, so they win over the layered bg-accent / bg-card utilities on the same element.

Upgrade impact: none beyond the intended visual change in a crewmate's chat. tone is optional and defaults to today's classes; no class, attribute or prop that another reader keys on is removed.

Audience fit: scoped to the Members DM, which is what #17839 asked for; the default single-chat experience is unchanged, and forced-colors keeps a border where fills are dropped.

CI: latest run of every check on this head passes (the cancelled rows are superseded duplicates, each with a later success). I did not run the tests locally.

Non-blocking follow-up

  • The pinned-prompt banner ChatPane mounts in the Members DM still draws its own user-bubble … bg-card text-card-fg box (PinnedPrompt.tsx:741). Once a user message scrolls past the fold, the accent bubble is replaced by a neutral gray card, so the colour cue this PR adds flips at the moment of pinning. Passing the tone through to PinnedPrompt (or adding user-bubble-accent there) would keep it consistent.

@buluoray
buluoray merged commit 65e13d6 into main Oct 8, 2026
152 of 160 checks passed
@buluoray
buluoray deleted the feat/crewmate-bubble-colors branch October 8, 2026 03:06
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 8, 2026
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.

feat(crewmate-chat): iMessage-style bubble colors (user = accent, crewmate = gray)

2 participants