fix(web): address composer banner review follow-ups

[juliusmarminge]

Follow-up fixes from the review of #8734. Monitoring could hide the loading status, keyboard focus could disappear inside a notice stack, and composer controls had a few focus and pointer issues.

Open the before/after comparison page for every change, including keyboard and pointer recordings.

• Keep loading and syncing visible ahead of Monitoring.
• Keep the notice peek visibly focused until activated. Enter or Space opens the stack, and Escape returns focus to the peek.
• Leave room for question-option focus rings.
• Preserve task and stash list semantics when list markers are hidden.
• Remove the decorative chevron's extra touch hit area.
• Show distinct progress and failure icons for server updates, respecting reduced motion.
• Share the drawer inset across banners, the command menu, and the context strip.

The notice-action alignment change and enlarged touch disclosure were reverted. Items 4 and 6 in the comparison document show the original layouts restored. The compact touch peek remains.

The working timer stays in the timeline, tasks stay in the composer, loading hides tasks, and stash remains a separate tab.

Before: Monitoring hides loading	After: loading stays attached

Validation: 110 focused tests, web typecheck, targeted lint, and 36 browser checks passed. Browser checks cover keyboard focus, hover, touch expansion, pointer hit testing, responsive widths, reduced motion, and inset sizing. Web and the shared desktop UI are affected; native mobile is unchanged. Safari and VoiceOver were not exercised.

Fixtures and comparison assets are not committed.

---

Note

Low Risk
UI, accessibility, and layout-only changes; the main behavioral caveat is drawer inset computing to 0 if --chat-composer-drawer-inset is missing outside ComposerSurface.Shell.

Overview
Follow-up polish for composer banners and notices on web/desktop: loading/activity stays the attached front banner ahead of other notices (including Monitoring), and server update notices use status-specific icons (spinner, error, info) instead of a generic info icon.

Notice stack keyboard and pointer behavior is tightened in ComposerBannerStack: hover no longer auto-expands on touch; Tab/Enter/Space on Show other notices moves focus into the expanded stack; Escape collapses and returns focus to the peek control; peek is hidden from the tab order while expanded. ARIA role="group" / labels and role="list" on stash and task lists improve semantics.

Layout standardizes horizontal inset via --chat-composer-drawer-inset on the composer shell (banner width, context strip, clip-path, command-menu positioning); the command menu drops the 1.375rem JS fallback when the variable is unset. Minor UI fixes: decorative chevron pointer-events-none, padding on the pending-question panel body, and user docs for the notice stack interaction.

^{Reviewed by Cursor Bugbot for commit 5e56011. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix composer banner accessibility, focus management, and drawer inset CSS variable

• Adds keyboard focus transfer (expand/collapse), Escape to close, aria-hidden/tabIndex management, and role="group" to ComposerBannerStack; hover no longer expands on touch pointers
• Replaces static InfoIcon in the server update banner with a new ComposerServerUpdateIcon that renders a spinner for running, alert for failed, and info otherwise
• Introduces --chat-composer-drawer-inset (default 1.375rem) on ComposerSurface.Shell and uses it in ComposerBanner.Attachment width and ComposerCommandMenuLayer positioning instead of hardcoded values
• Adds role="list" to stash menu and tasks badge lists, pointer-events-none to ComposerBanner.ToggleIcon, and moves activityStackItem ahead of props.bannerItems in the stack
• Behavioral Change: ComposerCommandMenuLayer no longer falls back to 1.375 when the CSS variable is missing — callers relying on --chat-composer-drawer-inset must define it or inherit the ComposerSurface.Shell default

^{Macroscope summarized 5e56011.}

---

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c2a675ff-c719-42ad-9b79-d8c17e552d6a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−22 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−4 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−18 B (−0.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	−28 B (−0.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−9 B (−0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	−44 B (−0.1%)	66.4 KiB	✅
Claude	Live turn messages	11	10	−1 (−9.1%)	21	✅

Baseline: 30175a8 · PR result: 5e56011 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

One finding in ComposerBannerStack: the Escape handler runs even when the stack is already collapsed, which leaves a stale pending-focus request that later steals focus. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a contained web composer UI and accessibility follow-up with no schema, security, billing, or deployment impact. An unresolved comment identifies a concrete keyboard-focus and Escape-event regression in the notice stack, so the changed interaction behavior needs human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

One finding: the production composer now routes its props through a committed dev-only review fixture. Details inline.

^{Posted via Macroscope — UI Consistency}

[juliusmarminge]

Follow-up fixes from the review of #8734. Monitoring could hide the loading status, keyboard focus could disappear inside a notice stack, and composer controls had a few focus and pointer issues.

Open the before/after comparison page for every change, including keyboard and pointer recordings.

• Keep loading and syncing visible ahead of Monitoring.
• Keep the notice peek visibly focused until activated. Enter or Space opens the stack, and Escape returns focus to the peek.
• Leave room for question-option focus rings.
• Preserve task and stash list semantics when list markers are hidden.
• Remove the decorative chevron's extra touch hit area.
• Show distinct progress and failure icons for server updates, respecting reduced motion.
• Share the drawer inset across banners, the command menu, and the context strip.

The notice-action alignment change and enlarged touch disclosure were reverted. Items 4 and 6 in the comparison document show the original layouts restored. The compact touch peek remains.

The working timer stays in the timeline, tasks stay in the composer, loading hides tasks, and stash remains a separate tab.

Before: Monitoring hides loading	After: loading stays attached

Validation: 110 focused tests, web typecheck, targeted lint, and 36 browser checks passed. Browser checks cover keyboard focus, hover, touch expansion, pointer hit testing, responsive widths, reduced motion, and inset sizing. Web and the shared desktop UI are affected; native mobile is unchanged. Safari and VoiceOver were not exercised.

Fixtures and comparison assets are not committed.

---

Note

Low Risk
UI, accessibility, and layout-only changes; the main behavioral caveat is drawer inset computing to 0 if --chat-composer-drawer-inset is missing outside ComposerSurface.Shell.

Overview
Follow-up polish for composer banners and notices on web/desktop: loading/activity stays the attached front banner ahead of other notices (including Monitoring), and server update notices use status-specific icons (spinner, error, info) instead of a generic info icon.

Notice stack keyboard and pointer behavior is tightened in ComposerBannerStack: hover no longer auto-expands on touch; Tab/Enter/Space on Show other notices moves focus into the expanded stack; Escape collapses and returns focus to the peek control; peek is hidden from the tab order while expanded. ARIA role="group" / labels and role="list" on stash and task lists improve semantics.

Layout standardizes horizontal inset via --chat-composer-drawer-inset on the composer shell (banner width, context strip, clip-path, command-menu positioning); the command menu drops the 1.375rem JS fallback when the variable is unset. Minor UI fixes: decorative chevron pointer-events-none, padding on the pending-question panel body, and user docs for the notice stack interaction.

^{Reviewed by Cursor Bugbot for commit 5e56011. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix composer banner accessibility, focus management, and drawer inset CSS variable

• Adds keyboard focus transfer (expand/collapse), Escape to close, aria-hidden/tabIndex management, and role="group" to ComposerBannerStack; hover no longer expands on touch pointers
• Replaces static InfoIcon in the server update banner with a new ComposerServerUpdateIcon that renders a spinner for running, alert for failed, and info otherwise
• Introduces --chat-composer-drawer-inset (default 1.375rem) on ComposerSurface.Shell and uses it in ComposerBanner.Attachment width and ComposerCommandMenuLayer positioning instead of hardcoded values
• Adds role="list" to stash menu and tasks badge lists, pointer-events-none to ComposerBanner.ToggleIcon, and moves activityStackItem ahead of props.bannerItems in the stack
• Behavioral Change: ComposerCommandMenuLayer no longer falls back to 1.375 when the CSS variable is missing — callers relying on --chat-composer-drawer-inset must define it or inherit the ComposerSurface.Shell default

^{Macroscope summarized 5e56011.}

---

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c2a675ff-c719-42ad-9b79-d8c17e552d6a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−22 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−4 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−18 B (−0.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	−28 B (−0.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−9 B (−0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	−44 B (−0.1%)	66.4 KiB	✅
Claude	Live turn messages	11	10	−1 (−9.1%)	21	✅

Baseline: 30175a8 · PR result: 5e56011 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

One finding in ComposerBannerStack: the Escape handler runs even when the stack is already collapsed, which leaves a stale pending-focus request that later steals focus. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a contained web composer UI and accessibility follow-up with no schema, security, billing, or deployment impact. An unresolved comment identifies a concrete keyboard-focus and Escape-event regression in the notice stack, so the changed interaction behavior needs human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

One finding: the production composer now routes its props through a committed dev-only review fixture. Details inline.

^{Posted via Macroscope — UI Consistency}

[juliusmarminge]

Follow-up fixes from the review of #8734. Monitoring could hide the loading status, keyboard focus could disappear inside a notice stack, and composer controls had a few focus and pointer issues.

Open the before/after comparison page for every change, including keyboard and pointer recordings.

• Keep loading and syncing visible ahead of Monitoring.
• Keep the notice peek visibly focused until activated. Enter or Space opens the stack, and Escape returns focus to the peek.
• Leave room for question-option focus rings.
• Preserve task and stash list semantics when list markers are hidden.
• Remove the decorative chevron's extra touch hit area.
• Show distinct progress and failure icons for server updates, respecting reduced motion.
• Share the drawer inset across banners, the command menu, and the context strip.

The notice-action alignment change and enlarged touch disclosure were reverted. Items 4 and 6 in the comparison document show the original layouts restored. The compact touch peek remains.

The working timer stays in the timeline, tasks stay in the composer, loading hides tasks, and stash remains a separate tab.

Before: Monitoring hides loading	After: loading stays attached

Validation: 110 focused tests, web typecheck, targeted lint, and 36 browser checks passed. Browser checks cover keyboard focus, hover, touch expansion, pointer hit testing, responsive widths, reduced motion, and inset sizing. Web and the shared desktop UI are affected; native mobile is unchanged. Safari and VoiceOver were not exercised.

Fixtures and comparison assets are not committed.

---

Note

Low Risk
UI, accessibility, and layout-only changes; the main behavioral caveat is drawer inset computing to 0 if --chat-composer-drawer-inset is missing outside ComposerSurface.Shell.

Overview
Follow-up polish for composer banners and notices on web/desktop: loading/activity stays the attached front banner ahead of other notices (including Monitoring), and server update notices use status-specific icons (spinner, error, info) instead of a generic info icon.

Notice stack keyboard and pointer behavior is tightened in ComposerBannerStack: hover no longer auto-expands on touch; Tab/Enter/Space on Show other notices moves focus into the expanded stack; Escape collapses and returns focus to the peek control; peek is hidden from the tab order while expanded. ARIA role="group" / labels and role="list" on stash and task lists improve semantics.

Layout standardizes horizontal inset via --chat-composer-drawer-inset on the composer shell (banner width, context strip, clip-path, command-menu positioning); the command menu drops the 1.375rem JS fallback when the variable is unset. Minor UI fixes: decorative chevron pointer-events-none, padding on the pending-question panel body, and user docs for the notice stack interaction.

^{Reviewed by Cursor Bugbot for commit 5e56011. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix composer banner accessibility, focus management, and drawer inset CSS variable

• Adds keyboard focus transfer (expand/collapse), Escape to close, aria-hidden/tabIndex management, and role="group" to ComposerBannerStack; hover no longer expands on touch pointers
• Replaces static InfoIcon in the server update banner with a new ComposerServerUpdateIcon that renders a spinner for running, alert for failed, and info otherwise
• Introduces --chat-composer-drawer-inset (default 1.375rem) on ComposerSurface.Shell and uses it in ComposerBanner.Attachment width and ComposerCommandMenuLayer positioning instead of hardcoded values
• Adds role="list" to stash menu and tasks badge lists, pointer-events-none to ComposerBanner.ToggleIcon, and moves activityStackItem ahead of props.bannerItems in the stack
• Behavioral Change: ComposerCommandMenuLayer no longer falls back to 1.375 when the CSS variable is missing — callers relying on --chat-composer-drawer-inset must define it or inherit the ComposerSurface.Shell default

^{Macroscope summarized 5e56011.}

---

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c2a675ff-c719-42ad-9b79-d8c17e552d6a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−22 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−4 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−18 B (−0.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	−28 B (−0.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−9 B (−0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	−44 B (−0.1%)	66.4 KiB	✅
Claude	Live turn messages	11	10	−1 (−9.1%)	21	✅

Baseline: 30175a8 · PR result: 5e56011 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

One finding in ComposerBannerStack: the Escape handler runs even when the stack is already collapsed, which leaves a stale pending-focus request that later steals focus. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a contained web composer UI and accessibility follow-up with no schema, security, billing, or deployment impact. An unresolved comment identifies a concrete keyboard-focus and Escape-event regression in the notice stack, so the changed interaction behavior needs human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

One finding: the production composer now routes its props through a committed dev-only review fixture. Details inline.

^{Posted via Macroscope — UI Consistency}

[juliusmarminge]

Follow-up fixes from the review of #8734. Monitoring could hide the loading status, keyboard focus could disappear inside a notice stack, and composer controls had a few focus and pointer issues.

Open the before/after comparison page for every change, including keyboard and pointer recordings.

• Keep loading and syncing visible ahead of Monitoring.
• Keep the notice peek visibly focused until activated. Enter or Space opens the stack, and Escape returns focus to the peek.
• Leave room for question-option focus rings.
• Preserve task and stash list semantics when list markers are hidden.
• Remove the decorative chevron's extra touch hit area.
• Show distinct progress and failure icons for server updates, respecting reduced motion.
• Share the drawer inset across banners, the command menu, and the context strip.

The notice-action alignment change and enlarged touch disclosure were reverted. Items 4 and 6 in the comparison document show the original layouts restored. The compact touch peek remains.

The working timer stays in the timeline, tasks stay in the composer, loading hides tasks, and stash remains a separate tab.

Before: Monitoring hides loading	After: loading stays attached

Validation: 110 focused tests, web typecheck, targeted lint, and 36 browser checks passed. Browser checks cover keyboard focus, hover, touch expansion, pointer hit testing, responsive widths, reduced motion, and inset sizing. Web and the shared desktop UI are affected; native mobile is unchanged. Safari and VoiceOver were not exercised.

Fixtures and comparison assets are not committed.

---

Note

Low Risk
UI, accessibility, and layout-only changes; the main behavioral caveat is drawer inset computing to 0 if --chat-composer-drawer-inset is missing outside ComposerSurface.Shell.

Overview
Follow-up polish for composer banners and notices on web/desktop: loading/activity stays the attached front banner ahead of other notices (including Monitoring), and server update notices use status-specific icons (spinner, error, info) instead of a generic info icon.

Notice stack keyboard and pointer behavior is tightened in ComposerBannerStack: hover no longer auto-expands on touch; Tab/Enter/Space on Show other notices moves focus into the expanded stack; Escape collapses and returns focus to the peek control; peek is hidden from the tab order while expanded. ARIA role="group" / labels and role="list" on stash and task lists improve semantics.

Layout standardizes horizontal inset via --chat-composer-drawer-inset on the composer shell (banner width, context strip, clip-path, command-menu positioning); the command menu drops the 1.375rem JS fallback when the variable is unset. Minor UI fixes: decorative chevron pointer-events-none, padding on the pending-question panel body, and user docs for the notice stack interaction.

^{Reviewed by Cursor Bugbot for commit 5e56011. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix composer banner accessibility, focus management, and drawer inset CSS variable

• Adds keyboard focus transfer (expand/collapse), Escape to close, aria-hidden/tabIndex management, and role="group" to ComposerBannerStack; hover no longer expands on touch pointers
• Replaces static InfoIcon in the server update banner with a new ComposerServerUpdateIcon that renders a spinner for running, alert for failed, and info otherwise
• Introduces --chat-composer-drawer-inset (default 1.375rem) on ComposerSurface.Shell and uses it in ComposerBanner.Attachment width and ComposerCommandMenuLayer positioning instead of hardcoded values
• Adds role="list" to stash menu and tasks badge lists, pointer-events-none to ComposerBanner.ToggleIcon, and moves activityStackItem ahead of props.bannerItems in the stack
• Behavioral Change: ComposerCommandMenuLayer no longer falls back to 1.375 when the CSS variable is missing — callers relying on --chat-composer-drawer-inset must define it or inherit the ComposerSurface.Shell default

^{Macroscope summarized 5e56011.}

---

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c2a675ff-c719-42ad-9b79-d8c17e552d6a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−22 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−4 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−18 B (−0.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	−28 B (−0.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−9 B (−0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	−44 B (−0.1%)	66.4 KiB	✅
Claude	Live turn messages	11	10	−1 (−9.1%)	21	✅

Baseline: 30175a8 · PR result: 5e56011 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

One finding in ComposerBannerStack: the Escape handler runs even when the stack is already collapsed, which leaves a stale pending-focus request that later steals focus. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a contained web composer UI and accessibility follow-up with no schema, security, billing, or deployment impact. An unresolved comment identifies a concrete keyboard-focus and Escape-event regression in the notice stack, so the changed interaction behavior needs human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

One finding: the production composer now routes its props through a committed dev-only review fixture. Details inline.

^{Posted via Macroscope — UI Consistency}

[juliusmarminge]

Follow-up fixes from the review of #8734. Monitoring could hide the loading status, keyboard focus could disappear inside a notice stack, and composer controls had a few focus and pointer issues.

Open the before/after comparison page for every change, including keyboard and pointer recordings.

• Keep loading and syncing visible ahead of Monitoring.
• Keep the notice peek visibly focused until activated. Enter or Space opens the stack, and Escape returns focus to the peek.
• Leave room for question-option focus rings.
• Preserve task and stash list semantics when list markers are hidden.
• Remove the decorative chevron's extra touch hit area.
• Show distinct progress and failure icons for server updates, respecting reduced motion.
• Share the drawer inset across banners, the command menu, and the context strip.

The notice-action alignment change and enlarged touch disclosure were reverted. Items 4 and 6 in the comparison document show the original layouts restored. The compact touch peek remains.

The working timer stays in the timeline, tasks stay in the composer, loading hides tasks, and stash remains a separate tab.

Before: Monitoring hides loading	After: loading stays attached

Validation: 110 focused tests, web typecheck, targeted lint, and 36 browser checks passed. Browser checks cover keyboard focus, hover, touch expansion, pointer hit testing, responsive widths, reduced motion, and inset sizing. Web and the shared desktop UI are affected; native mobile is unchanged. Safari and VoiceOver were not exercised.

Fixtures and comparison assets are not committed.

---

Note

Low Risk
UI, accessibility, and layout-only changes; the main behavioral caveat is drawer inset computing to 0 if --chat-composer-drawer-inset is missing outside ComposerSurface.Shell.

Overview
Follow-up polish for composer banners and notices on web/desktop: loading/activity stays the attached front banner ahead of other notices (including Monitoring), and server update notices use status-specific icons (spinner, error, info) instead of a generic info icon.

Notice stack keyboard and pointer behavior is tightened in ComposerBannerStack: hover no longer auto-expands on touch; Tab/Enter/Space on Show other notices moves focus into the expanded stack; Escape collapses and returns focus to the peek control; peek is hidden from the tab order while expanded. ARIA role="group" / labels and role="list" on stash and task lists improve semantics.

Layout standardizes horizontal inset via --chat-composer-drawer-inset on the composer shell (banner width, context strip, clip-path, command-menu positioning); the command menu drops the 1.375rem JS fallback when the variable is unset. Minor UI fixes: decorative chevron pointer-events-none, padding on the pending-question panel body, and user docs for the notice stack interaction.

^{Reviewed by Cursor Bugbot for commit 5e56011. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix composer banner accessibility, focus management, and drawer inset CSS variable

• Adds keyboard focus transfer (expand/collapse), Escape to close, aria-hidden/tabIndex management, and role="group" to ComposerBannerStack; hover no longer expands on touch pointers
• Replaces static InfoIcon in the server update banner with a new ComposerServerUpdateIcon that renders a spinner for running, alert for failed, and info otherwise
• Introduces --chat-composer-drawer-inset (default 1.375rem) on ComposerSurface.Shell and uses it in ComposerBanner.Attachment width and ComposerCommandMenuLayer positioning instead of hardcoded values
• Adds role="list" to stash menu and tasks badge lists, pointer-events-none to ComposerBanner.ToggleIcon, and moves activityStackItem ahead of props.bannerItems in the stack
• Behavioral Change: ComposerCommandMenuLayer no longer falls back to 1.375 when the CSS variable is missing — callers relying on --chat-composer-drawer-inset must define it or inherit the ComposerSurface.Shell default

^{Macroscope summarized 5e56011.}

---

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c2a675ff-c719-42ad-9b79-d8c17e552d6a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−22 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−4 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−18 B (−0.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	−28 B (−0.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−9 B (−0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	−44 B (−0.1%)	66.4 KiB	✅
Claude	Live turn messages	11	10	−1 (−9.1%)	21	✅

Baseline: 30175a8 · PR result: 5e56011 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

One finding in ComposerBannerStack: the Escape handler runs even when the stack is already collapsed, which leaves a stale pending-focus request that later steals focus. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a contained web composer UI and accessibility follow-up with no schema, security, billing, or deployment impact. An unresolved comment identifies a concrete keyboard-focus and Escape-event regression in the notice stack, so the changed interaction behavior needs human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

One finding: the production composer now routes its props through a committed dev-only review fixture. Details inline.

^{Posted via Macroscope — UI Consistency}

[juliusmarminge]

Follow-up fixes from the review of #8734. Monitoring could hide the loading status, keyboard focus could disappear inside a notice stack, and composer controls had a few focus and pointer issues.

Open the before/after comparison page for every change, including keyboard and pointer recordings.

• Keep loading and syncing visible ahead of Monitoring.
• Keep the notice peek visibly focused until activated. Enter or Space opens the stack, and Escape returns focus to the peek.
• Leave room for question-option focus rings.
• Preserve task and stash list semantics when list markers are hidden.
• Remove the decorative chevron's extra touch hit area.
• Show distinct progress and failure icons for server updates, respecting reduced motion.
• Share the drawer inset across banners, the command menu, and the context strip.

The notice-action alignment change and enlarged touch disclosure were reverted. Items 4 and 6 in the comparison document show the original layouts restored. The compact touch peek remains.

The working timer stays in the timeline, tasks stay in the composer, loading hides tasks, and stash remains a separate tab.

Before: Monitoring hides loading	After: loading stays attached

Validation: 110 focused tests, web typecheck, targeted lint, and 36 browser checks passed. Browser checks cover keyboard focus, hover, touch expansion, pointer hit testing, responsive widths, reduced motion, and inset sizing. Web and the shared desktop UI are affected; native mobile is unchanged. Safari and VoiceOver were not exercised.

Fixtures and comparison assets are not committed.

---

Note

Low Risk
UI, accessibility, and layout-only changes; the main behavioral caveat is drawer inset computing to 0 if --chat-composer-drawer-inset is missing outside ComposerSurface.Shell.

Overview
Follow-up polish for composer banners and notices on web/desktop: loading/activity stays the attached front banner ahead of other notices (including Monitoring), and server update notices use status-specific icons (spinner, error, info) instead of a generic info icon.

Notice stack keyboard and pointer behavior is tightened in ComposerBannerStack: hover no longer auto-expands on touch; Tab/Enter/Space on Show other notices moves focus into the expanded stack; Escape collapses and returns focus to the peek control; peek is hidden from the tab order while expanded. ARIA role="group" / labels and role="list" on stash and task lists improve semantics.

Layout standardizes horizontal inset via --chat-composer-drawer-inset on the composer shell (banner width, context strip, clip-path, command-menu positioning); the command menu drops the 1.375rem JS fallback when the variable is unset. Minor UI fixes: decorative chevron pointer-events-none, padding on the pending-question panel body, and user docs for the notice stack interaction.

^{Reviewed by Cursor Bugbot for commit 5e56011. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix composer banner accessibility, focus management, and drawer inset CSS variable

• Adds keyboard focus transfer (expand/collapse), Escape to close, aria-hidden/tabIndex management, and role="group" to ComposerBannerStack; hover no longer expands on touch pointers
• Replaces static InfoIcon in the server update banner with a new ComposerServerUpdateIcon that renders a spinner for running, alert for failed, and info otherwise
• Introduces --chat-composer-drawer-inset (default 1.375rem) on ComposerSurface.Shell and uses it in ComposerBanner.Attachment width and ComposerCommandMenuLayer positioning instead of hardcoded values
• Adds role="list" to stash menu and tasks badge lists, pointer-events-none to ComposerBanner.ToggleIcon, and moves activityStackItem ahead of props.bannerItems in the stack
• Behavioral Change: ComposerCommandMenuLayer no longer falls back to 1.375 when the CSS variable is missing — callers relying on --chat-composer-drawer-inset must define it or inherit the ComposerSurface.Shell default

^{Macroscope summarized 5e56011.}

---

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c2a675ff-c719-42ad-9b79-d8c17e552d6a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−22 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−4 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−18 B (−0.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	−28 B (−0.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−9 B (−0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	−44 B (−0.1%)	66.4 KiB	✅
Claude	Live turn messages	11	10	−1 (−9.1%)	21	✅

Baseline: 30175a8 · PR result: 5e56011 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

One finding in ComposerBannerStack: the Escape handler runs even when the stack is already collapsed, which leaves a stale pending-focus request that later steals focus. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a contained web composer UI and accessibility follow-up with no schema, security, billing, or deployment impact. An unresolved comment identifies a concrete keyboard-focus and Escape-event regression in the notice stack, so the changed interaction behavior needs human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

One finding: the production composer now routes its props through a committed dev-only review fixture. Details inline.

^{Posted via Macroscope — UI Consistency}

[juliusmarminge]

Follow-up fixes from the review of #8734. Monitoring could hide the loading status, keyboard focus could disappear inside a notice stack, and composer controls had a few focus and pointer issues.

Open the before/after comparison page for every change, including keyboard and pointer recordings.

• Keep loading and syncing visible ahead of Monitoring.
• Keep the notice peek visibly focused until activated. Enter or Space opens the stack, and Escape returns focus to the peek.
• Leave room for question-option focus rings.
• Preserve task and stash list semantics when list markers are hidden.
• Remove the decorative chevron's extra touch hit area.
• Show distinct progress and failure icons for server updates, respecting reduced motion.
• Share the drawer inset across banners, the command menu, and the context strip.

The notice-action alignment change and enlarged touch disclosure were reverted. Items 4 and 6 in the comparison document show the original layouts restored. The compact touch peek remains.

The working timer stays in the timeline, tasks stay in the composer, loading hides tasks, and stash remains a separate tab.

Before: Monitoring hides loading	After: loading stays attached

Validation: 110 focused tests, web typecheck, targeted lint, and 36 browser checks passed. Browser checks cover keyboard focus, hover, touch expansion, pointer hit testing, responsive widths, reduced motion, and inset sizing. Web and the shared desktop UI are affected; native mobile is unchanged. Safari and VoiceOver were not exercised.

Fixtures and comparison assets are not committed.

---

Note

Low Risk
UI, accessibility, and layout-only changes; the main behavioral caveat is drawer inset computing to 0 if --chat-composer-drawer-inset is missing outside ComposerSurface.Shell.

Overview
Follow-up polish for composer banners and notices on web/desktop: loading/activity stays the attached front banner ahead of other notices (including Monitoring), and server update notices use status-specific icons (spinner, error, info) instead of a generic info icon.

Notice stack keyboard and pointer behavior is tightened in ComposerBannerStack: hover no longer auto-expands on touch; Tab/Enter/Space on Show other notices moves focus into the expanded stack; Escape collapses and returns focus to the peek control; peek is hidden from the tab order while expanded. ARIA role="group" / labels and role="list" on stash and task lists improve semantics.

Layout standardizes horizontal inset via --chat-composer-drawer-inset on the composer shell (banner width, context strip, clip-path, command-menu positioning); the command menu drops the 1.375rem JS fallback when the variable is unset. Minor UI fixes: decorative chevron pointer-events-none, padding on the pending-question panel body, and user docs for the notice stack interaction.

^{Reviewed by Cursor Bugbot for commit 5e56011. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix composer banner accessibility, focus management, and drawer inset CSS variable

• Adds keyboard focus transfer (expand/collapse), Escape to close, aria-hidden/tabIndex management, and role="group" to ComposerBannerStack; hover no longer expands on touch pointers
• Replaces static InfoIcon in the server update banner with a new ComposerServerUpdateIcon that renders a spinner for running, alert for failed, and info otherwise
• Introduces --chat-composer-drawer-inset (default 1.375rem) on ComposerSurface.Shell and uses it in ComposerBanner.Attachment width and ComposerCommandMenuLayer positioning instead of hardcoded values
• Adds role="list" to stash menu and tasks badge lists, pointer-events-none to ComposerBanner.ToggleIcon, and moves activityStackItem ahead of props.bannerItems in the stack
• Behavioral Change: ComposerCommandMenuLayer no longer falls back to 1.375 when the CSS variable is missing — callers relying on --chat-composer-drawer-inset must define it or inherit the ComposerSurface.Shell default

^{Macroscope summarized 5e56011.}

---

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c2a675ff-c719-42ad-9b79-d8c17e552d6a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−22 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−4 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−18 B (−0.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	−28 B (−0.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−9 B (−0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	−44 B (−0.1%)	66.4 KiB	✅
Claude	Live turn messages	11	10	−1 (−9.1%)	21	✅

Baseline: 30175a8 · PR result: 5e56011 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

One finding in ComposerBannerStack: the Escape handler runs even when the stack is already collapsed, which leaves a stale pending-focus request that later steals focus. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a contained web composer UI and accessibility follow-up with no schema, security, billing, or deployment impact. An unresolved comment identifies a concrete keyboard-focus and Escape-event regression in the notice stack, so the changed interaction behavior needs human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

One finding: the production composer now routes its props through a committed dev-only review fixture. Details inline.

^{Posted via Macroscope — UI Consistency}

[juliusmarminge]

Follow-up fixes from the review of #8734. Monitoring could hide the loading status, keyboard focus could disappear inside a notice stack, and composer controls had a few focus and pointer issues.

Open the before/after comparison page for every change, including keyboard and pointer recordings.

• Keep loading and syncing visible ahead of Monitoring.
• Keep the notice peek visibly focused until activated. Enter or Space opens the stack, and Escape returns focus to the peek.
• Leave room for question-option focus rings.
• Preserve task and stash list semantics when list markers are hidden.
• Remove the decorative chevron's extra touch hit area.
• Show distinct progress and failure icons for server updates, respecting reduced motion.
• Share the drawer inset across banners, the command menu, and the context strip.

The notice-action alignment change and enlarged touch disclosure were reverted. Items 4 and 6 in the comparison document show the original layouts restored. The compact touch peek remains.

The working timer stays in the timeline, tasks stay in the composer, loading hides tasks, and stash remains a separate tab.

Before: Monitoring hides loading	After: loading stays attached

Validation: 110 focused tests, web typecheck, targeted lint, and 36 browser checks passed. Browser checks cover keyboard focus, hover, touch expansion, pointer hit testing, responsive widths, reduced motion, and inset sizing. Web and the shared desktop UI are affected; native mobile is unchanged. Safari and VoiceOver were not exercised.

Fixtures and comparison assets are not committed.

---

Note

Low Risk
UI, accessibility, and layout-only changes; the main behavioral caveat is drawer inset computing to 0 if --chat-composer-drawer-inset is missing outside ComposerSurface.Shell.

Overview
Follow-up polish for composer banners and notices on web/desktop: loading/activity stays the attached front banner ahead of other notices (including Monitoring), and server update notices use status-specific icons (spinner, error, info) instead of a generic info icon.

Notice stack keyboard and pointer behavior is tightened in ComposerBannerStack: hover no longer auto-expands on touch; Tab/Enter/Space on Show other notices moves focus into the expanded stack; Escape collapses and returns focus to the peek control; peek is hidden from the tab order while expanded. ARIA role="group" / labels and role="list" on stash and task lists improve semantics.

Layout standardizes horizontal inset via --chat-composer-drawer-inset on the composer shell (banner width, context strip, clip-path, command-menu positioning); the command menu drops the 1.375rem JS fallback when the variable is unset. Minor UI fixes: decorative chevron pointer-events-none, padding on the pending-question panel body, and user docs for the notice stack interaction.

^{Reviewed by Cursor Bugbot for commit 5e56011. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix composer banner accessibility, focus management, and drawer inset CSS variable

• Adds keyboard focus transfer (expand/collapse), Escape to close, aria-hidden/tabIndex management, and role="group" to ComposerBannerStack; hover no longer expands on touch pointers
• Replaces static InfoIcon in the server update banner with a new ComposerServerUpdateIcon that renders a spinner for running, alert for failed, and info otherwise
• Introduces --chat-composer-drawer-inset (default 1.375rem) on ComposerSurface.Shell and uses it in ComposerBanner.Attachment width and ComposerCommandMenuLayer positioning instead of hardcoded values
• Adds role="list" to stash menu and tasks badge lists, pointer-events-none to ComposerBanner.ToggleIcon, and moves activityStackItem ahead of props.bannerItems in the stack
• Behavioral Change: ComposerCommandMenuLayer no longer falls back to 1.375 when the CSS variable is missing — callers relying on --chat-composer-drawer-inset must define it or inherit the ComposerSurface.Shell default

^{Macroscope summarized 5e56011.}

---

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c2a675ff-c719-42ad-9b79-d8c17e552d6a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−22 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−4 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−18 B (−0.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	−28 B (−0.2%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−9 B (−0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	−44 B (−0.1%)	66.4 KiB	✅
Claude	Live turn messages	11	10	−1 (−9.1%)	21	✅

Baseline: 30175a8 · PR result: 5e56011 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

One finding in ComposerBannerStack: the Escape handler runs even when the stack is already collapsed, which leaves a stale pending-focus request that later steals focus. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a contained web composer UI and accessibility follow-up with no schema, security, billing, or deployment impact. An unresolved comment identifies a concrete keyboard-focus and Escape-event regression in the notice stack, so the changed interaction behavior needs human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

One finding: the production composer now routes its props through a committed dev-only review fixture. Details inline.

^{Posted via Macroscope — UI Consistency}