fix(web): restore unified activity logs and composer banners

[t3dotgg]

Restores the activity log grouping and shared composer banners from #8693 after #8733, while deferring the composer-attached working timer.

Working for keeps main's placement in the conversation timeline, including the current task label, Thinking state, and turn lifecycle. Long task labels truncate to one line while the timer remains fully visible. The composer keeps the restored task controls, notice stacking, and shared Tailwind components. Task progress appears only in the composer; the duplicate timeline checklist is removed. Plan proposals remain in the timeline. Stash stays in its own tab beside notices and expanded task lists, including compact layouts; its footer variant is removed. Loading and syncing use the shared banner stack and hide task controls until the thread is up to date. Their spinner respects reduced-motion preferences.

Rebased onto current main, including interim response folding and the latest failed-tool icon fix. Orchestrator V2 and queueing are deferred until this main-targeted PR is merged.

All after screenshots below were recaptured from 35e6b6653e95. The timeline comparisons render the same scripted events through the actual timeline components from the PR base, 8b817cbcaad7, and the current PR. Each pair uses matching viewport dimensions. Completed-turn folds are open in both versions; the mixed activity group is shown both collapsed and expanded. The composer comparisons retain their earlier-iteration before images, labelled separately.

Mixed command, file-read, and status entries now get one useful summary. Main already summarized tool-only groups; the improvement here is that mixed groups use that presentation too.

PR base: last command and hidden log entries	Current PR: summary of the whole group

Expanding that same group keeps the summary and shows compact detail rows, without separate Work Log headings.

PR base: expanded mixed log	Current PR: expanded activity group

Task updates no longer add Plan updated rows or a second checklist to the timeline. Commands stay in one group; task controls remain in the composer.

PR base: plan chatter and timeline checklist	Current PR: one command group, no duplicate tasks

The earlier error screenshot incorrectly modeled a failed test as a runtime error. These two corrected scenarios use the server's actual event conversion and payload projection.

Failed command followed by a successful retry — unchanged. A test exits with code 1, the fixture is edited, and the test reruns successfully. All three tool calls stay in one group on both the PR base and this branch. A nonzero command exit code does not split the group, and no failure-count prefix is added.

PR base: failed test and retry in one group	Current PR: same grouping

Expanding the group and failed command reveals the failure output in both versions:

PR base: failed command details	Current PR: same failure details

Provider crash at the end of a run. Two commands finish, then the provider exits unexpectedly and the turn ends. There are no commands continuing after the crash in this fixture. The base already shows the terminal runtime error; this PR gives the preceding commands their own summary and renders the error as a separate row.

PR base: terminal error with previous tool calls	Current PR: command summary followed by runtime error

The outer Worked for fold is open in every comparison. Collapsing that fold can still hide the error. The grouping boundary applies to error events, such as runtime failures, rather than ordinary failed tool results. This update corrects the evidence; it does not change production behavior.

The initial restore passed 242 focused web tests, web typecheck, and targeted lint. Checked the isolated fixture playground in the browser, including running/idle turns, task expansion, loading/syncing, notices, approvals, and stash. Stopping a turn removes the timer; deleting the last stashed prompt closes the stash. Preview fixtures remain local and are not part of the PR.

Earlier restore: attached timer	Current PR: timeline timer, tasks only in composer

Long task labels checked at 1440px and 768px viewport widths. Targeted lint and web typecheck pass.

PR base: wrapping task label	Current PR: single-line task label

Loading and syncing now keep the combined banner behavior: the status stays attached, notices peek behind it, and task controls stay hidden until the thread is up to date. Stash keeps its separate tab. Verified loading and syncing with and without tasks, notice expansion, narrow layouts, and reduced motion. All 64 focused tests, web typecheck, and targeted lint passed.

Earlier iteration: separate status row, tasks visible	Current PR: combined banner, tasks hidden

Narrow layout · Spinner recording

The stash placement update passed 61 focused tests, web typecheck, and targeted lint. Browser checks covered notices, expanded tasks, notice stacks, loading, narrow questions, compact-composer expansion, restoring a prompt, deleting the last entry, and the empty composer. This changes the shared web/desktop composer; native clients are unchanged.

Earlier iteration: stash in footer	Current PR: separate stash tab

With Stash closed, its tab stays beside the update notice:

Opening Stash shows the saved drafts in a drawer across the top of the composer, covering the notice underneath. Closing Stash reveals the notice again:

Expanded tasks keep their own panel beside Stash:

The task-list cleanup passed 218 focused tests, web typecheck, and targeted lint. Browser checks covered composer task expansion/collapse, command-group expansion, and completed turns. The working timer is unchanged. This uses the shared web/desktop timeline; native clients, providers, and wire contracts are unchanged.

Earlier restore: duplicate task checklist	Current PR: tasks only in the composer

The composer task list still expands beside Stash:

Note

Restore unified activity logs and rebuild composer banner system

• Removes turn-plan timeline rows and the MAX_VISIBLE_WORK_LOG_ENTRIES cap/overflow toggle, so work log entries are always shown in unified activity groups instead of being collapsed behind '+N previous …'
• Introduces a new update action type in ToolGroupAction for non-tool entries, with standalone rows for agent spawns and error-toned entries that bypass grouping
• Replaces ad-hoc composer layout with a new ComposerBanner, ComposerBannerStack, and ComposerSurface primitive system; tasks, stash, pending approvals, and server update notices all render through these shared components
• Integrates tasks progress into the banner stack (no longer dismissible per-turn) and adds a ComposerServerUpdateStatus component with dismissal support for failed update states
• Risk: ChatComposerProps replaces externalDrawerAttached with bannerItems and adds threadSyncPhase; ComposerStashBadge removes the placement prop; ComposerTasksBadge removes onDismiss and hasTrailingShoulder; deriveTurnPlans is deleted and deriveTimelineEntries no longer accepts turn plans — any out-of-tree callers of these APIs will break

^{Macroscope summarized cfb3851.}

---

Note

Medium Risk
Large, user-facing composer and timeline refactor with prop/API removals (externalDrawerAttached, task dismiss, turn plans); behavior changes for notices, sync, and work-log grouping are easy to miss in edge cases.

Overview
Restores unified timeline activity grouping and rebuilds the chat composer around shared ComposerSurface / ComposerBanner primitives.

Work log rendering drops the per-group visibility cap and turn-plan timeline rows. Mixed runs collapse into one expandable summary (including non-tool updates), while agent spawns and error-toned entries stay standalone. deriveTimelineEntries no longer takes turn plans.

Composer notices, thread sync, task progress, stash, approvals, and command/stash drawers all attach through ComposerBannerStack with explicit priority (activity / urgent / notice) instead of manual urgent/calm splits in ChatView. Banners move from above the glass shell into ChatComposer via bannerItems; threadSyncPhase suppresses task UI until sync finishes and can show ComposerActivityRow in the stack. Task progress is derived from the current turn’sactivePlan (not sidebar planProgress); per-turn task dismiss is removed. Stash is a shoulder tab only (no inline/footer variant). Server-update banners use ComposerServerUpdateStatus and can dismiss failed updates. shoulderTabReserve and the extra overlay mutation observer are removed—scroll clearance uses full composer height. BranchToolbar uses ComposerSurface.ContextStrip.

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

[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: f3a66e84-043e-4bc3-b47b-654eccf47321

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	+9 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−5 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	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.4 KiB	13.3 KiB	−16 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 8b817cb · PR result: 35e6b66 · 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]

UI consistency review found 2 issues in the new composer banner primitives. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The removed CollapsiblePanel className="px-3 sm:px-4" carried a comment explaining that the panel clips its content while the height animates, so the option buttons have to sit inside that padding or their focus rings get shaved. ComposerBanner.Body only supplies padding-inline-start, so the w-full option buttons now touch the panel's inline-end and block-end edges and their focus-visible:ring-1 is clipped by overflow-hidden. Restoring end/bottom padding inside the clipped box keeps the ring visible.

Suggested change

	<ComposerBanner.Body>
	<ComposerBanner.BodyclassName="pb-1 pe-1">

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This XXL change replaces shared composer and timeline behavior across many production paths, including notice stacking, task and sync visibility, activity grouping, and layout measurement. Several unresolved findings also identify interaction, accessibility, loading-state, and test-coverage regressions that require focused human review.

Not approved because:

• 3 blocking correctness issues found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[CDVolvik]

Verified fix(web): restore unified activity logs and composer banners at 39283f4 as CDVolvik.

Restores #8693 after #8733 revert — git diff 33 files +1506/-2094 identical to original. Activity logs: MessagesTimeline working row removed, work entries grouped contiguously, ChatView active task progress tied to activePlan of current turn, ChatComposer exposes bannerItems/isWorking. Composer banners: ComposerSurface/Banner primitives, priority activity<urgent<notice, custom tasks content, accessible peek. Tests: MessagesTimeline.logic+session-logic+versionSkew+ChatView.logic 194/194, MessagesTimeline 37/37 pass. Note per PR: Compact/dismiss alignment and banner padding not fixed yet — author defers to Julius — hold merge until follow-up. Otherwise LGTM, no push.

[macroscopeapp]

🟡 Mediumchat/ComposerBanner.tsx:94

When the notice stack is expanded, the Peek button remains pointer-interactive and keyboard-focusable despite receiving opacity-0, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply pointer-events-none and disabled (or omit it from the DOM) while the stack is expanded.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ComposerBanner.tsx around line 94:
When the notice stack is expanded, the `Peek` button remains pointer-interactive and keyboard-focusable despite receiving `opacity-0`, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply `pointer-events-none` and `disabled` (or omit it from the DOM) while the stack is expanded.

[macroscopeapp]

🟡 Mediumchat/ChatComposer.tsx:3602

ComposerTasksBadge and ComposerTasksDrawer no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.

Also found in 2 other location(s)

apps/web/src/components/chat/ComposerTasksBadge.tsx:112

ComposerTasksBadge no longer accepts or renders an onDismiss action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.

apps/web/src/components/chat/ComposerTasksBadge.tsx:232

ComposerTasksDrawer no longer accepts or renders the former onDismiss action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed dismissTasks to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ChatComposer.tsx around line 3602:
`ComposerTasksBadge` and `ComposerTasksDrawer` no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.
Also found in 2 other location(s):
- apps/web/src/components/chat/ComposerTasksBadge.tsx:112 -- `ComposerTasksBadge` no longer accepts or renders an `onDismiss` action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.
- apps/web/src/components/chat/ComposerTasksBadge.tsx:232 -- `ComposerTasksDrawer` no longer accepts or renders the former `onDismiss` action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed `dismissTasks` to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

[macroscopeapp]

UI consistency review of the restored composer banner/surface system. Three findings below; the two findings posted on the previous head (ComposerBanner.ToggleIcon inheriting the coarse-pointer hit-target pseudo-element, and ComposerBanner.Body losing the clipped panel's end/bottom padding) are still open on this head and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Notices with a description now bind both the icon and the action/dismiss controls to the titleRow, with the description rendered as a separate row underneath (ComposerBanner.Children). That reproduces the alignment regression this PR's description acknowledges as the reason #8693 was reverted: Compact / dismiss sit on the title line instead of being centered against the whole title + description block.

The primitive it replaced did this in one row: Alert (controlAlignment: "center") lays out icon | title+description column | actions in a single items-center flex row, so the controls center against the full block and only opt into first-line alignment explicitly.

Smallest fix: keep the description inside the same Row's ComposerBanner.Content (stacked, e.g. className="flex-col items-start gap-0.5" with the title span keeping font-medium) and reserve ComposerBanner.Children for item.children, so the row's items-center centers the icon and actions over both lines. The other half of the revert — banner edge padding, now p-1 on ComposerBanner.Root versus the old px-3 pt-2 sm:px-4 — belongs on Root rather than at each call site.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Attachment hardcodes the drawer inset (w-[calc(100%-2.75rem)], max-w-[45.25rem]), while this PR deletes the only declaration of --chat-composer-drawer-inset: 1.375rem from index.css. That variable still has an imperative consumer: ComposerCommandMenuLayer reads it with getComputedStyle(form ?? anchor).getPropertyValue("--chat-composer-drawer-inset") (ChatComposer.tsx:233) to compute the command menu's left and width. The read now always resolves to "" and silently takes the || 1.375 fallback, so the menu lines up only because 2.75rem happens to be twice that fallback, and the two owners will drift the next time this width changes.

Suggest keeping one owner: declare [--chat-composer-drawer-inset:1.375rem] on an ancestor the composer form inherits from (ComposerSurface.Shell) and derive the widths here from it, e.g. w-[calc(100%-2*var(--chat-composer-drawer-inset))] max-w-[calc(48rem-2*var(--chat-composer-drawer-inset))].

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This test was dropped when the working row left the timeline, but the follow-up commit restored WorkingTimelineRow/ThinkingActivityRow and the activeTurnStartedAt prop, and LiveActivityContent still emits gap-1.5 py-0.5 px-1 for the iconless variant — so the assertions still hold and the restored row is now unguarded, right as this PR reworks neighbouring row indentation (TurnPlanTimelineRow's chevron column and pl-6 → pl-8). Suggest restoring it as-is.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration at fe1774e. One new finding below (list semantics lost in the tasks/stash list migration). The findings from my earlier reviews on this PR are still open and are not reposted here:

• ComposerBannerStack.tsx — description notices bind icon/actions to the title row, so Compact/dismiss no longer center against the title + description block.
• ComposerBanner.tsxAttachment — hardcoded inset while --chat-composer-drawer-inset is deleted from index.css, leaving ComposerCommandMenuLayer's getPropertyValue read resolving to "".
• ComposerBanner.tsxToggleIcon — decorative aria-hidden span inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 hit overlay inside Row render={<button/>}.
• ComposerPendingUserInputPanel.tsx — ComposerBanner.Body supplies only inline-start padding, so option-button focus rings are clipped by the animating CollapsiblePanel.
• MessagesTimeline.test.tsx — the iconless Thinking/working-timer alignment test is still dropped while the row it covered is restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The task list loses its list semantics in this migration: the old drawer rendered role="list" + role="listitem" explicitly (the deleted ComposerTasksBadge.test.tsx asserted both), while this <ul> relies on implicit roles. Tailwind's preflight sets list-style: none on ul, which makes WebKit drop the list role — and with it the aria-label on this container, since a generic element's label is not announced. Suggest re-asserting the role on the container (the li children keep listitem once the list role is explicit). ComposerStashMenu.tsx:133 has the same shape (render={<ul />} with aria-label="Stashed prompts") and needs the same fix.

Suggested change

	>
	render={<ulrole="list"/>}

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c0d3d53. Configure here.}

[macroscopeapp]

Reviewed the two new commits (c0d3d53 restoring the sync status, 4977016 moving the stash tab into the banner dock) plus the surrounding banner/surface migration.

One new finding on the restored ThreadSyncStatusPill (inline). The findings from earlier runs on this PR still apply at 4977016 and are not repeated here:

• ComposerBanner.ToggleIcon inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 overlay on a decorative span.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus-visible ring is clipped by the collapsible panel's overflow-hidden (ComposerPendingUserInputPanel.tsx:203-262).
• ComposerBannerStackAlert binds actions/dismiss to the title row while the description renders as a separate row, so controls are no longer centered against the title + description block.
• The tasks list (ComposerBanner.Children render={<ul />}) relies on implicit list semantics, which Tailwind preflight's list-style: none drops in WebKit along with the container aria-label.
• apps/web/src/components/chat/MessagesTimeline.test.tsx still drops the working/thinking row assertions even though WorkingTimelineRow was restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

🟡 Mediumcomponents/ChatView.tsx:4556

activeComposerTasksProgress returns null while thread details are loading because it now derives entirely from activePlan, which reads threadActivities — but buildLoadingThreadFromShell forces activities: [] during the loading window. The previous code fell back to activeThreadShell?.planProgress, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.

Consider falling back to activeThreadShell?.planProgress when activePlan is null and the thread is still loading, so the shell-level progress remains visible during that window.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/ChatView.tsx around line 4556:
`activeComposerTasksProgress` returns `null` while thread details are loading because it now derives entirely from `activePlan`, which reads `threadActivities` — but `buildLoadingThreadFromShell` forces `activities: []` during the loading window. The previous code fell back to `activeThreadShell?.planProgress`, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.
Consider falling back to `activeThreadShell?.planProgress` when `activePlan` is `null` and the thread is still loading, so the shell-level progress remains visible during that window.

[macroscopeapp]

One new finding in this push's neighbourhood: the composer server-update notice lost the live/failure indicator that ServerUpdateProgress used to own, and now shows a static InfoIcon even in the error variant. Previously reported findings on the earlier commits (banner Attachment inset vs. the deleted --chat-composer-drawer-inset, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body end/bottom padding, notice description/action alignment, ThreadSyncStatusPill bypassing the banner row grid, task-list role="list", and the dropped working-row alignment test) still apply and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This notice now uses a static InfoIcon for all three states, which drops the only live cue for a running update and puts an info icon on an error-variant banner. The removed code explained why: ServerUpdateProgress carried a pulsing dot while running and a destructive dot on failure, and only the idle offer needed an icon. ComposerServerUpdateStatus renders text only, so the pulse is gone and the failed row reads as informational next to the sibling notices that do pick situational icons (WifiOffIcon, AlarmClockIcon, GitBranchIcon) and a pulsing dot for live states.

Suggest keeping InfoIcon for the idle offer and restoring the dots for the other two states (ComposerBanner.Dot exists for exactly this and currently has no consumer, if you prefer routing it through the primitive):

Suggested change

	icon: <InfoIconaria-hidden/>,
	icon: updateInProgress ? (
	<span
	className="size-1.5 animate-status-pulse rounded-full bg-foreground"
	aria-hidden="true"
	/>
	) : updateFailed ? (
	<spanclassName="size-1.5 rounded-full bg-destructive"aria-hidden="true"/>
	) : (
	<InfoIconaria-hidden/>
	),

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration again against the new commit (53c1702, "restore combined loading and syncing banners").

The sync status now composes ComposerBanner.Row / Icon / Content (ComposerActivityStatus.tsx), which resolves the icon-column misalignment flagged on 4977016. One new finding below on the verification gate for the primitives this PR introduces.

Findings raised on earlier commits that are still present at this head (not re-posted):

• ComposerBanner.ToggleIcon inherits the full buttonVariants base, including the pointer-coarse 44x44 ::after hit box, inside rows that are themselves buttons.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus rings are clipped by the animating CollapsiblePanel.
• The task list relies on implicit ul/li roles after Preflight's list-style: none, dropping the list role and its aria-label in WebKit.
• Notice descriptions render as a second row, so actions/dismiss align to the title line instead of the whole block.
• ComposerCommandMenuLayer still reads --chat-composer-drawer-inset, whose only declaration this PR deletes.
• ChatView's server-update notice uses a static InfoIcon for running/failed/idle states.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

ComposerBanner and ComposerSurface now own the behaviors that four deleted test files pinned — attachment seam and placement (attached vs floating), per-variant outline/tint, stack-cap severity, tab vs inline rendering, and the sync status row — while ComposerBannerStack.test.tsx, ComposerStashBadge.test.tsx, ComposerTasksBadge.test.tsx and ThreadSyncStatusPill.test.tsx are removed and assertions are trimmed from ComposerCommandMenu.test.tsx / ComposerStashMenu.test.tsx. Nothing in apps/web renders ComposerBanner or ComposerSurface in a test, so the migrated contracts are unpinned.

This commit adds one more untested contract right here: width defaulting ("content" collapses to w-fit max-w-full flex-none and drops @container, so Row layout="wrap-actions" silently loses its container queries), plus the ChatComposer swap where threadSyncPhase suppresses activeTasksProgress/activeTaskSteps and takes the stack's attached slot.

Suggest a focused renderToStaticMarkup test for ComposerBanner.Root/Row covering attached vs floating placement, each variant's outline/tint tokens, and both width values, so these behaviors stay pinned the way the replaced components were.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency: one new finding on the latest push (combined loading/syncing banner). The earlier ThreadSyncStatusPill hand-rolled-row finding is resolved — ComposerActivityRow now composes Row/Icon/Content and shares the --composer-banner-icon-column grid. Findings from previous runs on this PR (server-update InfoIcon, banner description/action alignment, missing role="list" on the migrated task and stash lists, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body dropping the clipped panel's end/bottom padding, the deleted --chat-composer-drawer-inset declaration still read by ComposerCommandMenuLayer, and the removed Thinking-row test) are still open and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Peek is now the only pointer affordance for revealing the hidden notices, but its hit area is the 12px cap itself (h-3). ComposerBannerStack skips onPointerEnter when event.pointerType === "touch" and collapses the stack on onPointerDownCapture over the front banner, so on a coarse pointer this 12px strip is the only way to open the stack — before this PR any tap inside group/banner-stack revealed it through hover/focus-within. Elsewhere the system guarantees coarse pointers a 44px box (buttonVariants' pointer-coarse:after:min-h-11).

Suggest growing the tappable box upward only, so it stays clear of the front banner's dismiss/actions directly below:

Suggested change

	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"pointer-coarse:before:absolute pointer-coarse:before:inset-x-0 pointer-coarse:before:bottom-0 pointer-coarse:before:h-8",

^{Posted via Macroscope — UI Consistency}

[t3dotgg]

Restores the activity log grouping and shared composer banners from #8693 after #8733, while deferring the composer-attached working timer.

Working for keeps main's placement in the conversation timeline, including the current task label, Thinking state, and turn lifecycle. Long task labels truncate to one line while the timer remains fully visible. The composer keeps the restored task controls, notice stacking, and shared Tailwind components. Task progress appears only in the composer; the duplicate timeline checklist is removed. Plan proposals remain in the timeline. Stash stays in its own tab beside notices and expanded task lists, including compact layouts; its footer variant is removed. Loading and syncing use the shared banner stack and hide task controls until the thread is up to date. Their spinner respects reduced-motion preferences.

Rebased onto current main, including interim response folding and the latest failed-tool icon fix. Orchestrator V2 and queueing are deferred until this main-targeted PR is merged.

All after screenshots below were recaptured from 35e6b6653e95. The timeline comparisons render the same scripted events through the actual timeline components from the PR base, 8b817cbcaad7, and the current PR. Each pair uses matching viewport dimensions. Completed-turn folds are open in both versions; the mixed activity group is shown both collapsed and expanded. The composer comparisons retain their earlier-iteration before images, labelled separately.

Mixed command, file-read, and status entries now get one useful summary. Main already summarized tool-only groups; the improvement here is that mixed groups use that presentation too.

PR base: last command and hidden log entries	Current PR: summary of the whole group

Expanding that same group keeps the summary and shows compact detail rows, without separate Work Log headings.

PR base: expanded mixed log	Current PR: expanded activity group

Task updates no longer add Plan updated rows or a second checklist to the timeline. Commands stay in one group; task controls remain in the composer.

PR base: plan chatter and timeline checklist	Current PR: one command group, no duplicate tasks

The earlier error screenshot incorrectly modeled a failed test as a runtime error. These two corrected scenarios use the server's actual event conversion and payload projection.

Failed command followed by a successful retry — unchanged. A test exits with code 1, the fixture is edited, and the test reruns successfully. All three tool calls stay in one group on both the PR base and this branch. A nonzero command exit code does not split the group, and no failure-count prefix is added.

PR base: failed test and retry in one group	Current PR: same grouping

Expanding the group and failed command reveals the failure output in both versions:

PR base: failed command details	Current PR: same failure details

Provider crash at the end of a run. Two commands finish, then the provider exits unexpectedly and the turn ends. There are no commands continuing after the crash in this fixture. The base already shows the terminal runtime error; this PR gives the preceding commands their own summary and renders the error as a separate row.

PR base: terminal error with previous tool calls	Current PR: command summary followed by runtime error

The outer Worked for fold is open in every comparison. Collapsing that fold can still hide the error. The grouping boundary applies to error events, such as runtime failures, rather than ordinary failed tool results. This update corrects the evidence; it does not change production behavior.

The initial restore passed 242 focused web tests, web typecheck, and targeted lint. Checked the isolated fixture playground in the browser, including running/idle turns, task expansion, loading/syncing, notices, approvals, and stash. Stopping a turn removes the timer; deleting the last stashed prompt closes the stash. Preview fixtures remain local and are not part of the PR.

Earlier restore: attached timer	Current PR: timeline timer, tasks only in composer

Long task labels checked at 1440px and 768px viewport widths. Targeted lint and web typecheck pass.

PR base: wrapping task label	Current PR: single-line task label

Loading and syncing now keep the combined banner behavior: the status stays attached, notices peek behind it, and task controls stay hidden until the thread is up to date. Stash keeps its separate tab. Verified loading and syncing with and without tasks, notice expansion, narrow layouts, and reduced motion. All 64 focused tests, web typecheck, and targeted lint passed.

Earlier iteration: separate status row, tasks visible	Current PR: combined banner, tasks hidden

Narrow layout · Spinner recording

The stash placement update passed 61 focused tests, web typecheck, and targeted lint. Browser checks covered notices, expanded tasks, notice stacks, loading, narrow questions, compact-composer expansion, restoring a prompt, deleting the last entry, and the empty composer. This changes the shared web/desktop composer; native clients are unchanged.

Earlier iteration: stash in footer	Current PR: separate stash tab

With Stash closed, its tab stays beside the update notice:

Opening Stash shows the saved drafts in a drawer across the top of the composer, covering the notice underneath. Closing Stash reveals the notice again:

Expanded tasks keep their own panel beside Stash:

The task-list cleanup passed 218 focused tests, web typecheck, and targeted lint. Browser checks covered composer task expansion/collapse, command-group expansion, and completed turns. The working timer is unchanged. This uses the shared web/desktop timeline; native clients, providers, and wire contracts are unchanged.

Earlier restore: duplicate task checklist	Current PR: tasks only in the composer

The composer task list still expands beside Stash:

Note

Restore unified activity logs and rebuild composer banner system

• Removes turn-plan timeline rows and the MAX_VISIBLE_WORK_LOG_ENTRIES cap/overflow toggle, so work log entries are always shown in unified activity groups instead of being collapsed behind '+N previous …'
• Introduces a new update action type in ToolGroupAction for non-tool entries, with standalone rows for agent spawns and error-toned entries that bypass grouping
• Replaces ad-hoc composer layout with a new ComposerBanner, ComposerBannerStack, and ComposerSurface primitive system; tasks, stash, pending approvals, and server update notices all render through these shared components
• Integrates tasks progress into the banner stack (no longer dismissible per-turn) and adds a ComposerServerUpdateStatus component with dismissal support for failed update states
• Risk: ChatComposerProps replaces externalDrawerAttached with bannerItems and adds threadSyncPhase; ComposerStashBadge removes the placement prop; ComposerTasksBadge removes onDismiss and hasTrailingShoulder; deriveTurnPlans is deleted and deriveTimelineEntries no longer accepts turn plans — any out-of-tree callers of these APIs will break

^{Macroscope summarized cfb3851.}

---

Note

Medium Risk
Large, user-facing composer and timeline refactor with prop/API removals (externalDrawerAttached, task dismiss, turn plans); behavior changes for notices, sync, and work-log grouping are easy to miss in edge cases.

Overview
Restores unified timeline activity grouping and rebuilds the chat composer around shared ComposerSurface / ComposerBanner primitives.

Work log rendering drops the per-group visibility cap and turn-plan timeline rows. Mixed runs collapse into one expandable summary (including non-tool updates), while agent spawns and error-toned entries stay standalone. deriveTimelineEntries no longer takes turn plans.

Composer notices, thread sync, task progress, stash, approvals, and command/stash drawers all attach through ComposerBannerStack with explicit priority (activity / urgent / notice) instead of manual urgent/calm splits in ChatView. Banners move from above the glass shell into ChatComposer via bannerItems; threadSyncPhase suppresses task UI until sync finishes and can show ComposerActivityRow in the stack. Task progress is derived from the current turn’sactivePlan (not sidebar planProgress); per-turn task dismiss is removed. Stash is a shoulder tab only (no inline/footer variant). Server-update banners use ComposerServerUpdateStatus and can dismiss failed updates. shoulderTabReserve and the extra overlay mutation observer are removed—scroll clearance uses full composer height. BranchToolbar uses ComposerSurface.ContextStrip.

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

[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: f3a66e84-043e-4bc3-b47b-654eccf47321

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	+9 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−5 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	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.4 KiB	13.3 KiB	−16 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 8b817cb · PR result: 35e6b66 · 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]

UI consistency review found 2 issues in the new composer banner primitives. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The removed CollapsiblePanel className="px-3 sm:px-4" carried a comment explaining that the panel clips its content while the height animates, so the option buttons have to sit inside that padding or their focus rings get shaved. ComposerBanner.Body only supplies padding-inline-start, so the w-full option buttons now touch the panel's inline-end and block-end edges and their focus-visible:ring-1 is clipped by overflow-hidden. Restoring end/bottom padding inside the clipped box keeps the ring visible.

Suggested change

	<ComposerBanner.Body>
	<ComposerBanner.BodyclassName="pb-1 pe-1">

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This XXL change replaces shared composer and timeline behavior across many production paths, including notice stacking, task and sync visibility, activity grouping, and layout measurement. Several unresolved findings also identify interaction, accessibility, loading-state, and test-coverage regressions that require focused human review.

Not approved because:

• 3 blocking correctness issues found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[CDVolvik]

Verified fix(web): restore unified activity logs and composer banners at 39283f4 as CDVolvik.

Restores #8693 after #8733 revert — git diff 33 files +1506/-2094 identical to original. Activity logs: MessagesTimeline working row removed, work entries grouped contiguously, ChatView active task progress tied to activePlan of current turn, ChatComposer exposes bannerItems/isWorking. Composer banners: ComposerSurface/Banner primitives, priority activity<urgent<notice, custom tasks content, accessible peek. Tests: MessagesTimeline.logic+session-logic+versionSkew+ChatView.logic 194/194, MessagesTimeline 37/37 pass. Note per PR: Compact/dismiss alignment and banner padding not fixed yet — author defers to Julius — hold merge until follow-up. Otherwise LGTM, no push.

[macroscopeapp]

🟡 Mediumchat/ComposerBanner.tsx:94

When the notice stack is expanded, the Peek button remains pointer-interactive and keyboard-focusable despite receiving opacity-0, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply pointer-events-none and disabled (or omit it from the DOM) while the stack is expanded.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ComposerBanner.tsx around line 94:
When the notice stack is expanded, the `Peek` button remains pointer-interactive and keyboard-focusable despite receiving `opacity-0`, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply `pointer-events-none` and `disabled` (or omit it from the DOM) while the stack is expanded.

[macroscopeapp]

🟡 Mediumchat/ChatComposer.tsx:3602

ComposerTasksBadge and ComposerTasksDrawer no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.

Also found in 2 other location(s)

apps/web/src/components/chat/ComposerTasksBadge.tsx:112

ComposerTasksBadge no longer accepts or renders an onDismiss action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.

apps/web/src/components/chat/ComposerTasksBadge.tsx:232

ComposerTasksDrawer no longer accepts or renders the former onDismiss action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed dismissTasks to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ChatComposer.tsx around line 3602:
`ComposerTasksBadge` and `ComposerTasksDrawer` no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.
Also found in 2 other location(s):
- apps/web/src/components/chat/ComposerTasksBadge.tsx:112 -- `ComposerTasksBadge` no longer accepts or renders an `onDismiss` action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.
- apps/web/src/components/chat/ComposerTasksBadge.tsx:232 -- `ComposerTasksDrawer` no longer accepts or renders the former `onDismiss` action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed `dismissTasks` to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

[macroscopeapp]

UI consistency review of the restored composer banner/surface system. Three findings below; the two findings posted on the previous head (ComposerBanner.ToggleIcon inheriting the coarse-pointer hit-target pseudo-element, and ComposerBanner.Body losing the clipped panel's end/bottom padding) are still open on this head and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Notices with a description now bind both the icon and the action/dismiss controls to the titleRow, with the description rendered as a separate row underneath (ComposerBanner.Children). That reproduces the alignment regression this PR's description acknowledges as the reason #8693 was reverted: Compact / dismiss sit on the title line instead of being centered against the whole title + description block.

The primitive it replaced did this in one row: Alert (controlAlignment: "center") lays out icon | title+description column | actions in a single items-center flex row, so the controls center against the full block and only opt into first-line alignment explicitly.

Smallest fix: keep the description inside the same Row's ComposerBanner.Content (stacked, e.g. className="flex-col items-start gap-0.5" with the title span keeping font-medium) and reserve ComposerBanner.Children for item.children, so the row's items-center centers the icon and actions over both lines. The other half of the revert — banner edge padding, now p-1 on ComposerBanner.Root versus the old px-3 pt-2 sm:px-4 — belongs on Root rather than at each call site.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Attachment hardcodes the drawer inset (w-[calc(100%-2.75rem)], max-w-[45.25rem]), while this PR deletes the only declaration of --chat-composer-drawer-inset: 1.375rem from index.css. That variable still has an imperative consumer: ComposerCommandMenuLayer reads it with getComputedStyle(form ?? anchor).getPropertyValue("--chat-composer-drawer-inset") (ChatComposer.tsx:233) to compute the command menu's left and width. The read now always resolves to "" and silently takes the || 1.375 fallback, so the menu lines up only because 2.75rem happens to be twice that fallback, and the two owners will drift the next time this width changes.

Suggest keeping one owner: declare [--chat-composer-drawer-inset:1.375rem] on an ancestor the composer form inherits from (ComposerSurface.Shell) and derive the widths here from it, e.g. w-[calc(100%-2*var(--chat-composer-drawer-inset))] max-w-[calc(48rem-2*var(--chat-composer-drawer-inset))].

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This test was dropped when the working row left the timeline, but the follow-up commit restored WorkingTimelineRow/ThinkingActivityRow and the activeTurnStartedAt prop, and LiveActivityContent still emits gap-1.5 py-0.5 px-1 for the iconless variant — so the assertions still hold and the restored row is now unguarded, right as this PR reworks neighbouring row indentation (TurnPlanTimelineRow's chevron column and pl-6 → pl-8). Suggest restoring it as-is.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration at fe1774e. One new finding below (list semantics lost in the tasks/stash list migration). The findings from my earlier reviews on this PR are still open and are not reposted here:

• ComposerBannerStack.tsx — description notices bind icon/actions to the title row, so Compact/dismiss no longer center against the title + description block.
• ComposerBanner.tsxAttachment — hardcoded inset while --chat-composer-drawer-inset is deleted from index.css, leaving ComposerCommandMenuLayer's getPropertyValue read resolving to "".
• ComposerBanner.tsxToggleIcon — decorative aria-hidden span inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 hit overlay inside Row render={<button/>}.
• ComposerPendingUserInputPanel.tsx — ComposerBanner.Body supplies only inline-start padding, so option-button focus rings are clipped by the animating CollapsiblePanel.
• MessagesTimeline.test.tsx — the iconless Thinking/working-timer alignment test is still dropped while the row it covered is restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The task list loses its list semantics in this migration: the old drawer rendered role="list" + role="listitem" explicitly (the deleted ComposerTasksBadge.test.tsx asserted both), while this <ul> relies on implicit roles. Tailwind's preflight sets list-style: none on ul, which makes WebKit drop the list role — and with it the aria-label on this container, since a generic element's label is not announced. Suggest re-asserting the role on the container (the li children keep listitem once the list role is explicit). ComposerStashMenu.tsx:133 has the same shape (render={<ul />} with aria-label="Stashed prompts") and needs the same fix.

Suggested change

	>
	render={<ulrole="list"/>}

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c0d3d53. Configure here.}

[macroscopeapp]

Reviewed the two new commits (c0d3d53 restoring the sync status, 4977016 moving the stash tab into the banner dock) plus the surrounding banner/surface migration.

One new finding on the restored ThreadSyncStatusPill (inline). The findings from earlier runs on this PR still apply at 4977016 and are not repeated here:

• ComposerBanner.ToggleIcon inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 overlay on a decorative span.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus-visible ring is clipped by the collapsible panel's overflow-hidden (ComposerPendingUserInputPanel.tsx:203-262).
• ComposerBannerStackAlert binds actions/dismiss to the title row while the description renders as a separate row, so controls are no longer centered against the title + description block.
• The tasks list (ComposerBanner.Children render={<ul />}) relies on implicit list semantics, which Tailwind preflight's list-style: none drops in WebKit along with the container aria-label.
• apps/web/src/components/chat/MessagesTimeline.test.tsx still drops the working/thinking row assertions even though WorkingTimelineRow was restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

🟡 Mediumcomponents/ChatView.tsx:4556

activeComposerTasksProgress returns null while thread details are loading because it now derives entirely from activePlan, which reads threadActivities — but buildLoadingThreadFromShell forces activities: [] during the loading window. The previous code fell back to activeThreadShell?.planProgress, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.

Consider falling back to activeThreadShell?.planProgress when activePlan is null and the thread is still loading, so the shell-level progress remains visible during that window.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/ChatView.tsx around line 4556:
`activeComposerTasksProgress` returns `null` while thread details are loading because it now derives entirely from `activePlan`, which reads `threadActivities` — but `buildLoadingThreadFromShell` forces `activities: []` during the loading window. The previous code fell back to `activeThreadShell?.planProgress`, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.
Consider falling back to `activeThreadShell?.planProgress` when `activePlan` is `null` and the thread is still loading, so the shell-level progress remains visible during that window.

[macroscopeapp]

One new finding in this push's neighbourhood: the composer server-update notice lost the live/failure indicator that ServerUpdateProgress used to own, and now shows a static InfoIcon even in the error variant. Previously reported findings on the earlier commits (banner Attachment inset vs. the deleted --chat-composer-drawer-inset, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body end/bottom padding, notice description/action alignment, ThreadSyncStatusPill bypassing the banner row grid, task-list role="list", and the dropped working-row alignment test) still apply and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This notice now uses a static InfoIcon for all three states, which drops the only live cue for a running update and puts an info icon on an error-variant banner. The removed code explained why: ServerUpdateProgress carried a pulsing dot while running and a destructive dot on failure, and only the idle offer needed an icon. ComposerServerUpdateStatus renders text only, so the pulse is gone and the failed row reads as informational next to the sibling notices that do pick situational icons (WifiOffIcon, AlarmClockIcon, GitBranchIcon) and a pulsing dot for live states.

Suggest keeping InfoIcon for the idle offer and restoring the dots for the other two states (ComposerBanner.Dot exists for exactly this and currently has no consumer, if you prefer routing it through the primitive):

Suggested change

	icon: <InfoIconaria-hidden/>,
	icon: updateInProgress ? (
	<span
	className="size-1.5 animate-status-pulse rounded-full bg-foreground"
	aria-hidden="true"
	/>
	) : updateFailed ? (
	<spanclassName="size-1.5 rounded-full bg-destructive"aria-hidden="true"/>
	) : (
	<InfoIconaria-hidden/>
	),

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration again against the new commit (53c1702, "restore combined loading and syncing banners").

The sync status now composes ComposerBanner.Row / Icon / Content (ComposerActivityStatus.tsx), which resolves the icon-column misalignment flagged on 4977016. One new finding below on the verification gate for the primitives this PR introduces.

Findings raised on earlier commits that are still present at this head (not re-posted):

• ComposerBanner.ToggleIcon inherits the full buttonVariants base, including the pointer-coarse 44x44 ::after hit box, inside rows that are themselves buttons.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus rings are clipped by the animating CollapsiblePanel.
• The task list relies on implicit ul/li roles after Preflight's list-style: none, dropping the list role and its aria-label in WebKit.
• Notice descriptions render as a second row, so actions/dismiss align to the title line instead of the whole block.
• ComposerCommandMenuLayer still reads --chat-composer-drawer-inset, whose only declaration this PR deletes.
• ChatView's server-update notice uses a static InfoIcon for running/failed/idle states.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

ComposerBanner and ComposerSurface now own the behaviors that four deleted test files pinned — attachment seam and placement (attached vs floating), per-variant outline/tint, stack-cap severity, tab vs inline rendering, and the sync status row — while ComposerBannerStack.test.tsx, ComposerStashBadge.test.tsx, ComposerTasksBadge.test.tsx and ThreadSyncStatusPill.test.tsx are removed and assertions are trimmed from ComposerCommandMenu.test.tsx / ComposerStashMenu.test.tsx. Nothing in apps/web renders ComposerBanner or ComposerSurface in a test, so the migrated contracts are unpinned.

This commit adds one more untested contract right here: width defaulting ("content" collapses to w-fit max-w-full flex-none and drops @container, so Row layout="wrap-actions" silently loses its container queries), plus the ChatComposer swap where threadSyncPhase suppresses activeTasksProgress/activeTaskSteps and takes the stack's attached slot.

Suggest a focused renderToStaticMarkup test for ComposerBanner.Root/Row covering attached vs floating placement, each variant's outline/tint tokens, and both width values, so these behaviors stay pinned the way the replaced components were.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency: one new finding on the latest push (combined loading/syncing banner). The earlier ThreadSyncStatusPill hand-rolled-row finding is resolved — ComposerActivityRow now composes Row/Icon/Content and shares the --composer-banner-icon-column grid. Findings from previous runs on this PR (server-update InfoIcon, banner description/action alignment, missing role="list" on the migrated task and stash lists, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body dropping the clipped panel's end/bottom padding, the deleted --chat-composer-drawer-inset declaration still read by ComposerCommandMenuLayer, and the removed Thinking-row test) are still open and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Peek is now the only pointer affordance for revealing the hidden notices, but its hit area is the 12px cap itself (h-3). ComposerBannerStack skips onPointerEnter when event.pointerType === "touch" and collapses the stack on onPointerDownCapture over the front banner, so on a coarse pointer this 12px strip is the only way to open the stack — before this PR any tap inside group/banner-stack revealed it through hover/focus-within. Elsewhere the system guarantees coarse pointers a 44px box (buttonVariants' pointer-coarse:after:min-h-11).

Suggest growing the tappable box upward only, so it stays clear of the front banner's dismiss/actions directly below:

Suggested change

	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"pointer-coarse:before:absolute pointer-coarse:before:inset-x-0 pointer-coarse:before:bottom-0 pointer-coarse:before:h-8",

^{Posted via Macroscope — UI Consistency}

[t3dotgg]

Restores the activity log grouping and shared composer banners from #8693 after #8733, while deferring the composer-attached working timer.

Working for keeps main's placement in the conversation timeline, including the current task label, Thinking state, and turn lifecycle. Long task labels truncate to one line while the timer remains fully visible. The composer keeps the restored task controls, notice stacking, and shared Tailwind components. Task progress appears only in the composer; the duplicate timeline checklist is removed. Plan proposals remain in the timeline. Stash stays in its own tab beside notices and expanded task lists, including compact layouts; its footer variant is removed. Loading and syncing use the shared banner stack and hide task controls until the thread is up to date. Their spinner respects reduced-motion preferences.

Rebased onto current main, including interim response folding and the latest failed-tool icon fix. Orchestrator V2 and queueing are deferred until this main-targeted PR is merged.

All after screenshots below were recaptured from 35e6b6653e95. The timeline comparisons render the same scripted events through the actual timeline components from the PR base, 8b817cbcaad7, and the current PR. Each pair uses matching viewport dimensions. Completed-turn folds are open in both versions; the mixed activity group is shown both collapsed and expanded. The composer comparisons retain their earlier-iteration before images, labelled separately.

Mixed command, file-read, and status entries now get one useful summary. Main already summarized tool-only groups; the improvement here is that mixed groups use that presentation too.

PR base: last command and hidden log entries	Current PR: summary of the whole group

Expanding that same group keeps the summary and shows compact detail rows, without separate Work Log headings.

PR base: expanded mixed log	Current PR: expanded activity group

Task updates no longer add Plan updated rows or a second checklist to the timeline. Commands stay in one group; task controls remain in the composer.

PR base: plan chatter and timeline checklist	Current PR: one command group, no duplicate tasks

The earlier error screenshot incorrectly modeled a failed test as a runtime error. These two corrected scenarios use the server's actual event conversion and payload projection.

Failed command followed by a successful retry — unchanged. A test exits with code 1, the fixture is edited, and the test reruns successfully. All three tool calls stay in one group on both the PR base and this branch. A nonzero command exit code does not split the group, and no failure-count prefix is added.

PR base: failed test and retry in one group	Current PR: same grouping

Expanding the group and failed command reveals the failure output in both versions:

PR base: failed command details	Current PR: same failure details

Provider crash at the end of a run. Two commands finish, then the provider exits unexpectedly and the turn ends. There are no commands continuing after the crash in this fixture. The base already shows the terminal runtime error; this PR gives the preceding commands their own summary and renders the error as a separate row.

PR base: terminal error with previous tool calls	Current PR: command summary followed by runtime error

The outer Worked for fold is open in every comparison. Collapsing that fold can still hide the error. The grouping boundary applies to error events, such as runtime failures, rather than ordinary failed tool results. This update corrects the evidence; it does not change production behavior.

The initial restore passed 242 focused web tests, web typecheck, and targeted lint. Checked the isolated fixture playground in the browser, including running/idle turns, task expansion, loading/syncing, notices, approvals, and stash. Stopping a turn removes the timer; deleting the last stashed prompt closes the stash. Preview fixtures remain local and are not part of the PR.

Earlier restore: attached timer	Current PR: timeline timer, tasks only in composer

Long task labels checked at 1440px and 768px viewport widths. Targeted lint and web typecheck pass.

PR base: wrapping task label	Current PR: single-line task label

Loading and syncing now keep the combined banner behavior: the status stays attached, notices peek behind it, and task controls stay hidden until the thread is up to date. Stash keeps its separate tab. Verified loading and syncing with and without tasks, notice expansion, narrow layouts, and reduced motion. All 64 focused tests, web typecheck, and targeted lint passed.

Earlier iteration: separate status row, tasks visible	Current PR: combined banner, tasks hidden

Narrow layout · Spinner recording

The stash placement update passed 61 focused tests, web typecheck, and targeted lint. Browser checks covered notices, expanded tasks, notice stacks, loading, narrow questions, compact-composer expansion, restoring a prompt, deleting the last entry, and the empty composer. This changes the shared web/desktop composer; native clients are unchanged.

Earlier iteration: stash in footer	Current PR: separate stash tab

With Stash closed, its tab stays beside the update notice:

Opening Stash shows the saved drafts in a drawer across the top of the composer, covering the notice underneath. Closing Stash reveals the notice again:

Expanded tasks keep their own panel beside Stash:

The task-list cleanup passed 218 focused tests, web typecheck, and targeted lint. Browser checks covered composer task expansion/collapse, command-group expansion, and completed turns. The working timer is unchanged. This uses the shared web/desktop timeline; native clients, providers, and wire contracts are unchanged.

Earlier restore: duplicate task checklist	Current PR: tasks only in the composer

The composer task list still expands beside Stash:

Note

Restore unified activity logs and rebuild composer banner system

• Removes turn-plan timeline rows and the MAX_VISIBLE_WORK_LOG_ENTRIES cap/overflow toggle, so work log entries are always shown in unified activity groups instead of being collapsed behind '+N previous …'
• Introduces a new update action type in ToolGroupAction for non-tool entries, with standalone rows for agent spawns and error-toned entries that bypass grouping
• Replaces ad-hoc composer layout with a new ComposerBanner, ComposerBannerStack, and ComposerSurface primitive system; tasks, stash, pending approvals, and server update notices all render through these shared components
• Integrates tasks progress into the banner stack (no longer dismissible per-turn) and adds a ComposerServerUpdateStatus component with dismissal support for failed update states
• Risk: ChatComposerProps replaces externalDrawerAttached with bannerItems and adds threadSyncPhase; ComposerStashBadge removes the placement prop; ComposerTasksBadge removes onDismiss and hasTrailingShoulder; deriveTurnPlans is deleted and deriveTimelineEntries no longer accepts turn plans — any out-of-tree callers of these APIs will break

^{Macroscope summarized cfb3851.}

---

Note

Medium Risk
Large, user-facing composer and timeline refactor with prop/API removals (externalDrawerAttached, task dismiss, turn plans); behavior changes for notices, sync, and work-log grouping are easy to miss in edge cases.

Overview
Restores unified timeline activity grouping and rebuilds the chat composer around shared ComposerSurface / ComposerBanner primitives.

Work log rendering drops the per-group visibility cap and turn-plan timeline rows. Mixed runs collapse into one expandable summary (including non-tool updates), while agent spawns and error-toned entries stay standalone. deriveTimelineEntries no longer takes turn plans.

Composer notices, thread sync, task progress, stash, approvals, and command/stash drawers all attach through ComposerBannerStack with explicit priority (activity / urgent / notice) instead of manual urgent/calm splits in ChatView. Banners move from above the glass shell into ChatComposer via bannerItems; threadSyncPhase suppresses task UI until sync finishes and can show ComposerActivityRow in the stack. Task progress is derived from the current turn’sactivePlan (not sidebar planProgress); per-turn task dismiss is removed. Stash is a shoulder tab only (no inline/footer variant). Server-update banners use ComposerServerUpdateStatus and can dismiss failed updates. shoulderTabReserve and the extra overlay mutation observer are removed—scroll clearance uses full composer height. BranchToolbar uses ComposerSurface.ContextStrip.

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

[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: f3a66e84-043e-4bc3-b47b-654eccf47321

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	+9 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−5 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	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.4 KiB	13.3 KiB	−16 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 8b817cb · PR result: 35e6b66 · 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]

UI consistency review found 2 issues in the new composer banner primitives. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The removed CollapsiblePanel className="px-3 sm:px-4" carried a comment explaining that the panel clips its content while the height animates, so the option buttons have to sit inside that padding or their focus rings get shaved. ComposerBanner.Body only supplies padding-inline-start, so the w-full option buttons now touch the panel's inline-end and block-end edges and their focus-visible:ring-1 is clipped by overflow-hidden. Restoring end/bottom padding inside the clipped box keeps the ring visible.

Suggested change

	<ComposerBanner.Body>
	<ComposerBanner.BodyclassName="pb-1 pe-1">

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This XXL change replaces shared composer and timeline behavior across many production paths, including notice stacking, task and sync visibility, activity grouping, and layout measurement. Several unresolved findings also identify interaction, accessibility, loading-state, and test-coverage regressions that require focused human review.

Not approved because:

• 3 blocking correctness issues found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[CDVolvik]

Verified fix(web): restore unified activity logs and composer banners at 39283f4 as CDVolvik.

Restores #8693 after #8733 revert — git diff 33 files +1506/-2094 identical to original. Activity logs: MessagesTimeline working row removed, work entries grouped contiguously, ChatView active task progress tied to activePlan of current turn, ChatComposer exposes bannerItems/isWorking. Composer banners: ComposerSurface/Banner primitives, priority activity<urgent<notice, custom tasks content, accessible peek. Tests: MessagesTimeline.logic+session-logic+versionSkew+ChatView.logic 194/194, MessagesTimeline 37/37 pass. Note per PR: Compact/dismiss alignment and banner padding not fixed yet — author defers to Julius — hold merge until follow-up. Otherwise LGTM, no push.

[macroscopeapp]

🟡 Mediumchat/ComposerBanner.tsx:94

When the notice stack is expanded, the Peek button remains pointer-interactive and keyboard-focusable despite receiving opacity-0, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply pointer-events-none and disabled (or omit it from the DOM) while the stack is expanded.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ComposerBanner.tsx around line 94:
When the notice stack is expanded, the `Peek` button remains pointer-interactive and keyboard-focusable despite receiving `opacity-0`, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply `pointer-events-none` and `disabled` (or omit it from the DOM) while the stack is expanded.

[macroscopeapp]

🟡 Mediumchat/ChatComposer.tsx:3602

ComposerTasksBadge and ComposerTasksDrawer no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.

Also found in 2 other location(s)

apps/web/src/components/chat/ComposerTasksBadge.tsx:112

ComposerTasksBadge no longer accepts or renders an onDismiss action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.

apps/web/src/components/chat/ComposerTasksBadge.tsx:232

ComposerTasksDrawer no longer accepts or renders the former onDismiss action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed dismissTasks to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ChatComposer.tsx around line 3602:
`ComposerTasksBadge` and `ComposerTasksDrawer` no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.
Also found in 2 other location(s):
- apps/web/src/components/chat/ComposerTasksBadge.tsx:112 -- `ComposerTasksBadge` no longer accepts or renders an `onDismiss` action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.
- apps/web/src/components/chat/ComposerTasksBadge.tsx:232 -- `ComposerTasksDrawer` no longer accepts or renders the former `onDismiss` action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed `dismissTasks` to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

[macroscopeapp]

UI consistency review of the restored composer banner/surface system. Three findings below; the two findings posted on the previous head (ComposerBanner.ToggleIcon inheriting the coarse-pointer hit-target pseudo-element, and ComposerBanner.Body losing the clipped panel's end/bottom padding) are still open on this head and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Notices with a description now bind both the icon and the action/dismiss controls to the titleRow, with the description rendered as a separate row underneath (ComposerBanner.Children). That reproduces the alignment regression this PR's description acknowledges as the reason #8693 was reverted: Compact / dismiss sit on the title line instead of being centered against the whole title + description block.

The primitive it replaced did this in one row: Alert (controlAlignment: "center") lays out icon | title+description column | actions in a single items-center flex row, so the controls center against the full block and only opt into first-line alignment explicitly.

Smallest fix: keep the description inside the same Row's ComposerBanner.Content (stacked, e.g. className="flex-col items-start gap-0.5" with the title span keeping font-medium) and reserve ComposerBanner.Children for item.children, so the row's items-center centers the icon and actions over both lines. The other half of the revert — banner edge padding, now p-1 on ComposerBanner.Root versus the old px-3 pt-2 sm:px-4 — belongs on Root rather than at each call site.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Attachment hardcodes the drawer inset (w-[calc(100%-2.75rem)], max-w-[45.25rem]), while this PR deletes the only declaration of --chat-composer-drawer-inset: 1.375rem from index.css. That variable still has an imperative consumer: ComposerCommandMenuLayer reads it with getComputedStyle(form ?? anchor).getPropertyValue("--chat-composer-drawer-inset") (ChatComposer.tsx:233) to compute the command menu's left and width. The read now always resolves to "" and silently takes the || 1.375 fallback, so the menu lines up only because 2.75rem happens to be twice that fallback, and the two owners will drift the next time this width changes.

Suggest keeping one owner: declare [--chat-composer-drawer-inset:1.375rem] on an ancestor the composer form inherits from (ComposerSurface.Shell) and derive the widths here from it, e.g. w-[calc(100%-2*var(--chat-composer-drawer-inset))] max-w-[calc(48rem-2*var(--chat-composer-drawer-inset))].

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This test was dropped when the working row left the timeline, but the follow-up commit restored WorkingTimelineRow/ThinkingActivityRow and the activeTurnStartedAt prop, and LiveActivityContent still emits gap-1.5 py-0.5 px-1 for the iconless variant — so the assertions still hold and the restored row is now unguarded, right as this PR reworks neighbouring row indentation (TurnPlanTimelineRow's chevron column and pl-6 → pl-8). Suggest restoring it as-is.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration at fe1774e. One new finding below (list semantics lost in the tasks/stash list migration). The findings from my earlier reviews on this PR are still open and are not reposted here:

• ComposerBannerStack.tsx — description notices bind icon/actions to the title row, so Compact/dismiss no longer center against the title + description block.
• ComposerBanner.tsxAttachment — hardcoded inset while --chat-composer-drawer-inset is deleted from index.css, leaving ComposerCommandMenuLayer's getPropertyValue read resolving to "".
• ComposerBanner.tsxToggleIcon — decorative aria-hidden span inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 hit overlay inside Row render={<button/>}.
• ComposerPendingUserInputPanel.tsx — ComposerBanner.Body supplies only inline-start padding, so option-button focus rings are clipped by the animating CollapsiblePanel.
• MessagesTimeline.test.tsx — the iconless Thinking/working-timer alignment test is still dropped while the row it covered is restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The task list loses its list semantics in this migration: the old drawer rendered role="list" + role="listitem" explicitly (the deleted ComposerTasksBadge.test.tsx asserted both), while this <ul> relies on implicit roles. Tailwind's preflight sets list-style: none on ul, which makes WebKit drop the list role — and with it the aria-label on this container, since a generic element's label is not announced. Suggest re-asserting the role on the container (the li children keep listitem once the list role is explicit). ComposerStashMenu.tsx:133 has the same shape (render={<ul />} with aria-label="Stashed prompts") and needs the same fix.

Suggested change

	>
	render={<ulrole="list"/>}

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c0d3d53. Configure here.}

[macroscopeapp]

Reviewed the two new commits (c0d3d53 restoring the sync status, 4977016 moving the stash tab into the banner dock) plus the surrounding banner/surface migration.

One new finding on the restored ThreadSyncStatusPill (inline). The findings from earlier runs on this PR still apply at 4977016 and are not repeated here:

• ComposerBanner.ToggleIcon inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 overlay on a decorative span.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus-visible ring is clipped by the collapsible panel's overflow-hidden (ComposerPendingUserInputPanel.tsx:203-262).
• ComposerBannerStackAlert binds actions/dismiss to the title row while the description renders as a separate row, so controls are no longer centered against the title + description block.
• The tasks list (ComposerBanner.Children render={<ul />}) relies on implicit list semantics, which Tailwind preflight's list-style: none drops in WebKit along with the container aria-label.
• apps/web/src/components/chat/MessagesTimeline.test.tsx still drops the working/thinking row assertions even though WorkingTimelineRow was restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

🟡 Mediumcomponents/ChatView.tsx:4556

activeComposerTasksProgress returns null while thread details are loading because it now derives entirely from activePlan, which reads threadActivities — but buildLoadingThreadFromShell forces activities: [] during the loading window. The previous code fell back to activeThreadShell?.planProgress, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.

Consider falling back to activeThreadShell?.planProgress when activePlan is null and the thread is still loading, so the shell-level progress remains visible during that window.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/ChatView.tsx around line 4556:
`activeComposerTasksProgress` returns `null` while thread details are loading because it now derives entirely from `activePlan`, which reads `threadActivities` — but `buildLoadingThreadFromShell` forces `activities: []` during the loading window. The previous code fell back to `activeThreadShell?.planProgress`, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.
Consider falling back to `activeThreadShell?.planProgress` when `activePlan` is `null` and the thread is still loading, so the shell-level progress remains visible during that window.

[macroscopeapp]

One new finding in this push's neighbourhood: the composer server-update notice lost the live/failure indicator that ServerUpdateProgress used to own, and now shows a static InfoIcon even in the error variant. Previously reported findings on the earlier commits (banner Attachment inset vs. the deleted --chat-composer-drawer-inset, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body end/bottom padding, notice description/action alignment, ThreadSyncStatusPill bypassing the banner row grid, task-list role="list", and the dropped working-row alignment test) still apply and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This notice now uses a static InfoIcon for all three states, which drops the only live cue for a running update and puts an info icon on an error-variant banner. The removed code explained why: ServerUpdateProgress carried a pulsing dot while running and a destructive dot on failure, and only the idle offer needed an icon. ComposerServerUpdateStatus renders text only, so the pulse is gone and the failed row reads as informational next to the sibling notices that do pick situational icons (WifiOffIcon, AlarmClockIcon, GitBranchIcon) and a pulsing dot for live states.

Suggest keeping InfoIcon for the idle offer and restoring the dots for the other two states (ComposerBanner.Dot exists for exactly this and currently has no consumer, if you prefer routing it through the primitive):

Suggested change

	icon: <InfoIconaria-hidden/>,
	icon: updateInProgress ? (
	<span
	className="size-1.5 animate-status-pulse rounded-full bg-foreground"
	aria-hidden="true"
	/>
	) : updateFailed ? (
	<spanclassName="size-1.5 rounded-full bg-destructive"aria-hidden="true"/>
	) : (
	<InfoIconaria-hidden/>
	),

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration again against the new commit (53c1702, "restore combined loading and syncing banners").

The sync status now composes ComposerBanner.Row / Icon / Content (ComposerActivityStatus.tsx), which resolves the icon-column misalignment flagged on 4977016. One new finding below on the verification gate for the primitives this PR introduces.

Findings raised on earlier commits that are still present at this head (not re-posted):

• ComposerBanner.ToggleIcon inherits the full buttonVariants base, including the pointer-coarse 44x44 ::after hit box, inside rows that are themselves buttons.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus rings are clipped by the animating CollapsiblePanel.
• The task list relies on implicit ul/li roles after Preflight's list-style: none, dropping the list role and its aria-label in WebKit.
• Notice descriptions render as a second row, so actions/dismiss align to the title line instead of the whole block.
• ComposerCommandMenuLayer still reads --chat-composer-drawer-inset, whose only declaration this PR deletes.
• ChatView's server-update notice uses a static InfoIcon for running/failed/idle states.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

ComposerBanner and ComposerSurface now own the behaviors that four deleted test files pinned — attachment seam and placement (attached vs floating), per-variant outline/tint, stack-cap severity, tab vs inline rendering, and the sync status row — while ComposerBannerStack.test.tsx, ComposerStashBadge.test.tsx, ComposerTasksBadge.test.tsx and ThreadSyncStatusPill.test.tsx are removed and assertions are trimmed from ComposerCommandMenu.test.tsx / ComposerStashMenu.test.tsx. Nothing in apps/web renders ComposerBanner or ComposerSurface in a test, so the migrated contracts are unpinned.

This commit adds one more untested contract right here: width defaulting ("content" collapses to w-fit max-w-full flex-none and drops @container, so Row layout="wrap-actions" silently loses its container queries), plus the ChatComposer swap where threadSyncPhase suppresses activeTasksProgress/activeTaskSteps and takes the stack's attached slot.

Suggest a focused renderToStaticMarkup test for ComposerBanner.Root/Row covering attached vs floating placement, each variant's outline/tint tokens, and both width values, so these behaviors stay pinned the way the replaced components were.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency: one new finding on the latest push (combined loading/syncing banner). The earlier ThreadSyncStatusPill hand-rolled-row finding is resolved — ComposerActivityRow now composes Row/Icon/Content and shares the --composer-banner-icon-column grid. Findings from previous runs on this PR (server-update InfoIcon, banner description/action alignment, missing role="list" on the migrated task and stash lists, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body dropping the clipped panel's end/bottom padding, the deleted --chat-composer-drawer-inset declaration still read by ComposerCommandMenuLayer, and the removed Thinking-row test) are still open and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Peek is now the only pointer affordance for revealing the hidden notices, but its hit area is the 12px cap itself (h-3). ComposerBannerStack skips onPointerEnter when event.pointerType === "touch" and collapses the stack on onPointerDownCapture over the front banner, so on a coarse pointer this 12px strip is the only way to open the stack — before this PR any tap inside group/banner-stack revealed it through hover/focus-within. Elsewhere the system guarantees coarse pointers a 44px box (buttonVariants' pointer-coarse:after:min-h-11).

Suggest growing the tappable box upward only, so it stays clear of the front banner's dismiss/actions directly below:

Suggested change

	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"pointer-coarse:before:absolute pointer-coarse:before:inset-x-0 pointer-coarse:before:bottom-0 pointer-coarse:before:h-8",

^{Posted via Macroscope — UI Consistency}

[t3dotgg]

Restores the activity log grouping and shared composer banners from #8693 after #8733, while deferring the composer-attached working timer.

Working for keeps main's placement in the conversation timeline, including the current task label, Thinking state, and turn lifecycle. Long task labels truncate to one line while the timer remains fully visible. The composer keeps the restored task controls, notice stacking, and shared Tailwind components. Task progress appears only in the composer; the duplicate timeline checklist is removed. Plan proposals remain in the timeline. Stash stays in its own tab beside notices and expanded task lists, including compact layouts; its footer variant is removed. Loading and syncing use the shared banner stack and hide task controls until the thread is up to date. Their spinner respects reduced-motion preferences.

Rebased onto current main, including interim response folding and the latest failed-tool icon fix. Orchestrator V2 and queueing are deferred until this main-targeted PR is merged.

All after screenshots below were recaptured from 35e6b6653e95. The timeline comparisons render the same scripted events through the actual timeline components from the PR base, 8b817cbcaad7, and the current PR. Each pair uses matching viewport dimensions. Completed-turn folds are open in both versions; the mixed activity group is shown both collapsed and expanded. The composer comparisons retain their earlier-iteration before images, labelled separately.

Mixed command, file-read, and status entries now get one useful summary. Main already summarized tool-only groups; the improvement here is that mixed groups use that presentation too.

PR base: last command and hidden log entries	Current PR: summary of the whole group

Expanding that same group keeps the summary and shows compact detail rows, without separate Work Log headings.

PR base: expanded mixed log	Current PR: expanded activity group

Task updates no longer add Plan updated rows or a second checklist to the timeline. Commands stay in one group; task controls remain in the composer.

PR base: plan chatter and timeline checklist	Current PR: one command group, no duplicate tasks

The earlier error screenshot incorrectly modeled a failed test as a runtime error. These two corrected scenarios use the server's actual event conversion and payload projection.

Failed command followed by a successful retry — unchanged. A test exits with code 1, the fixture is edited, and the test reruns successfully. All three tool calls stay in one group on both the PR base and this branch. A nonzero command exit code does not split the group, and no failure-count prefix is added.

PR base: failed test and retry in one group	Current PR: same grouping

Expanding the group and failed command reveals the failure output in both versions:

PR base: failed command details	Current PR: same failure details

Provider crash at the end of a run. Two commands finish, then the provider exits unexpectedly and the turn ends. There are no commands continuing after the crash in this fixture. The base already shows the terminal runtime error; this PR gives the preceding commands their own summary and renders the error as a separate row.

PR base: terminal error with previous tool calls	Current PR: command summary followed by runtime error

The outer Worked for fold is open in every comparison. Collapsing that fold can still hide the error. The grouping boundary applies to error events, such as runtime failures, rather than ordinary failed tool results. This update corrects the evidence; it does not change production behavior.

The initial restore passed 242 focused web tests, web typecheck, and targeted lint. Checked the isolated fixture playground in the browser, including running/idle turns, task expansion, loading/syncing, notices, approvals, and stash. Stopping a turn removes the timer; deleting the last stashed prompt closes the stash. Preview fixtures remain local and are not part of the PR.

Earlier restore: attached timer	Current PR: timeline timer, tasks only in composer

Long task labels checked at 1440px and 768px viewport widths. Targeted lint and web typecheck pass.

PR base: wrapping task label	Current PR: single-line task label

Loading and syncing now keep the combined banner behavior: the status stays attached, notices peek behind it, and task controls stay hidden until the thread is up to date. Stash keeps its separate tab. Verified loading and syncing with and without tasks, notice expansion, narrow layouts, and reduced motion. All 64 focused tests, web typecheck, and targeted lint passed.

Earlier iteration: separate status row, tasks visible	Current PR: combined banner, tasks hidden

Narrow layout · Spinner recording

The stash placement update passed 61 focused tests, web typecheck, and targeted lint. Browser checks covered notices, expanded tasks, notice stacks, loading, narrow questions, compact-composer expansion, restoring a prompt, deleting the last entry, and the empty composer. This changes the shared web/desktop composer; native clients are unchanged.

Earlier iteration: stash in footer	Current PR: separate stash tab

With Stash closed, its tab stays beside the update notice:

Opening Stash shows the saved drafts in a drawer across the top of the composer, covering the notice underneath. Closing Stash reveals the notice again:

Expanded tasks keep their own panel beside Stash:

The task-list cleanup passed 218 focused tests, web typecheck, and targeted lint. Browser checks covered composer task expansion/collapse, command-group expansion, and completed turns. The working timer is unchanged. This uses the shared web/desktop timeline; native clients, providers, and wire contracts are unchanged.

Earlier restore: duplicate task checklist	Current PR: tasks only in the composer

The composer task list still expands beside Stash:

Note

Restore unified activity logs and rebuild composer banner system

• Removes turn-plan timeline rows and the MAX_VISIBLE_WORK_LOG_ENTRIES cap/overflow toggle, so work log entries are always shown in unified activity groups instead of being collapsed behind '+N previous …'
• Introduces a new update action type in ToolGroupAction for non-tool entries, with standalone rows for agent spawns and error-toned entries that bypass grouping
• Replaces ad-hoc composer layout with a new ComposerBanner, ComposerBannerStack, and ComposerSurface primitive system; tasks, stash, pending approvals, and server update notices all render through these shared components
• Integrates tasks progress into the banner stack (no longer dismissible per-turn) and adds a ComposerServerUpdateStatus component with dismissal support for failed update states
• Risk: ChatComposerProps replaces externalDrawerAttached with bannerItems and adds threadSyncPhase; ComposerStashBadge removes the placement prop; ComposerTasksBadge removes onDismiss and hasTrailingShoulder; deriveTurnPlans is deleted and deriveTimelineEntries no longer accepts turn plans — any out-of-tree callers of these APIs will break

^{Macroscope summarized cfb3851.}

---

Note

Medium Risk
Large, user-facing composer and timeline refactor with prop/API removals (externalDrawerAttached, task dismiss, turn plans); behavior changes for notices, sync, and work-log grouping are easy to miss in edge cases.

Overview
Restores unified timeline activity grouping and rebuilds the chat composer around shared ComposerSurface / ComposerBanner primitives.

Work log rendering drops the per-group visibility cap and turn-plan timeline rows. Mixed runs collapse into one expandable summary (including non-tool updates), while agent spawns and error-toned entries stay standalone. deriveTimelineEntries no longer takes turn plans.

Composer notices, thread sync, task progress, stash, approvals, and command/stash drawers all attach through ComposerBannerStack with explicit priority (activity / urgent / notice) instead of manual urgent/calm splits in ChatView. Banners move from above the glass shell into ChatComposer via bannerItems; threadSyncPhase suppresses task UI until sync finishes and can show ComposerActivityRow in the stack. Task progress is derived from the current turn’sactivePlan (not sidebar planProgress); per-turn task dismiss is removed. Stash is a shoulder tab only (no inline/footer variant). Server-update banners use ComposerServerUpdateStatus and can dismiss failed updates. shoulderTabReserve and the extra overlay mutation observer are removed—scroll clearance uses full composer height. BranchToolbar uses ComposerSurface.ContextStrip.

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

[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: f3a66e84-043e-4bc3-b47b-654eccf47321

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	+9 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−5 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	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.4 KiB	13.3 KiB	−16 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 8b817cb · PR result: 35e6b66 · 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]

UI consistency review found 2 issues in the new composer banner primitives. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The removed CollapsiblePanel className="px-3 sm:px-4" carried a comment explaining that the panel clips its content while the height animates, so the option buttons have to sit inside that padding or their focus rings get shaved. ComposerBanner.Body only supplies padding-inline-start, so the w-full option buttons now touch the panel's inline-end and block-end edges and their focus-visible:ring-1 is clipped by overflow-hidden. Restoring end/bottom padding inside the clipped box keeps the ring visible.

Suggested change

	<ComposerBanner.Body>
	<ComposerBanner.BodyclassName="pb-1 pe-1">

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This XXL change replaces shared composer and timeline behavior across many production paths, including notice stacking, task and sync visibility, activity grouping, and layout measurement. Several unresolved findings also identify interaction, accessibility, loading-state, and test-coverage regressions that require focused human review.

Not approved because:

• 3 blocking correctness issues found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[CDVolvik]

Verified fix(web): restore unified activity logs and composer banners at 39283f4 as CDVolvik.

Restores #8693 after #8733 revert — git diff 33 files +1506/-2094 identical to original. Activity logs: MessagesTimeline working row removed, work entries grouped contiguously, ChatView active task progress tied to activePlan of current turn, ChatComposer exposes bannerItems/isWorking. Composer banners: ComposerSurface/Banner primitives, priority activity<urgent<notice, custom tasks content, accessible peek. Tests: MessagesTimeline.logic+session-logic+versionSkew+ChatView.logic 194/194, MessagesTimeline 37/37 pass. Note per PR: Compact/dismiss alignment and banner padding not fixed yet — author defers to Julius — hold merge until follow-up. Otherwise LGTM, no push.

[macroscopeapp]

🟡 Mediumchat/ComposerBanner.tsx:94

When the notice stack is expanded, the Peek button remains pointer-interactive and keyboard-focusable despite receiving opacity-0, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply pointer-events-none and disabled (or omit it from the DOM) while the stack is expanded.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ComposerBanner.tsx around line 94:
When the notice stack is expanded, the `Peek` button remains pointer-interactive and keyboard-focusable despite receiving `opacity-0`, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply `pointer-events-none` and `disabled` (or omit it from the DOM) while the stack is expanded.

[macroscopeapp]

🟡 Mediumchat/ChatComposer.tsx:3602

ComposerTasksBadge and ComposerTasksDrawer no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.

Also found in 2 other location(s)

apps/web/src/components/chat/ComposerTasksBadge.tsx:112

ComposerTasksBadge no longer accepts or renders an onDismiss action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.

apps/web/src/components/chat/ComposerTasksBadge.tsx:232

ComposerTasksDrawer no longer accepts or renders the former onDismiss action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed dismissTasks to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ChatComposer.tsx around line 3602:
`ComposerTasksBadge` and `ComposerTasksDrawer` no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.
Also found in 2 other location(s):
- apps/web/src/components/chat/ComposerTasksBadge.tsx:112 -- `ComposerTasksBadge` no longer accepts or renders an `onDismiss` action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.
- apps/web/src/components/chat/ComposerTasksBadge.tsx:232 -- `ComposerTasksDrawer` no longer accepts or renders the former `onDismiss` action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed `dismissTasks` to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

[macroscopeapp]

UI consistency review of the restored composer banner/surface system. Three findings below; the two findings posted on the previous head (ComposerBanner.ToggleIcon inheriting the coarse-pointer hit-target pseudo-element, and ComposerBanner.Body losing the clipped panel's end/bottom padding) are still open on this head and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Notices with a description now bind both the icon and the action/dismiss controls to the titleRow, with the description rendered as a separate row underneath (ComposerBanner.Children). That reproduces the alignment regression this PR's description acknowledges as the reason #8693 was reverted: Compact / dismiss sit on the title line instead of being centered against the whole title + description block.

The primitive it replaced did this in one row: Alert (controlAlignment: "center") lays out icon | title+description column | actions in a single items-center flex row, so the controls center against the full block and only opt into first-line alignment explicitly.

Smallest fix: keep the description inside the same Row's ComposerBanner.Content (stacked, e.g. className="flex-col items-start gap-0.5" with the title span keeping font-medium) and reserve ComposerBanner.Children for item.children, so the row's items-center centers the icon and actions over both lines. The other half of the revert — banner edge padding, now p-1 on ComposerBanner.Root versus the old px-3 pt-2 sm:px-4 — belongs on Root rather than at each call site.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Attachment hardcodes the drawer inset (w-[calc(100%-2.75rem)], max-w-[45.25rem]), while this PR deletes the only declaration of --chat-composer-drawer-inset: 1.375rem from index.css. That variable still has an imperative consumer: ComposerCommandMenuLayer reads it with getComputedStyle(form ?? anchor).getPropertyValue("--chat-composer-drawer-inset") (ChatComposer.tsx:233) to compute the command menu's left and width. The read now always resolves to "" and silently takes the || 1.375 fallback, so the menu lines up only because 2.75rem happens to be twice that fallback, and the two owners will drift the next time this width changes.

Suggest keeping one owner: declare [--chat-composer-drawer-inset:1.375rem] on an ancestor the composer form inherits from (ComposerSurface.Shell) and derive the widths here from it, e.g. w-[calc(100%-2*var(--chat-composer-drawer-inset))] max-w-[calc(48rem-2*var(--chat-composer-drawer-inset))].

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This test was dropped when the working row left the timeline, but the follow-up commit restored WorkingTimelineRow/ThinkingActivityRow and the activeTurnStartedAt prop, and LiveActivityContent still emits gap-1.5 py-0.5 px-1 for the iconless variant — so the assertions still hold and the restored row is now unguarded, right as this PR reworks neighbouring row indentation (TurnPlanTimelineRow's chevron column and pl-6 → pl-8). Suggest restoring it as-is.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration at fe1774e. One new finding below (list semantics lost in the tasks/stash list migration). The findings from my earlier reviews on this PR are still open and are not reposted here:

• ComposerBannerStack.tsx — description notices bind icon/actions to the title row, so Compact/dismiss no longer center against the title + description block.
• ComposerBanner.tsxAttachment — hardcoded inset while --chat-composer-drawer-inset is deleted from index.css, leaving ComposerCommandMenuLayer's getPropertyValue read resolving to "".
• ComposerBanner.tsxToggleIcon — decorative aria-hidden span inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 hit overlay inside Row render={<button/>}.
• ComposerPendingUserInputPanel.tsx — ComposerBanner.Body supplies only inline-start padding, so option-button focus rings are clipped by the animating CollapsiblePanel.
• MessagesTimeline.test.tsx — the iconless Thinking/working-timer alignment test is still dropped while the row it covered is restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The task list loses its list semantics in this migration: the old drawer rendered role="list" + role="listitem" explicitly (the deleted ComposerTasksBadge.test.tsx asserted both), while this <ul> relies on implicit roles. Tailwind's preflight sets list-style: none on ul, which makes WebKit drop the list role — and with it the aria-label on this container, since a generic element's label is not announced. Suggest re-asserting the role on the container (the li children keep listitem once the list role is explicit). ComposerStashMenu.tsx:133 has the same shape (render={<ul />} with aria-label="Stashed prompts") and needs the same fix.

Suggested change

	>
	render={<ulrole="list"/>}

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c0d3d53. Configure here.}

[macroscopeapp]

Reviewed the two new commits (c0d3d53 restoring the sync status, 4977016 moving the stash tab into the banner dock) plus the surrounding banner/surface migration.

One new finding on the restored ThreadSyncStatusPill (inline). The findings from earlier runs on this PR still apply at 4977016 and are not repeated here:

• ComposerBanner.ToggleIcon inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 overlay on a decorative span.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus-visible ring is clipped by the collapsible panel's overflow-hidden (ComposerPendingUserInputPanel.tsx:203-262).
• ComposerBannerStackAlert binds actions/dismiss to the title row while the description renders as a separate row, so controls are no longer centered against the title + description block.
• The tasks list (ComposerBanner.Children render={<ul />}) relies on implicit list semantics, which Tailwind preflight's list-style: none drops in WebKit along with the container aria-label.
• apps/web/src/components/chat/MessagesTimeline.test.tsx still drops the working/thinking row assertions even though WorkingTimelineRow was restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

🟡 Mediumcomponents/ChatView.tsx:4556

activeComposerTasksProgress returns null while thread details are loading because it now derives entirely from activePlan, which reads threadActivities — but buildLoadingThreadFromShell forces activities: [] during the loading window. The previous code fell back to activeThreadShell?.planProgress, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.

Consider falling back to activeThreadShell?.planProgress when activePlan is null and the thread is still loading, so the shell-level progress remains visible during that window.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/ChatView.tsx around line 4556:
`activeComposerTasksProgress` returns `null` while thread details are loading because it now derives entirely from `activePlan`, which reads `threadActivities` — but `buildLoadingThreadFromShell` forces `activities: []` during the loading window. The previous code fell back to `activeThreadShell?.planProgress`, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.
Consider falling back to `activeThreadShell?.planProgress` when `activePlan` is `null` and the thread is still loading, so the shell-level progress remains visible during that window.

[macroscopeapp]

One new finding in this push's neighbourhood: the composer server-update notice lost the live/failure indicator that ServerUpdateProgress used to own, and now shows a static InfoIcon even in the error variant. Previously reported findings on the earlier commits (banner Attachment inset vs. the deleted --chat-composer-drawer-inset, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body end/bottom padding, notice description/action alignment, ThreadSyncStatusPill bypassing the banner row grid, task-list role="list", and the dropped working-row alignment test) still apply and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This notice now uses a static InfoIcon for all three states, which drops the only live cue for a running update and puts an info icon on an error-variant banner. The removed code explained why: ServerUpdateProgress carried a pulsing dot while running and a destructive dot on failure, and only the idle offer needed an icon. ComposerServerUpdateStatus renders text only, so the pulse is gone and the failed row reads as informational next to the sibling notices that do pick situational icons (WifiOffIcon, AlarmClockIcon, GitBranchIcon) and a pulsing dot for live states.

Suggest keeping InfoIcon for the idle offer and restoring the dots for the other two states (ComposerBanner.Dot exists for exactly this and currently has no consumer, if you prefer routing it through the primitive):

Suggested change

	icon: <InfoIconaria-hidden/>,
	icon: updateInProgress ? (
	<span
	className="size-1.5 animate-status-pulse rounded-full bg-foreground"
	aria-hidden="true"
	/>
	) : updateFailed ? (
	<spanclassName="size-1.5 rounded-full bg-destructive"aria-hidden="true"/>
	) : (
	<InfoIconaria-hidden/>
	),

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration again against the new commit (53c1702, "restore combined loading and syncing banners").

The sync status now composes ComposerBanner.Row / Icon / Content (ComposerActivityStatus.tsx), which resolves the icon-column misalignment flagged on 4977016. One new finding below on the verification gate for the primitives this PR introduces.

Findings raised on earlier commits that are still present at this head (not re-posted):

• ComposerBanner.ToggleIcon inherits the full buttonVariants base, including the pointer-coarse 44x44 ::after hit box, inside rows that are themselves buttons.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus rings are clipped by the animating CollapsiblePanel.
• The task list relies on implicit ul/li roles after Preflight's list-style: none, dropping the list role and its aria-label in WebKit.
• Notice descriptions render as a second row, so actions/dismiss align to the title line instead of the whole block.
• ComposerCommandMenuLayer still reads --chat-composer-drawer-inset, whose only declaration this PR deletes.
• ChatView's server-update notice uses a static InfoIcon for running/failed/idle states.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

ComposerBanner and ComposerSurface now own the behaviors that four deleted test files pinned — attachment seam and placement (attached vs floating), per-variant outline/tint, stack-cap severity, tab vs inline rendering, and the sync status row — while ComposerBannerStack.test.tsx, ComposerStashBadge.test.tsx, ComposerTasksBadge.test.tsx and ThreadSyncStatusPill.test.tsx are removed and assertions are trimmed from ComposerCommandMenu.test.tsx / ComposerStashMenu.test.tsx. Nothing in apps/web renders ComposerBanner or ComposerSurface in a test, so the migrated contracts are unpinned.

This commit adds one more untested contract right here: width defaulting ("content" collapses to w-fit max-w-full flex-none and drops @container, so Row layout="wrap-actions" silently loses its container queries), plus the ChatComposer swap where threadSyncPhase suppresses activeTasksProgress/activeTaskSteps and takes the stack's attached slot.

Suggest a focused renderToStaticMarkup test for ComposerBanner.Root/Row covering attached vs floating placement, each variant's outline/tint tokens, and both width values, so these behaviors stay pinned the way the replaced components were.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency: one new finding on the latest push (combined loading/syncing banner). The earlier ThreadSyncStatusPill hand-rolled-row finding is resolved — ComposerActivityRow now composes Row/Icon/Content and shares the --composer-banner-icon-column grid. Findings from previous runs on this PR (server-update InfoIcon, banner description/action alignment, missing role="list" on the migrated task and stash lists, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body dropping the clipped panel's end/bottom padding, the deleted --chat-composer-drawer-inset declaration still read by ComposerCommandMenuLayer, and the removed Thinking-row test) are still open and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Peek is now the only pointer affordance for revealing the hidden notices, but its hit area is the 12px cap itself (h-3). ComposerBannerStack skips onPointerEnter when event.pointerType === "touch" and collapses the stack on onPointerDownCapture over the front banner, so on a coarse pointer this 12px strip is the only way to open the stack — before this PR any tap inside group/banner-stack revealed it through hover/focus-within. Elsewhere the system guarantees coarse pointers a 44px box (buttonVariants' pointer-coarse:after:min-h-11).

Suggest growing the tappable box upward only, so it stays clear of the front banner's dismiss/actions directly below:

Suggested change

	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"pointer-coarse:before:absolute pointer-coarse:before:inset-x-0 pointer-coarse:before:bottom-0 pointer-coarse:before:h-8",

^{Posted via Macroscope — UI Consistency}

[t3dotgg]

Restores the activity log grouping and shared composer banners from #8693 after #8733, while deferring the composer-attached working timer.

Working for keeps main's placement in the conversation timeline, including the current task label, Thinking state, and turn lifecycle. Long task labels truncate to one line while the timer remains fully visible. The composer keeps the restored task controls, notice stacking, and shared Tailwind components. Task progress appears only in the composer; the duplicate timeline checklist is removed. Plan proposals remain in the timeline. Stash stays in its own tab beside notices and expanded task lists, including compact layouts; its footer variant is removed. Loading and syncing use the shared banner stack and hide task controls until the thread is up to date. Their spinner respects reduced-motion preferences.

Rebased onto current main, including interim response folding and the latest failed-tool icon fix. Orchestrator V2 and queueing are deferred until this main-targeted PR is merged.

All after screenshots below were recaptured from 35e6b6653e95. The timeline comparisons render the same scripted events through the actual timeline components from the PR base, 8b817cbcaad7, and the current PR. Each pair uses matching viewport dimensions. Completed-turn folds are open in both versions; the mixed activity group is shown both collapsed and expanded. The composer comparisons retain their earlier-iteration before images, labelled separately.

Mixed command, file-read, and status entries now get one useful summary. Main already summarized tool-only groups; the improvement here is that mixed groups use that presentation too.

PR base: last command and hidden log entries	Current PR: summary of the whole group

Expanding that same group keeps the summary and shows compact detail rows, without separate Work Log headings.

PR base: expanded mixed log	Current PR: expanded activity group

Task updates no longer add Plan updated rows or a second checklist to the timeline. Commands stay in one group; task controls remain in the composer.

PR base: plan chatter and timeline checklist	Current PR: one command group, no duplicate tasks

The earlier error screenshot incorrectly modeled a failed test as a runtime error. These two corrected scenarios use the server's actual event conversion and payload projection.

Failed command followed by a successful retry — unchanged. A test exits with code 1, the fixture is edited, and the test reruns successfully. All three tool calls stay in one group on both the PR base and this branch. A nonzero command exit code does not split the group, and no failure-count prefix is added.

PR base: failed test and retry in one group	Current PR: same grouping

Expanding the group and failed command reveals the failure output in both versions:

PR base: failed command details	Current PR: same failure details

Provider crash at the end of a run. Two commands finish, then the provider exits unexpectedly and the turn ends. There are no commands continuing after the crash in this fixture. The base already shows the terminal runtime error; this PR gives the preceding commands their own summary and renders the error as a separate row.

PR base: terminal error with previous tool calls	Current PR: command summary followed by runtime error

The outer Worked for fold is open in every comparison. Collapsing that fold can still hide the error. The grouping boundary applies to error events, such as runtime failures, rather than ordinary failed tool results. This update corrects the evidence; it does not change production behavior.

The initial restore passed 242 focused web tests, web typecheck, and targeted lint. Checked the isolated fixture playground in the browser, including running/idle turns, task expansion, loading/syncing, notices, approvals, and stash. Stopping a turn removes the timer; deleting the last stashed prompt closes the stash. Preview fixtures remain local and are not part of the PR.

Earlier restore: attached timer	Current PR: timeline timer, tasks only in composer

Long task labels checked at 1440px and 768px viewport widths. Targeted lint and web typecheck pass.

PR base: wrapping task label	Current PR: single-line task label

Loading and syncing now keep the combined banner behavior: the status stays attached, notices peek behind it, and task controls stay hidden until the thread is up to date. Stash keeps its separate tab. Verified loading and syncing with and without tasks, notice expansion, narrow layouts, and reduced motion. All 64 focused tests, web typecheck, and targeted lint passed.

Earlier iteration: separate status row, tasks visible	Current PR: combined banner, tasks hidden

Narrow layout · Spinner recording

The stash placement update passed 61 focused tests, web typecheck, and targeted lint. Browser checks covered notices, expanded tasks, notice stacks, loading, narrow questions, compact-composer expansion, restoring a prompt, deleting the last entry, and the empty composer. This changes the shared web/desktop composer; native clients are unchanged.

Earlier iteration: stash in footer	Current PR: separate stash tab

With Stash closed, its tab stays beside the update notice:

Opening Stash shows the saved drafts in a drawer across the top of the composer, covering the notice underneath. Closing Stash reveals the notice again:

Expanded tasks keep their own panel beside Stash:

The task-list cleanup passed 218 focused tests, web typecheck, and targeted lint. Browser checks covered composer task expansion/collapse, command-group expansion, and completed turns. The working timer is unchanged. This uses the shared web/desktop timeline; native clients, providers, and wire contracts are unchanged.

Earlier restore: duplicate task checklist	Current PR: tasks only in the composer

The composer task list still expands beside Stash:

Note

Restore unified activity logs and rebuild composer banner system

• Removes turn-plan timeline rows and the MAX_VISIBLE_WORK_LOG_ENTRIES cap/overflow toggle, so work log entries are always shown in unified activity groups instead of being collapsed behind '+N previous …'
• Introduces a new update action type in ToolGroupAction for non-tool entries, with standalone rows for agent spawns and error-toned entries that bypass grouping
• Replaces ad-hoc composer layout with a new ComposerBanner, ComposerBannerStack, and ComposerSurface primitive system; tasks, stash, pending approvals, and server update notices all render through these shared components
• Integrates tasks progress into the banner stack (no longer dismissible per-turn) and adds a ComposerServerUpdateStatus component with dismissal support for failed update states
• Risk: ChatComposerProps replaces externalDrawerAttached with bannerItems and adds threadSyncPhase; ComposerStashBadge removes the placement prop; ComposerTasksBadge removes onDismiss and hasTrailingShoulder; deriveTurnPlans is deleted and deriveTimelineEntries no longer accepts turn plans — any out-of-tree callers of these APIs will break

^{Macroscope summarized cfb3851.}

---

Note

Medium Risk
Large, user-facing composer and timeline refactor with prop/API removals (externalDrawerAttached, task dismiss, turn plans); behavior changes for notices, sync, and work-log grouping are easy to miss in edge cases.

Overview
Restores unified timeline activity grouping and rebuilds the chat composer around shared ComposerSurface / ComposerBanner primitives.

Work log rendering drops the per-group visibility cap and turn-plan timeline rows. Mixed runs collapse into one expandable summary (including non-tool updates), while agent spawns and error-toned entries stay standalone. deriveTimelineEntries no longer takes turn plans.

Composer notices, thread sync, task progress, stash, approvals, and command/stash drawers all attach through ComposerBannerStack with explicit priority (activity / urgent / notice) instead of manual urgent/calm splits in ChatView. Banners move from above the glass shell into ChatComposer via bannerItems; threadSyncPhase suppresses task UI until sync finishes and can show ComposerActivityRow in the stack. Task progress is derived from the current turn’sactivePlan (not sidebar planProgress); per-turn task dismiss is removed. Stash is a shoulder tab only (no inline/footer variant). Server-update banners use ComposerServerUpdateStatus and can dismiss failed updates. shoulderTabReserve and the extra overlay mutation observer are removed—scroll clearance uses full composer height. BranchToolbar uses ComposerSurface.ContextStrip.

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

[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: f3a66e84-043e-4bc3-b47b-654eccf47321

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	+9 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−5 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	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.4 KiB	13.3 KiB	−16 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 8b817cb · PR result: 35e6b66 · 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]

UI consistency review found 2 issues in the new composer banner primitives. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The removed CollapsiblePanel className="px-3 sm:px-4" carried a comment explaining that the panel clips its content while the height animates, so the option buttons have to sit inside that padding or their focus rings get shaved. ComposerBanner.Body only supplies padding-inline-start, so the w-full option buttons now touch the panel's inline-end and block-end edges and their focus-visible:ring-1 is clipped by overflow-hidden. Restoring end/bottom padding inside the clipped box keeps the ring visible.

Suggested change

	<ComposerBanner.Body>
	<ComposerBanner.BodyclassName="pb-1 pe-1">

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This XXL change replaces shared composer and timeline behavior across many production paths, including notice stacking, task and sync visibility, activity grouping, and layout measurement. Several unresolved findings also identify interaction, accessibility, loading-state, and test-coverage regressions that require focused human review.

Not approved because:

• 3 blocking correctness issues found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[CDVolvik]

Verified fix(web): restore unified activity logs and composer banners at 39283f4 as CDVolvik.

Restores #8693 after #8733 revert — git diff 33 files +1506/-2094 identical to original. Activity logs: MessagesTimeline working row removed, work entries grouped contiguously, ChatView active task progress tied to activePlan of current turn, ChatComposer exposes bannerItems/isWorking. Composer banners: ComposerSurface/Banner primitives, priority activity<urgent<notice, custom tasks content, accessible peek. Tests: MessagesTimeline.logic+session-logic+versionSkew+ChatView.logic 194/194, MessagesTimeline 37/37 pass. Note per PR: Compact/dismiss alignment and banner padding not fixed yet — author defers to Julius — hold merge until follow-up. Otherwise LGTM, no push.

[macroscopeapp]

🟡 Mediumchat/ComposerBanner.tsx:94

When the notice stack is expanded, the Peek button remains pointer-interactive and keyboard-focusable despite receiving opacity-0, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply pointer-events-none and disabled (or omit it from the DOM) while the stack is expanded.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ComposerBanner.tsx around line 94:
When the notice stack is expanded, the `Peek` button remains pointer-interactive and keyboard-focusable despite receiving `opacity-0`, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply `pointer-events-none` and `disabled` (or omit it from the DOM) while the stack is expanded.

[macroscopeapp]

🟡 Mediumchat/ChatComposer.tsx:3602

ComposerTasksBadge and ComposerTasksDrawer no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.

Also found in 2 other location(s)

apps/web/src/components/chat/ComposerTasksBadge.tsx:112

ComposerTasksBadge no longer accepts or renders an onDismiss action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.

apps/web/src/components/chat/ComposerTasksBadge.tsx:232

ComposerTasksDrawer no longer accepts or renders the former onDismiss action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed dismissTasks to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ChatComposer.tsx around line 3602:
`ComposerTasksBadge` and `ComposerTasksDrawer` no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.
Also found in 2 other location(s):
- apps/web/src/components/chat/ComposerTasksBadge.tsx:112 -- `ComposerTasksBadge` no longer accepts or renders an `onDismiss` action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.
- apps/web/src/components/chat/ComposerTasksBadge.tsx:232 -- `ComposerTasksDrawer` no longer accepts or renders the former `onDismiss` action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed `dismissTasks` to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

[macroscopeapp]

UI consistency review of the restored composer banner/surface system. Three findings below; the two findings posted on the previous head (ComposerBanner.ToggleIcon inheriting the coarse-pointer hit-target pseudo-element, and ComposerBanner.Body losing the clipped panel's end/bottom padding) are still open on this head and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Notices with a description now bind both the icon and the action/dismiss controls to the titleRow, with the description rendered as a separate row underneath (ComposerBanner.Children). That reproduces the alignment regression this PR's description acknowledges as the reason #8693 was reverted: Compact / dismiss sit on the title line instead of being centered against the whole title + description block.

The primitive it replaced did this in one row: Alert (controlAlignment: "center") lays out icon | title+description column | actions in a single items-center flex row, so the controls center against the full block and only opt into first-line alignment explicitly.

Smallest fix: keep the description inside the same Row's ComposerBanner.Content (stacked, e.g. className="flex-col items-start gap-0.5" with the title span keeping font-medium) and reserve ComposerBanner.Children for item.children, so the row's items-center centers the icon and actions over both lines. The other half of the revert — banner edge padding, now p-1 on ComposerBanner.Root versus the old px-3 pt-2 sm:px-4 — belongs on Root rather than at each call site.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Attachment hardcodes the drawer inset (w-[calc(100%-2.75rem)], max-w-[45.25rem]), while this PR deletes the only declaration of --chat-composer-drawer-inset: 1.375rem from index.css. That variable still has an imperative consumer: ComposerCommandMenuLayer reads it with getComputedStyle(form ?? anchor).getPropertyValue("--chat-composer-drawer-inset") (ChatComposer.tsx:233) to compute the command menu's left and width. The read now always resolves to "" and silently takes the || 1.375 fallback, so the menu lines up only because 2.75rem happens to be twice that fallback, and the two owners will drift the next time this width changes.

Suggest keeping one owner: declare [--chat-composer-drawer-inset:1.375rem] on an ancestor the composer form inherits from (ComposerSurface.Shell) and derive the widths here from it, e.g. w-[calc(100%-2*var(--chat-composer-drawer-inset))] max-w-[calc(48rem-2*var(--chat-composer-drawer-inset))].

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This test was dropped when the working row left the timeline, but the follow-up commit restored WorkingTimelineRow/ThinkingActivityRow and the activeTurnStartedAt prop, and LiveActivityContent still emits gap-1.5 py-0.5 px-1 for the iconless variant — so the assertions still hold and the restored row is now unguarded, right as this PR reworks neighbouring row indentation (TurnPlanTimelineRow's chevron column and pl-6 → pl-8). Suggest restoring it as-is.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration at fe1774e. One new finding below (list semantics lost in the tasks/stash list migration). The findings from my earlier reviews on this PR are still open and are not reposted here:

• ComposerBannerStack.tsx — description notices bind icon/actions to the title row, so Compact/dismiss no longer center against the title + description block.
• ComposerBanner.tsxAttachment — hardcoded inset while --chat-composer-drawer-inset is deleted from index.css, leaving ComposerCommandMenuLayer's getPropertyValue read resolving to "".
• ComposerBanner.tsxToggleIcon — decorative aria-hidden span inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 hit overlay inside Row render={<button/>}.
• ComposerPendingUserInputPanel.tsx — ComposerBanner.Body supplies only inline-start padding, so option-button focus rings are clipped by the animating CollapsiblePanel.
• MessagesTimeline.test.tsx — the iconless Thinking/working-timer alignment test is still dropped while the row it covered is restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The task list loses its list semantics in this migration: the old drawer rendered role="list" + role="listitem" explicitly (the deleted ComposerTasksBadge.test.tsx asserted both), while this <ul> relies on implicit roles. Tailwind's preflight sets list-style: none on ul, which makes WebKit drop the list role — and with it the aria-label on this container, since a generic element's label is not announced. Suggest re-asserting the role on the container (the li children keep listitem once the list role is explicit). ComposerStashMenu.tsx:133 has the same shape (render={<ul />} with aria-label="Stashed prompts") and needs the same fix.

Suggested change

	>
	render={<ulrole="list"/>}

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c0d3d53. Configure here.}

[macroscopeapp]

Reviewed the two new commits (c0d3d53 restoring the sync status, 4977016 moving the stash tab into the banner dock) plus the surrounding banner/surface migration.

One new finding on the restored ThreadSyncStatusPill (inline). The findings from earlier runs on this PR still apply at 4977016 and are not repeated here:

• ComposerBanner.ToggleIcon inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 overlay on a decorative span.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus-visible ring is clipped by the collapsible panel's overflow-hidden (ComposerPendingUserInputPanel.tsx:203-262).
• ComposerBannerStackAlert binds actions/dismiss to the title row while the description renders as a separate row, so controls are no longer centered against the title + description block.
• The tasks list (ComposerBanner.Children render={<ul />}) relies on implicit list semantics, which Tailwind preflight's list-style: none drops in WebKit along with the container aria-label.
• apps/web/src/components/chat/MessagesTimeline.test.tsx still drops the working/thinking row assertions even though WorkingTimelineRow was restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

🟡 Mediumcomponents/ChatView.tsx:4556

activeComposerTasksProgress returns null while thread details are loading because it now derives entirely from activePlan, which reads threadActivities — but buildLoadingThreadFromShell forces activities: [] during the loading window. The previous code fell back to activeThreadShell?.planProgress, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.

Consider falling back to activeThreadShell?.planProgress when activePlan is null and the thread is still loading, so the shell-level progress remains visible during that window.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/ChatView.tsx around line 4556:
`activeComposerTasksProgress` returns `null` while thread details are loading because it now derives entirely from `activePlan`, which reads `threadActivities` — but `buildLoadingThreadFromShell` forces `activities: []` during the loading window. The previous code fell back to `activeThreadShell?.planProgress`, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.
Consider falling back to `activeThreadShell?.planProgress` when `activePlan` is `null` and the thread is still loading, so the shell-level progress remains visible during that window.

[macroscopeapp]

One new finding in this push's neighbourhood: the composer server-update notice lost the live/failure indicator that ServerUpdateProgress used to own, and now shows a static InfoIcon even in the error variant. Previously reported findings on the earlier commits (banner Attachment inset vs. the deleted --chat-composer-drawer-inset, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body end/bottom padding, notice description/action alignment, ThreadSyncStatusPill bypassing the banner row grid, task-list role="list", and the dropped working-row alignment test) still apply and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This notice now uses a static InfoIcon for all three states, which drops the only live cue for a running update and puts an info icon on an error-variant banner. The removed code explained why: ServerUpdateProgress carried a pulsing dot while running and a destructive dot on failure, and only the idle offer needed an icon. ComposerServerUpdateStatus renders text only, so the pulse is gone and the failed row reads as informational next to the sibling notices that do pick situational icons (WifiOffIcon, AlarmClockIcon, GitBranchIcon) and a pulsing dot for live states.

Suggest keeping InfoIcon for the idle offer and restoring the dots for the other two states (ComposerBanner.Dot exists for exactly this and currently has no consumer, if you prefer routing it through the primitive):

Suggested change

	icon: <InfoIconaria-hidden/>,
	icon: updateInProgress ? (
	<span
	className="size-1.5 animate-status-pulse rounded-full bg-foreground"
	aria-hidden="true"
	/>
	) : updateFailed ? (
	<spanclassName="size-1.5 rounded-full bg-destructive"aria-hidden="true"/>
	) : (
	<InfoIconaria-hidden/>
	),

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration again against the new commit (53c1702, "restore combined loading and syncing banners").

The sync status now composes ComposerBanner.Row / Icon / Content (ComposerActivityStatus.tsx), which resolves the icon-column misalignment flagged on 4977016. One new finding below on the verification gate for the primitives this PR introduces.

Findings raised on earlier commits that are still present at this head (not re-posted):

• ComposerBanner.ToggleIcon inherits the full buttonVariants base, including the pointer-coarse 44x44 ::after hit box, inside rows that are themselves buttons.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus rings are clipped by the animating CollapsiblePanel.
• The task list relies on implicit ul/li roles after Preflight's list-style: none, dropping the list role and its aria-label in WebKit.
• Notice descriptions render as a second row, so actions/dismiss align to the title line instead of the whole block.
• ComposerCommandMenuLayer still reads --chat-composer-drawer-inset, whose only declaration this PR deletes.
• ChatView's server-update notice uses a static InfoIcon for running/failed/idle states.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

ComposerBanner and ComposerSurface now own the behaviors that four deleted test files pinned — attachment seam and placement (attached vs floating), per-variant outline/tint, stack-cap severity, tab vs inline rendering, and the sync status row — while ComposerBannerStack.test.tsx, ComposerStashBadge.test.tsx, ComposerTasksBadge.test.tsx and ThreadSyncStatusPill.test.tsx are removed and assertions are trimmed from ComposerCommandMenu.test.tsx / ComposerStashMenu.test.tsx. Nothing in apps/web renders ComposerBanner or ComposerSurface in a test, so the migrated contracts are unpinned.

This commit adds one more untested contract right here: width defaulting ("content" collapses to w-fit max-w-full flex-none and drops @container, so Row layout="wrap-actions" silently loses its container queries), plus the ChatComposer swap where threadSyncPhase suppresses activeTasksProgress/activeTaskSteps and takes the stack's attached slot.

Suggest a focused renderToStaticMarkup test for ComposerBanner.Root/Row covering attached vs floating placement, each variant's outline/tint tokens, and both width values, so these behaviors stay pinned the way the replaced components were.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency: one new finding on the latest push (combined loading/syncing banner). The earlier ThreadSyncStatusPill hand-rolled-row finding is resolved — ComposerActivityRow now composes Row/Icon/Content and shares the --composer-banner-icon-column grid. Findings from previous runs on this PR (server-update InfoIcon, banner description/action alignment, missing role="list" on the migrated task and stash lists, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body dropping the clipped panel's end/bottom padding, the deleted --chat-composer-drawer-inset declaration still read by ComposerCommandMenuLayer, and the removed Thinking-row test) are still open and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Peek is now the only pointer affordance for revealing the hidden notices, but its hit area is the 12px cap itself (h-3). ComposerBannerStack skips onPointerEnter when event.pointerType === "touch" and collapses the stack on onPointerDownCapture over the front banner, so on a coarse pointer this 12px strip is the only way to open the stack — before this PR any tap inside group/banner-stack revealed it through hover/focus-within. Elsewhere the system guarantees coarse pointers a 44px box (buttonVariants' pointer-coarse:after:min-h-11).

Suggest growing the tappable box upward only, so it stays clear of the front banner's dismiss/actions directly below:

Suggested change

	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"pointer-coarse:before:absolute pointer-coarse:before:inset-x-0 pointer-coarse:before:bottom-0 pointer-coarse:before:h-8",

^{Posted via Macroscope — UI Consistency}

[t3dotgg]

Restores the activity log grouping and shared composer banners from #8693 after #8733, while deferring the composer-attached working timer.

Working for keeps main's placement in the conversation timeline, including the current task label, Thinking state, and turn lifecycle. Long task labels truncate to one line while the timer remains fully visible. The composer keeps the restored task controls, notice stacking, and shared Tailwind components. Task progress appears only in the composer; the duplicate timeline checklist is removed. Plan proposals remain in the timeline. Stash stays in its own tab beside notices and expanded task lists, including compact layouts; its footer variant is removed. Loading and syncing use the shared banner stack and hide task controls until the thread is up to date. Their spinner respects reduced-motion preferences.

Rebased onto current main, including interim response folding and the latest failed-tool icon fix. Orchestrator V2 and queueing are deferred until this main-targeted PR is merged.

All after screenshots below were recaptured from 35e6b6653e95. The timeline comparisons render the same scripted events through the actual timeline components from the PR base, 8b817cbcaad7, and the current PR. Each pair uses matching viewport dimensions. Completed-turn folds are open in both versions; the mixed activity group is shown both collapsed and expanded. The composer comparisons retain their earlier-iteration before images, labelled separately.

Mixed command, file-read, and status entries now get one useful summary. Main already summarized tool-only groups; the improvement here is that mixed groups use that presentation too.

PR base: last command and hidden log entries	Current PR: summary of the whole group

Expanding that same group keeps the summary and shows compact detail rows, without separate Work Log headings.

PR base: expanded mixed log	Current PR: expanded activity group

Task updates no longer add Plan updated rows or a second checklist to the timeline. Commands stay in one group; task controls remain in the composer.

PR base: plan chatter and timeline checklist	Current PR: one command group, no duplicate tasks

The earlier error screenshot incorrectly modeled a failed test as a runtime error. These two corrected scenarios use the server's actual event conversion and payload projection.

Failed command followed by a successful retry — unchanged. A test exits with code 1, the fixture is edited, and the test reruns successfully. All three tool calls stay in one group on both the PR base and this branch. A nonzero command exit code does not split the group, and no failure-count prefix is added.

PR base: failed test and retry in one group	Current PR: same grouping

Expanding the group and failed command reveals the failure output in both versions:

PR base: failed command details	Current PR: same failure details

Provider crash at the end of a run. Two commands finish, then the provider exits unexpectedly and the turn ends. There are no commands continuing after the crash in this fixture. The base already shows the terminal runtime error; this PR gives the preceding commands their own summary and renders the error as a separate row.

PR base: terminal error with previous tool calls	Current PR: command summary followed by runtime error

The outer Worked for fold is open in every comparison. Collapsing that fold can still hide the error. The grouping boundary applies to error events, such as runtime failures, rather than ordinary failed tool results. This update corrects the evidence; it does not change production behavior.

The initial restore passed 242 focused web tests, web typecheck, and targeted lint. Checked the isolated fixture playground in the browser, including running/idle turns, task expansion, loading/syncing, notices, approvals, and stash. Stopping a turn removes the timer; deleting the last stashed prompt closes the stash. Preview fixtures remain local and are not part of the PR.

Earlier restore: attached timer	Current PR: timeline timer, tasks only in composer

Long task labels checked at 1440px and 768px viewport widths. Targeted lint and web typecheck pass.

PR base: wrapping task label	Current PR: single-line task label

Loading and syncing now keep the combined banner behavior: the status stays attached, notices peek behind it, and task controls stay hidden until the thread is up to date. Stash keeps its separate tab. Verified loading and syncing with and without tasks, notice expansion, narrow layouts, and reduced motion. All 64 focused tests, web typecheck, and targeted lint passed.

Earlier iteration: separate status row, tasks visible	Current PR: combined banner, tasks hidden

Narrow layout · Spinner recording

The stash placement update passed 61 focused tests, web typecheck, and targeted lint. Browser checks covered notices, expanded tasks, notice stacks, loading, narrow questions, compact-composer expansion, restoring a prompt, deleting the last entry, and the empty composer. This changes the shared web/desktop composer; native clients are unchanged.

Earlier iteration: stash in footer	Current PR: separate stash tab

With Stash closed, its tab stays beside the update notice:

Opening Stash shows the saved drafts in a drawer across the top of the composer, covering the notice underneath. Closing Stash reveals the notice again:

Expanded tasks keep their own panel beside Stash:

The task-list cleanup passed 218 focused tests, web typecheck, and targeted lint. Browser checks covered composer task expansion/collapse, command-group expansion, and completed turns. The working timer is unchanged. This uses the shared web/desktop timeline; native clients, providers, and wire contracts are unchanged.

Earlier restore: duplicate task checklist	Current PR: tasks only in the composer

The composer task list still expands beside Stash:

Note

Restore unified activity logs and rebuild composer banner system

• Removes turn-plan timeline rows and the MAX_VISIBLE_WORK_LOG_ENTRIES cap/overflow toggle, so work log entries are always shown in unified activity groups instead of being collapsed behind '+N previous …'
• Introduces a new update action type in ToolGroupAction for non-tool entries, with standalone rows for agent spawns and error-toned entries that bypass grouping
• Replaces ad-hoc composer layout with a new ComposerBanner, ComposerBannerStack, and ComposerSurface primitive system; tasks, stash, pending approvals, and server update notices all render through these shared components
• Integrates tasks progress into the banner stack (no longer dismissible per-turn) and adds a ComposerServerUpdateStatus component with dismissal support for failed update states
• Risk: ChatComposerProps replaces externalDrawerAttached with bannerItems and adds threadSyncPhase; ComposerStashBadge removes the placement prop; ComposerTasksBadge removes onDismiss and hasTrailingShoulder; deriveTurnPlans is deleted and deriveTimelineEntries no longer accepts turn plans — any out-of-tree callers of these APIs will break

^{Macroscope summarized cfb3851.}

---

Note

Medium Risk
Large, user-facing composer and timeline refactor with prop/API removals (externalDrawerAttached, task dismiss, turn plans); behavior changes for notices, sync, and work-log grouping are easy to miss in edge cases.

Overview
Restores unified timeline activity grouping and rebuilds the chat composer around shared ComposerSurface / ComposerBanner primitives.

Work log rendering drops the per-group visibility cap and turn-plan timeline rows. Mixed runs collapse into one expandable summary (including non-tool updates), while agent spawns and error-toned entries stay standalone. deriveTimelineEntries no longer takes turn plans.

Composer notices, thread sync, task progress, stash, approvals, and command/stash drawers all attach through ComposerBannerStack with explicit priority (activity / urgent / notice) instead of manual urgent/calm splits in ChatView. Banners move from above the glass shell into ChatComposer via bannerItems; threadSyncPhase suppresses task UI until sync finishes and can show ComposerActivityRow in the stack. Task progress is derived from the current turn’sactivePlan (not sidebar planProgress); per-turn task dismiss is removed. Stash is a shoulder tab only (no inline/footer variant). Server-update banners use ComposerServerUpdateStatus and can dismiss failed updates. shoulderTabReserve and the extra overlay mutation observer are removed—scroll clearance uses full composer height. BranchToolbar uses ComposerSurface.ContextStrip.

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

[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: f3a66e84-043e-4bc3-b47b-654eccf47321

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	+9 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−5 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	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.4 KiB	13.3 KiB	−16 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 8b817cb · PR result: 35e6b66 · 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]

UI consistency review found 2 issues in the new composer banner primitives. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The removed CollapsiblePanel className="px-3 sm:px-4" carried a comment explaining that the panel clips its content while the height animates, so the option buttons have to sit inside that padding or their focus rings get shaved. ComposerBanner.Body only supplies padding-inline-start, so the w-full option buttons now touch the panel's inline-end and block-end edges and their focus-visible:ring-1 is clipped by overflow-hidden. Restoring end/bottom padding inside the clipped box keeps the ring visible.

Suggested change

	<ComposerBanner.Body>
	<ComposerBanner.BodyclassName="pb-1 pe-1">

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This XXL change replaces shared composer and timeline behavior across many production paths, including notice stacking, task and sync visibility, activity grouping, and layout measurement. Several unresolved findings also identify interaction, accessibility, loading-state, and test-coverage regressions that require focused human review.

Not approved because:

• 3 blocking correctness issues found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[CDVolvik]

Verified fix(web): restore unified activity logs and composer banners at 39283f4 as CDVolvik.

Restores #8693 after #8733 revert — git diff 33 files +1506/-2094 identical to original. Activity logs: MessagesTimeline working row removed, work entries grouped contiguously, ChatView active task progress tied to activePlan of current turn, ChatComposer exposes bannerItems/isWorking. Composer banners: ComposerSurface/Banner primitives, priority activity<urgent<notice, custom tasks content, accessible peek. Tests: MessagesTimeline.logic+session-logic+versionSkew+ChatView.logic 194/194, MessagesTimeline 37/37 pass. Note per PR: Compact/dismiss alignment and banner padding not fixed yet — author defers to Julius — hold merge until follow-up. Otherwise LGTM, no push.

[macroscopeapp]

🟡 Mediumchat/ComposerBanner.tsx:94

When the notice stack is expanded, the Peek button remains pointer-interactive and keyboard-focusable despite receiving opacity-0, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply pointer-events-none and disabled (or omit it from the DOM) while the stack is expanded.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ComposerBanner.tsx around line 94:
When the notice stack is expanded, the `Peek` button remains pointer-interactive and keyboard-focusable despite receiving `opacity-0`, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply `pointer-events-none` and `disabled` (or omit it from the DOM) while the stack is expanded.

[macroscopeapp]

🟡 Mediumchat/ChatComposer.tsx:3602

ComposerTasksBadge and ComposerTasksDrawer no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.

Also found in 2 other location(s)

apps/web/src/components/chat/ComposerTasksBadge.tsx:112

ComposerTasksBadge no longer accepts or renders an onDismiss action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.

apps/web/src/components/chat/ComposerTasksBadge.tsx:232

ComposerTasksDrawer no longer accepts or renders the former onDismiss action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed dismissTasks to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ChatComposer.tsx around line 3602:
`ComposerTasksBadge` and `ComposerTasksDrawer` no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.
Also found in 2 other location(s):
- apps/web/src/components/chat/ComposerTasksBadge.tsx:112 -- `ComposerTasksBadge` no longer accepts or renders an `onDismiss` action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.
- apps/web/src/components/chat/ComposerTasksBadge.tsx:232 -- `ComposerTasksDrawer` no longer accepts or renders the former `onDismiss` action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed `dismissTasks` to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

[macroscopeapp]

UI consistency review of the restored composer banner/surface system. Three findings below; the two findings posted on the previous head (ComposerBanner.ToggleIcon inheriting the coarse-pointer hit-target pseudo-element, and ComposerBanner.Body losing the clipped panel's end/bottom padding) are still open on this head and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Notices with a description now bind both the icon and the action/dismiss controls to the titleRow, with the description rendered as a separate row underneath (ComposerBanner.Children). That reproduces the alignment regression this PR's description acknowledges as the reason #8693 was reverted: Compact / dismiss sit on the title line instead of being centered against the whole title + description block.

The primitive it replaced did this in one row: Alert (controlAlignment: "center") lays out icon | title+description column | actions in a single items-center flex row, so the controls center against the full block and only opt into first-line alignment explicitly.

Smallest fix: keep the description inside the same Row's ComposerBanner.Content (stacked, e.g. className="flex-col items-start gap-0.5" with the title span keeping font-medium) and reserve ComposerBanner.Children for item.children, so the row's items-center centers the icon and actions over both lines. The other half of the revert — banner edge padding, now p-1 on ComposerBanner.Root versus the old px-3 pt-2 sm:px-4 — belongs on Root rather than at each call site.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Attachment hardcodes the drawer inset (w-[calc(100%-2.75rem)], max-w-[45.25rem]), while this PR deletes the only declaration of --chat-composer-drawer-inset: 1.375rem from index.css. That variable still has an imperative consumer: ComposerCommandMenuLayer reads it with getComputedStyle(form ?? anchor).getPropertyValue("--chat-composer-drawer-inset") (ChatComposer.tsx:233) to compute the command menu's left and width. The read now always resolves to "" and silently takes the || 1.375 fallback, so the menu lines up only because 2.75rem happens to be twice that fallback, and the two owners will drift the next time this width changes.

Suggest keeping one owner: declare [--chat-composer-drawer-inset:1.375rem] on an ancestor the composer form inherits from (ComposerSurface.Shell) and derive the widths here from it, e.g. w-[calc(100%-2*var(--chat-composer-drawer-inset))] max-w-[calc(48rem-2*var(--chat-composer-drawer-inset))].

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This test was dropped when the working row left the timeline, but the follow-up commit restored WorkingTimelineRow/ThinkingActivityRow and the activeTurnStartedAt prop, and LiveActivityContent still emits gap-1.5 py-0.5 px-1 for the iconless variant — so the assertions still hold and the restored row is now unguarded, right as this PR reworks neighbouring row indentation (TurnPlanTimelineRow's chevron column and pl-6 → pl-8). Suggest restoring it as-is.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration at fe1774e. One new finding below (list semantics lost in the tasks/stash list migration). The findings from my earlier reviews on this PR are still open and are not reposted here:

• ComposerBannerStack.tsx — description notices bind icon/actions to the title row, so Compact/dismiss no longer center against the title + description block.
• ComposerBanner.tsxAttachment — hardcoded inset while --chat-composer-drawer-inset is deleted from index.css, leaving ComposerCommandMenuLayer's getPropertyValue read resolving to "".
• ComposerBanner.tsxToggleIcon — decorative aria-hidden span inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 hit overlay inside Row render={<button/>}.
• ComposerPendingUserInputPanel.tsx — ComposerBanner.Body supplies only inline-start padding, so option-button focus rings are clipped by the animating CollapsiblePanel.
• MessagesTimeline.test.tsx — the iconless Thinking/working-timer alignment test is still dropped while the row it covered is restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The task list loses its list semantics in this migration: the old drawer rendered role="list" + role="listitem" explicitly (the deleted ComposerTasksBadge.test.tsx asserted both), while this <ul> relies on implicit roles. Tailwind's preflight sets list-style: none on ul, which makes WebKit drop the list role — and with it the aria-label on this container, since a generic element's label is not announced. Suggest re-asserting the role on the container (the li children keep listitem once the list role is explicit). ComposerStashMenu.tsx:133 has the same shape (render={<ul />} with aria-label="Stashed prompts") and needs the same fix.

Suggested change

	>
	render={<ulrole="list"/>}

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c0d3d53. Configure here.}

[macroscopeapp]

Reviewed the two new commits (c0d3d53 restoring the sync status, 4977016 moving the stash tab into the banner dock) plus the surrounding banner/surface migration.

One new finding on the restored ThreadSyncStatusPill (inline). The findings from earlier runs on this PR still apply at 4977016 and are not repeated here:

• ComposerBanner.ToggleIcon inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 overlay on a decorative span.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus-visible ring is clipped by the collapsible panel's overflow-hidden (ComposerPendingUserInputPanel.tsx:203-262).
• ComposerBannerStackAlert binds actions/dismiss to the title row while the description renders as a separate row, so controls are no longer centered against the title + description block.
• The tasks list (ComposerBanner.Children render={<ul />}) relies on implicit list semantics, which Tailwind preflight's list-style: none drops in WebKit along with the container aria-label.
• apps/web/src/components/chat/MessagesTimeline.test.tsx still drops the working/thinking row assertions even though WorkingTimelineRow was restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

🟡 Mediumcomponents/ChatView.tsx:4556

activeComposerTasksProgress returns null while thread details are loading because it now derives entirely from activePlan, which reads threadActivities — but buildLoadingThreadFromShell forces activities: [] during the loading window. The previous code fell back to activeThreadShell?.planProgress, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.

Consider falling back to activeThreadShell?.planProgress when activePlan is null and the thread is still loading, so the shell-level progress remains visible during that window.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/ChatView.tsx around line 4556:
`activeComposerTasksProgress` returns `null` while thread details are loading because it now derives entirely from `activePlan`, which reads `threadActivities` — but `buildLoadingThreadFromShell` forces `activities: []` during the loading window. The previous code fell back to `activeThreadShell?.planProgress`, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.
Consider falling back to `activeThreadShell?.planProgress` when `activePlan` is `null` and the thread is still loading, so the shell-level progress remains visible during that window.

[macroscopeapp]

One new finding in this push's neighbourhood: the composer server-update notice lost the live/failure indicator that ServerUpdateProgress used to own, and now shows a static InfoIcon even in the error variant. Previously reported findings on the earlier commits (banner Attachment inset vs. the deleted --chat-composer-drawer-inset, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body end/bottom padding, notice description/action alignment, ThreadSyncStatusPill bypassing the banner row grid, task-list role="list", and the dropped working-row alignment test) still apply and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This notice now uses a static InfoIcon for all three states, which drops the only live cue for a running update and puts an info icon on an error-variant banner. The removed code explained why: ServerUpdateProgress carried a pulsing dot while running and a destructive dot on failure, and only the idle offer needed an icon. ComposerServerUpdateStatus renders text only, so the pulse is gone and the failed row reads as informational next to the sibling notices that do pick situational icons (WifiOffIcon, AlarmClockIcon, GitBranchIcon) and a pulsing dot for live states.

Suggest keeping InfoIcon for the idle offer and restoring the dots for the other two states (ComposerBanner.Dot exists for exactly this and currently has no consumer, if you prefer routing it through the primitive):

Suggested change

	icon: <InfoIconaria-hidden/>,
	icon: updateInProgress ? (
	<span
	className="size-1.5 animate-status-pulse rounded-full bg-foreground"
	aria-hidden="true"
	/>
	) : updateFailed ? (
	<spanclassName="size-1.5 rounded-full bg-destructive"aria-hidden="true"/>
	) : (
	<InfoIconaria-hidden/>
	),

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration again against the new commit (53c1702, "restore combined loading and syncing banners").

The sync status now composes ComposerBanner.Row / Icon / Content (ComposerActivityStatus.tsx), which resolves the icon-column misalignment flagged on 4977016. One new finding below on the verification gate for the primitives this PR introduces.

Findings raised on earlier commits that are still present at this head (not re-posted):

• ComposerBanner.ToggleIcon inherits the full buttonVariants base, including the pointer-coarse 44x44 ::after hit box, inside rows that are themselves buttons.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus rings are clipped by the animating CollapsiblePanel.
• The task list relies on implicit ul/li roles after Preflight's list-style: none, dropping the list role and its aria-label in WebKit.
• Notice descriptions render as a second row, so actions/dismiss align to the title line instead of the whole block.
• ComposerCommandMenuLayer still reads --chat-composer-drawer-inset, whose only declaration this PR deletes.
• ChatView's server-update notice uses a static InfoIcon for running/failed/idle states.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

ComposerBanner and ComposerSurface now own the behaviors that four deleted test files pinned — attachment seam and placement (attached vs floating), per-variant outline/tint, stack-cap severity, tab vs inline rendering, and the sync status row — while ComposerBannerStack.test.tsx, ComposerStashBadge.test.tsx, ComposerTasksBadge.test.tsx and ThreadSyncStatusPill.test.tsx are removed and assertions are trimmed from ComposerCommandMenu.test.tsx / ComposerStashMenu.test.tsx. Nothing in apps/web renders ComposerBanner or ComposerSurface in a test, so the migrated contracts are unpinned.

This commit adds one more untested contract right here: width defaulting ("content" collapses to w-fit max-w-full flex-none and drops @container, so Row layout="wrap-actions" silently loses its container queries), plus the ChatComposer swap where threadSyncPhase suppresses activeTasksProgress/activeTaskSteps and takes the stack's attached slot.

Suggest a focused renderToStaticMarkup test for ComposerBanner.Root/Row covering attached vs floating placement, each variant's outline/tint tokens, and both width values, so these behaviors stay pinned the way the replaced components were.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency: one new finding on the latest push (combined loading/syncing banner). The earlier ThreadSyncStatusPill hand-rolled-row finding is resolved — ComposerActivityRow now composes Row/Icon/Content and shares the --composer-banner-icon-column grid. Findings from previous runs on this PR (server-update InfoIcon, banner description/action alignment, missing role="list" on the migrated task and stash lists, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body dropping the clipped panel's end/bottom padding, the deleted --chat-composer-drawer-inset declaration still read by ComposerCommandMenuLayer, and the removed Thinking-row test) are still open and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Peek is now the only pointer affordance for revealing the hidden notices, but its hit area is the 12px cap itself (h-3). ComposerBannerStack skips onPointerEnter when event.pointerType === "touch" and collapses the stack on onPointerDownCapture over the front banner, so on a coarse pointer this 12px strip is the only way to open the stack — before this PR any tap inside group/banner-stack revealed it through hover/focus-within. Elsewhere the system guarantees coarse pointers a 44px box (buttonVariants' pointer-coarse:after:min-h-11).

Suggest growing the tappable box upward only, so it stays clear of the front banner's dismiss/actions directly below:

Suggested change

	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"pointer-coarse:before:absolute pointer-coarse:before:inset-x-0 pointer-coarse:before:bottom-0 pointer-coarse:before:h-8",

^{Posted via Macroscope — UI Consistency}

[t3dotgg]

Restores the activity log grouping and shared composer banners from #8693 after #8733, while deferring the composer-attached working timer.

Working for keeps main's placement in the conversation timeline, including the current task label, Thinking state, and turn lifecycle. Long task labels truncate to one line while the timer remains fully visible. The composer keeps the restored task controls, notice stacking, and shared Tailwind components. Task progress appears only in the composer; the duplicate timeline checklist is removed. Plan proposals remain in the timeline. Stash stays in its own tab beside notices and expanded task lists, including compact layouts; its footer variant is removed. Loading and syncing use the shared banner stack and hide task controls until the thread is up to date. Their spinner respects reduced-motion preferences.

Rebased onto current main, including interim response folding and the latest failed-tool icon fix. Orchestrator V2 and queueing are deferred until this main-targeted PR is merged.

All after screenshots below were recaptured from 35e6b6653e95. The timeline comparisons render the same scripted events through the actual timeline components from the PR base, 8b817cbcaad7, and the current PR. Each pair uses matching viewport dimensions. Completed-turn folds are open in both versions; the mixed activity group is shown both collapsed and expanded. The composer comparisons retain their earlier-iteration before images, labelled separately.

Mixed command, file-read, and status entries now get one useful summary. Main already summarized tool-only groups; the improvement here is that mixed groups use that presentation too.

PR base: last command and hidden log entries	Current PR: summary of the whole group

Expanding that same group keeps the summary and shows compact detail rows, without separate Work Log headings.

PR base: expanded mixed log	Current PR: expanded activity group

Task updates no longer add Plan updated rows or a second checklist to the timeline. Commands stay in one group; task controls remain in the composer.

PR base: plan chatter and timeline checklist	Current PR: one command group, no duplicate tasks

The earlier error screenshot incorrectly modeled a failed test as a runtime error. These two corrected scenarios use the server's actual event conversion and payload projection.

Failed command followed by a successful retry — unchanged. A test exits with code 1, the fixture is edited, and the test reruns successfully. All three tool calls stay in one group on both the PR base and this branch. A nonzero command exit code does not split the group, and no failure-count prefix is added.

PR base: failed test and retry in one group	Current PR: same grouping

Expanding the group and failed command reveals the failure output in both versions:

PR base: failed command details	Current PR: same failure details

Provider crash at the end of a run. Two commands finish, then the provider exits unexpectedly and the turn ends. There are no commands continuing after the crash in this fixture. The base already shows the terminal runtime error; this PR gives the preceding commands their own summary and renders the error as a separate row.

PR base: terminal error with previous tool calls	Current PR: command summary followed by runtime error

The outer Worked for fold is open in every comparison. Collapsing that fold can still hide the error. The grouping boundary applies to error events, such as runtime failures, rather than ordinary failed tool results. This update corrects the evidence; it does not change production behavior.

The initial restore passed 242 focused web tests, web typecheck, and targeted lint. Checked the isolated fixture playground in the browser, including running/idle turns, task expansion, loading/syncing, notices, approvals, and stash. Stopping a turn removes the timer; deleting the last stashed prompt closes the stash. Preview fixtures remain local and are not part of the PR.

Earlier restore: attached timer	Current PR: timeline timer, tasks only in composer

Long task labels checked at 1440px and 768px viewport widths. Targeted lint and web typecheck pass.

PR base: wrapping task label	Current PR: single-line task label

Loading and syncing now keep the combined banner behavior: the status stays attached, notices peek behind it, and task controls stay hidden until the thread is up to date. Stash keeps its separate tab. Verified loading and syncing with and without tasks, notice expansion, narrow layouts, and reduced motion. All 64 focused tests, web typecheck, and targeted lint passed.

Earlier iteration: separate status row, tasks visible	Current PR: combined banner, tasks hidden

Narrow layout · Spinner recording

The stash placement update passed 61 focused tests, web typecheck, and targeted lint. Browser checks covered notices, expanded tasks, notice stacks, loading, narrow questions, compact-composer expansion, restoring a prompt, deleting the last entry, and the empty composer. This changes the shared web/desktop composer; native clients are unchanged.

Earlier iteration: stash in footer	Current PR: separate stash tab

With Stash closed, its tab stays beside the update notice:

Opening Stash shows the saved drafts in a drawer across the top of the composer, covering the notice underneath. Closing Stash reveals the notice again:

Expanded tasks keep their own panel beside Stash:

The task-list cleanup passed 218 focused tests, web typecheck, and targeted lint. Browser checks covered composer task expansion/collapse, command-group expansion, and completed turns. The working timer is unchanged. This uses the shared web/desktop timeline; native clients, providers, and wire contracts are unchanged.

Earlier restore: duplicate task checklist	Current PR: tasks only in the composer

The composer task list still expands beside Stash:

Note

Restore unified activity logs and rebuild composer banner system

• Removes turn-plan timeline rows and the MAX_VISIBLE_WORK_LOG_ENTRIES cap/overflow toggle, so work log entries are always shown in unified activity groups instead of being collapsed behind '+N previous …'
• Introduces a new update action type in ToolGroupAction for non-tool entries, with standalone rows for agent spawns and error-toned entries that bypass grouping
• Replaces ad-hoc composer layout with a new ComposerBanner, ComposerBannerStack, and ComposerSurface primitive system; tasks, stash, pending approvals, and server update notices all render through these shared components
• Integrates tasks progress into the banner stack (no longer dismissible per-turn) and adds a ComposerServerUpdateStatus component with dismissal support for failed update states
• Risk: ChatComposerProps replaces externalDrawerAttached with bannerItems and adds threadSyncPhase; ComposerStashBadge removes the placement prop; ComposerTasksBadge removes onDismiss and hasTrailingShoulder; deriveTurnPlans is deleted and deriveTimelineEntries no longer accepts turn plans — any out-of-tree callers of these APIs will break

^{Macroscope summarized cfb3851.}

---

Note

Medium Risk
Large, user-facing composer and timeline refactor with prop/API removals (externalDrawerAttached, task dismiss, turn plans); behavior changes for notices, sync, and work-log grouping are easy to miss in edge cases.

Overview
Restores unified timeline activity grouping and rebuilds the chat composer around shared ComposerSurface / ComposerBanner primitives.

Work log rendering drops the per-group visibility cap and turn-plan timeline rows. Mixed runs collapse into one expandable summary (including non-tool updates), while agent spawns and error-toned entries stay standalone. deriveTimelineEntries no longer takes turn plans.

Composer notices, thread sync, task progress, stash, approvals, and command/stash drawers all attach through ComposerBannerStack with explicit priority (activity / urgent / notice) instead of manual urgent/calm splits in ChatView. Banners move from above the glass shell into ChatComposer via bannerItems; threadSyncPhase suppresses task UI until sync finishes and can show ComposerActivityRow in the stack. Task progress is derived from the current turn’sactivePlan (not sidebar planProgress); per-turn task dismiss is removed. Stash is a shoulder tab only (no inline/footer variant). Server-update banners use ComposerServerUpdateStatus and can dismiss failed updates. shoulderTabReserve and the extra overlay mutation observer are removed—scroll clearance uses full composer height. BranchToolbar uses ComposerSurface.ContextStrip.

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

[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: f3a66e84-043e-4bc3-b47b-654eccf47321

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	+9 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−5 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	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.4 KiB	13.3 KiB	−16 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 8b817cb · PR result: 35e6b66 · 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]

UI consistency review found 2 issues in the new composer banner primitives. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The removed CollapsiblePanel className="px-3 sm:px-4" carried a comment explaining that the panel clips its content while the height animates, so the option buttons have to sit inside that padding or their focus rings get shaved. ComposerBanner.Body only supplies padding-inline-start, so the w-full option buttons now touch the panel's inline-end and block-end edges and their focus-visible:ring-1 is clipped by overflow-hidden. Restoring end/bottom padding inside the clipped box keeps the ring visible.

Suggested change

	<ComposerBanner.Body>
	<ComposerBanner.BodyclassName="pb-1 pe-1">

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This XXL change replaces shared composer and timeline behavior across many production paths, including notice stacking, task and sync visibility, activity grouping, and layout measurement. Several unresolved findings also identify interaction, accessibility, loading-state, and test-coverage regressions that require focused human review.

Not approved because:

• 3 blocking correctness issues found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[CDVolvik]

Verified fix(web): restore unified activity logs and composer banners at 39283f4 as CDVolvik.

Restores #8693 after #8733 revert — git diff 33 files +1506/-2094 identical to original. Activity logs: MessagesTimeline working row removed, work entries grouped contiguously, ChatView active task progress tied to activePlan of current turn, ChatComposer exposes bannerItems/isWorking. Composer banners: ComposerSurface/Banner primitives, priority activity<urgent<notice, custom tasks content, accessible peek. Tests: MessagesTimeline.logic+session-logic+versionSkew+ChatView.logic 194/194, MessagesTimeline 37/37 pass. Note per PR: Compact/dismiss alignment and banner padding not fixed yet — author defers to Julius — hold merge until follow-up. Otherwise LGTM, no push.

[macroscopeapp]

🟡 Mediumchat/ComposerBanner.tsx:94

When the notice stack is expanded, the Peek button remains pointer-interactive and keyboard-focusable despite receiving opacity-0, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply pointer-events-none and disabled (or omit it from the DOM) while the stack is expanded.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ComposerBanner.tsx around line 94:
When the notice stack is expanded, the `Peek` button remains pointer-interactive and keyboard-focusable despite receiving `opacity-0`, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply `pointer-events-none` and `disabled` (or omit it from the DOM) while the stack is expanded.

[macroscopeapp]

🟡 Mediumchat/ChatComposer.tsx:3602

ComposerTasksBadge and ComposerTasksDrawer no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.

Also found in 2 other location(s)

apps/web/src/components/chat/ComposerTasksBadge.tsx:112

ComposerTasksBadge no longer accepts or renders an onDismiss action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.

apps/web/src/components/chat/ComposerTasksBadge.tsx:232

ComposerTasksDrawer no longer accepts or renders the former onDismiss action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed dismissTasks to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ChatComposer.tsx around line 3602:
`ComposerTasksBadge` and `ComposerTasksDrawer` no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.
Also found in 2 other location(s):
- apps/web/src/components/chat/ComposerTasksBadge.tsx:112 -- `ComposerTasksBadge` no longer accepts or renders an `onDismiss` action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.
- apps/web/src/components/chat/ComposerTasksBadge.tsx:232 -- `ComposerTasksDrawer` no longer accepts or renders the former `onDismiss` action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed `dismissTasks` to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

[macroscopeapp]

UI consistency review of the restored composer banner/surface system. Three findings below; the two findings posted on the previous head (ComposerBanner.ToggleIcon inheriting the coarse-pointer hit-target pseudo-element, and ComposerBanner.Body losing the clipped panel's end/bottom padding) are still open on this head and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Notices with a description now bind both the icon and the action/dismiss controls to the titleRow, with the description rendered as a separate row underneath (ComposerBanner.Children). That reproduces the alignment regression this PR's description acknowledges as the reason #8693 was reverted: Compact / dismiss sit on the title line instead of being centered against the whole title + description block.

The primitive it replaced did this in one row: Alert (controlAlignment: "center") lays out icon | title+description column | actions in a single items-center flex row, so the controls center against the full block and only opt into first-line alignment explicitly.

Smallest fix: keep the description inside the same Row's ComposerBanner.Content (stacked, e.g. className="flex-col items-start gap-0.5" with the title span keeping font-medium) and reserve ComposerBanner.Children for item.children, so the row's items-center centers the icon and actions over both lines. The other half of the revert — banner edge padding, now p-1 on ComposerBanner.Root versus the old px-3 pt-2 sm:px-4 — belongs on Root rather than at each call site.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Attachment hardcodes the drawer inset (w-[calc(100%-2.75rem)], max-w-[45.25rem]), while this PR deletes the only declaration of --chat-composer-drawer-inset: 1.375rem from index.css. That variable still has an imperative consumer: ComposerCommandMenuLayer reads it with getComputedStyle(form ?? anchor).getPropertyValue("--chat-composer-drawer-inset") (ChatComposer.tsx:233) to compute the command menu's left and width. The read now always resolves to "" and silently takes the || 1.375 fallback, so the menu lines up only because 2.75rem happens to be twice that fallback, and the two owners will drift the next time this width changes.

Suggest keeping one owner: declare [--chat-composer-drawer-inset:1.375rem] on an ancestor the composer form inherits from (ComposerSurface.Shell) and derive the widths here from it, e.g. w-[calc(100%-2*var(--chat-composer-drawer-inset))] max-w-[calc(48rem-2*var(--chat-composer-drawer-inset))].

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This test was dropped when the working row left the timeline, but the follow-up commit restored WorkingTimelineRow/ThinkingActivityRow and the activeTurnStartedAt prop, and LiveActivityContent still emits gap-1.5 py-0.5 px-1 for the iconless variant — so the assertions still hold and the restored row is now unguarded, right as this PR reworks neighbouring row indentation (TurnPlanTimelineRow's chevron column and pl-6 → pl-8). Suggest restoring it as-is.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration at fe1774e. One new finding below (list semantics lost in the tasks/stash list migration). The findings from my earlier reviews on this PR are still open and are not reposted here:

• ComposerBannerStack.tsx — description notices bind icon/actions to the title row, so Compact/dismiss no longer center against the title + description block.
• ComposerBanner.tsxAttachment — hardcoded inset while --chat-composer-drawer-inset is deleted from index.css, leaving ComposerCommandMenuLayer's getPropertyValue read resolving to "".
• ComposerBanner.tsxToggleIcon — decorative aria-hidden span inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 hit overlay inside Row render={<button/>}.
• ComposerPendingUserInputPanel.tsx — ComposerBanner.Body supplies only inline-start padding, so option-button focus rings are clipped by the animating CollapsiblePanel.
• MessagesTimeline.test.tsx — the iconless Thinking/working-timer alignment test is still dropped while the row it covered is restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The task list loses its list semantics in this migration: the old drawer rendered role="list" + role="listitem" explicitly (the deleted ComposerTasksBadge.test.tsx asserted both), while this <ul> relies on implicit roles. Tailwind's preflight sets list-style: none on ul, which makes WebKit drop the list role — and with it the aria-label on this container, since a generic element's label is not announced. Suggest re-asserting the role on the container (the li children keep listitem once the list role is explicit). ComposerStashMenu.tsx:133 has the same shape (render={<ul />} with aria-label="Stashed prompts") and needs the same fix.

Suggested change

	>
	render={<ulrole="list"/>}

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c0d3d53. Configure here.}

[macroscopeapp]

Reviewed the two new commits (c0d3d53 restoring the sync status, 4977016 moving the stash tab into the banner dock) plus the surrounding banner/surface migration.

One new finding on the restored ThreadSyncStatusPill (inline). The findings from earlier runs on this PR still apply at 4977016 and are not repeated here:

• ComposerBanner.ToggleIcon inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 overlay on a decorative span.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus-visible ring is clipped by the collapsible panel's overflow-hidden (ComposerPendingUserInputPanel.tsx:203-262).
• ComposerBannerStackAlert binds actions/dismiss to the title row while the description renders as a separate row, so controls are no longer centered against the title + description block.
• The tasks list (ComposerBanner.Children render={<ul />}) relies on implicit list semantics, which Tailwind preflight's list-style: none drops in WebKit along with the container aria-label.
• apps/web/src/components/chat/MessagesTimeline.test.tsx still drops the working/thinking row assertions even though WorkingTimelineRow was restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

🟡 Mediumcomponents/ChatView.tsx:4556

activeComposerTasksProgress returns null while thread details are loading because it now derives entirely from activePlan, which reads threadActivities — but buildLoadingThreadFromShell forces activities: [] during the loading window. The previous code fell back to activeThreadShell?.planProgress, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.

Consider falling back to activeThreadShell?.planProgress when activePlan is null and the thread is still loading, so the shell-level progress remains visible during that window.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/ChatView.tsx around line 4556:
`activeComposerTasksProgress` returns `null` while thread details are loading because it now derives entirely from `activePlan`, which reads `threadActivities` — but `buildLoadingThreadFromShell` forces `activities: []` during the loading window. The previous code fell back to `activeThreadShell?.planProgress`, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.
Consider falling back to `activeThreadShell?.planProgress` when `activePlan` is `null` and the thread is still loading, so the shell-level progress remains visible during that window.

[macroscopeapp]

One new finding in this push's neighbourhood: the composer server-update notice lost the live/failure indicator that ServerUpdateProgress used to own, and now shows a static InfoIcon even in the error variant. Previously reported findings on the earlier commits (banner Attachment inset vs. the deleted --chat-composer-drawer-inset, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body end/bottom padding, notice description/action alignment, ThreadSyncStatusPill bypassing the banner row grid, task-list role="list", and the dropped working-row alignment test) still apply and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This notice now uses a static InfoIcon for all three states, which drops the only live cue for a running update and puts an info icon on an error-variant banner. The removed code explained why: ServerUpdateProgress carried a pulsing dot while running and a destructive dot on failure, and only the idle offer needed an icon. ComposerServerUpdateStatus renders text only, so the pulse is gone and the failed row reads as informational next to the sibling notices that do pick situational icons (WifiOffIcon, AlarmClockIcon, GitBranchIcon) and a pulsing dot for live states.

Suggest keeping InfoIcon for the idle offer and restoring the dots for the other two states (ComposerBanner.Dot exists for exactly this and currently has no consumer, if you prefer routing it through the primitive):

Suggested change

	icon: <InfoIconaria-hidden/>,
	icon: updateInProgress ? (
	<span
	className="size-1.5 animate-status-pulse rounded-full bg-foreground"
	aria-hidden="true"
	/>
	) : updateFailed ? (
	<spanclassName="size-1.5 rounded-full bg-destructive"aria-hidden="true"/>
	) : (
	<InfoIconaria-hidden/>
	),

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration again against the new commit (53c1702, "restore combined loading and syncing banners").

The sync status now composes ComposerBanner.Row / Icon / Content (ComposerActivityStatus.tsx), which resolves the icon-column misalignment flagged on 4977016. One new finding below on the verification gate for the primitives this PR introduces.

Findings raised on earlier commits that are still present at this head (not re-posted):

• ComposerBanner.ToggleIcon inherits the full buttonVariants base, including the pointer-coarse 44x44 ::after hit box, inside rows that are themselves buttons.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus rings are clipped by the animating CollapsiblePanel.
• The task list relies on implicit ul/li roles after Preflight's list-style: none, dropping the list role and its aria-label in WebKit.
• Notice descriptions render as a second row, so actions/dismiss align to the title line instead of the whole block.
• ComposerCommandMenuLayer still reads --chat-composer-drawer-inset, whose only declaration this PR deletes.
• ChatView's server-update notice uses a static InfoIcon for running/failed/idle states.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

ComposerBanner and ComposerSurface now own the behaviors that four deleted test files pinned — attachment seam and placement (attached vs floating), per-variant outline/tint, stack-cap severity, tab vs inline rendering, and the sync status row — while ComposerBannerStack.test.tsx, ComposerStashBadge.test.tsx, ComposerTasksBadge.test.tsx and ThreadSyncStatusPill.test.tsx are removed and assertions are trimmed from ComposerCommandMenu.test.tsx / ComposerStashMenu.test.tsx. Nothing in apps/web renders ComposerBanner or ComposerSurface in a test, so the migrated contracts are unpinned.

This commit adds one more untested contract right here: width defaulting ("content" collapses to w-fit max-w-full flex-none and drops @container, so Row layout="wrap-actions" silently loses its container queries), plus the ChatComposer swap where threadSyncPhase suppresses activeTasksProgress/activeTaskSteps and takes the stack's attached slot.

Suggest a focused renderToStaticMarkup test for ComposerBanner.Root/Row covering attached vs floating placement, each variant's outline/tint tokens, and both width values, so these behaviors stay pinned the way the replaced components were.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency: one new finding on the latest push (combined loading/syncing banner). The earlier ThreadSyncStatusPill hand-rolled-row finding is resolved — ComposerActivityRow now composes Row/Icon/Content and shares the --composer-banner-icon-column grid. Findings from previous runs on this PR (server-update InfoIcon, banner description/action alignment, missing role="list" on the migrated task and stash lists, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body dropping the clipped panel's end/bottom padding, the deleted --chat-composer-drawer-inset declaration still read by ComposerCommandMenuLayer, and the removed Thinking-row test) are still open and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Peek is now the only pointer affordance for revealing the hidden notices, but its hit area is the 12px cap itself (h-3). ComposerBannerStack skips onPointerEnter when event.pointerType === "touch" and collapses the stack on onPointerDownCapture over the front banner, so on a coarse pointer this 12px strip is the only way to open the stack — before this PR any tap inside group/banner-stack revealed it through hover/focus-within. Elsewhere the system guarantees coarse pointers a 44px box (buttonVariants' pointer-coarse:after:min-h-11).

Suggest growing the tappable box upward only, so it stays clear of the front banner's dismiss/actions directly below:

Suggested change

	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"pointer-coarse:before:absolute pointer-coarse:before:inset-x-0 pointer-coarse:before:bottom-0 pointer-coarse:before:h-8",

^{Posted via Macroscope — UI Consistency}

[t3dotgg]

Restores the activity log grouping and shared composer banners from #8693 after #8733, while deferring the composer-attached working timer.

Working for keeps main's placement in the conversation timeline, including the current task label, Thinking state, and turn lifecycle. Long task labels truncate to one line while the timer remains fully visible. The composer keeps the restored task controls, notice stacking, and shared Tailwind components. Task progress appears only in the composer; the duplicate timeline checklist is removed. Plan proposals remain in the timeline. Stash stays in its own tab beside notices and expanded task lists, including compact layouts; its footer variant is removed. Loading and syncing use the shared banner stack and hide task controls until the thread is up to date. Their spinner respects reduced-motion preferences.

Rebased onto current main, including interim response folding and the latest failed-tool icon fix. Orchestrator V2 and queueing are deferred until this main-targeted PR is merged.

All after screenshots below were recaptured from 35e6b6653e95. The timeline comparisons render the same scripted events through the actual timeline components from the PR base, 8b817cbcaad7, and the current PR. Each pair uses matching viewport dimensions. Completed-turn folds are open in both versions; the mixed activity group is shown both collapsed and expanded. The composer comparisons retain their earlier-iteration before images, labelled separately.

Mixed command, file-read, and status entries now get one useful summary. Main already summarized tool-only groups; the improvement here is that mixed groups use that presentation too.

PR base: last command and hidden log entries	Current PR: summary of the whole group

Expanding that same group keeps the summary and shows compact detail rows, without separate Work Log headings.

PR base: expanded mixed log	Current PR: expanded activity group

Task updates no longer add Plan updated rows or a second checklist to the timeline. Commands stay in one group; task controls remain in the composer.

PR base: plan chatter and timeline checklist	Current PR: one command group, no duplicate tasks

The earlier error screenshot incorrectly modeled a failed test as a runtime error. These two corrected scenarios use the server's actual event conversion and payload projection.

Failed command followed by a successful retry — unchanged. A test exits with code 1, the fixture is edited, and the test reruns successfully. All three tool calls stay in one group on both the PR base and this branch. A nonzero command exit code does not split the group, and no failure-count prefix is added.

PR base: failed test and retry in one group	Current PR: same grouping

Expanding the group and failed command reveals the failure output in both versions:

PR base: failed command details	Current PR: same failure details

Provider crash at the end of a run. Two commands finish, then the provider exits unexpectedly and the turn ends. There are no commands continuing after the crash in this fixture. The base already shows the terminal runtime error; this PR gives the preceding commands their own summary and renders the error as a separate row.

PR base: terminal error with previous tool calls	Current PR: command summary followed by runtime error

The outer Worked for fold is open in every comparison. Collapsing that fold can still hide the error. The grouping boundary applies to error events, such as runtime failures, rather than ordinary failed tool results. This update corrects the evidence; it does not change production behavior.

The initial restore passed 242 focused web tests, web typecheck, and targeted lint. Checked the isolated fixture playground in the browser, including running/idle turns, task expansion, loading/syncing, notices, approvals, and stash. Stopping a turn removes the timer; deleting the last stashed prompt closes the stash. Preview fixtures remain local and are not part of the PR.

Earlier restore: attached timer	Current PR: timeline timer, tasks only in composer

Long task labels checked at 1440px and 768px viewport widths. Targeted lint and web typecheck pass.

PR base: wrapping task label	Current PR: single-line task label

Loading and syncing now keep the combined banner behavior: the status stays attached, notices peek behind it, and task controls stay hidden until the thread is up to date. Stash keeps its separate tab. Verified loading and syncing with and without tasks, notice expansion, narrow layouts, and reduced motion. All 64 focused tests, web typecheck, and targeted lint passed.

Earlier iteration: separate status row, tasks visible	Current PR: combined banner, tasks hidden

Narrow layout · Spinner recording

The stash placement update passed 61 focused tests, web typecheck, and targeted lint. Browser checks covered notices, expanded tasks, notice stacks, loading, narrow questions, compact-composer expansion, restoring a prompt, deleting the last entry, and the empty composer. This changes the shared web/desktop composer; native clients are unchanged.

Earlier iteration: stash in footer	Current PR: separate stash tab

With Stash closed, its tab stays beside the update notice:

Opening Stash shows the saved drafts in a drawer across the top of the composer, covering the notice underneath. Closing Stash reveals the notice again:

Expanded tasks keep their own panel beside Stash:

The task-list cleanup passed 218 focused tests, web typecheck, and targeted lint. Browser checks covered composer task expansion/collapse, command-group expansion, and completed turns. The working timer is unchanged. This uses the shared web/desktop timeline; native clients, providers, and wire contracts are unchanged.

Earlier restore: duplicate task checklist	Current PR: tasks only in the composer

The composer task list still expands beside Stash:

Note

Restore unified activity logs and rebuild composer banner system

• Removes turn-plan timeline rows and the MAX_VISIBLE_WORK_LOG_ENTRIES cap/overflow toggle, so work log entries are always shown in unified activity groups instead of being collapsed behind '+N previous …'
• Introduces a new update action type in ToolGroupAction for non-tool entries, with standalone rows for agent spawns and error-toned entries that bypass grouping
• Replaces ad-hoc composer layout with a new ComposerBanner, ComposerBannerStack, and ComposerSurface primitive system; tasks, stash, pending approvals, and server update notices all render through these shared components
• Integrates tasks progress into the banner stack (no longer dismissible per-turn) and adds a ComposerServerUpdateStatus component with dismissal support for failed update states
• Risk: ChatComposerProps replaces externalDrawerAttached with bannerItems and adds threadSyncPhase; ComposerStashBadge removes the placement prop; ComposerTasksBadge removes onDismiss and hasTrailingShoulder; deriveTurnPlans is deleted and deriveTimelineEntries no longer accepts turn plans — any out-of-tree callers of these APIs will break

^{Macroscope summarized cfb3851.}

---

Note

Medium Risk
Large, user-facing composer and timeline refactor with prop/API removals (externalDrawerAttached, task dismiss, turn plans); behavior changes for notices, sync, and work-log grouping are easy to miss in edge cases.

Overview
Restores unified timeline activity grouping and rebuilds the chat composer around shared ComposerSurface / ComposerBanner primitives.

Work log rendering drops the per-group visibility cap and turn-plan timeline rows. Mixed runs collapse into one expandable summary (including non-tool updates), while agent spawns and error-toned entries stay standalone. deriveTimelineEntries no longer takes turn plans.

Composer notices, thread sync, task progress, stash, approvals, and command/stash drawers all attach through ComposerBannerStack with explicit priority (activity / urgent / notice) instead of manual urgent/calm splits in ChatView. Banners move from above the glass shell into ChatComposer via bannerItems; threadSyncPhase suppresses task UI until sync finishes and can show ComposerActivityRow in the stack. Task progress is derived from the current turn’sactivePlan (not sidebar planProgress); per-turn task dismiss is removed. Stash is a shoulder tab only (no inline/footer variant). Server-update banners use ComposerServerUpdateStatus and can dismiss failed updates. shoulderTabReserve and the extra overlay mutation observer are removed—scroll clearance uses full composer height. BranchToolbar uses ComposerSurface.ContextStrip.

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

[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: f3a66e84-043e-4bc3-b47b-654eccf47321

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	+9 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−5 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	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.4 KiB	13.3 KiB	−16 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.4 KiB	−19 B (−0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 8b817cb · PR result: 35e6b66 · 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]

UI consistency review found 2 issues in the new composer banner primitives. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The removed CollapsiblePanel className="px-3 sm:px-4" carried a comment explaining that the panel clips its content while the height animates, so the option buttons have to sit inside that padding or their focus rings get shaved. ComposerBanner.Body only supplies padding-inline-start, so the w-full option buttons now touch the panel's inline-end and block-end edges and their focus-visible:ring-1 is clipped by overflow-hidden. Restoring end/bottom padding inside the clipped box keeps the ring visible.

Suggested change

	<ComposerBanner.Body>
	<ComposerBanner.BodyclassName="pb-1 pe-1">

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This XXL change replaces shared composer and timeline behavior across many production paths, including notice stacking, task and sync visibility, activity grouping, and layout measurement. Several unresolved findings also identify interaction, accessibility, loading-state, and test-coverage regressions that require focused human review.

Not approved because:

• 3 blocking correctness issues found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[CDVolvik]

Verified fix(web): restore unified activity logs and composer banners at 39283f4 as CDVolvik.

Restores #8693 after #8733 revert — git diff 33 files +1506/-2094 identical to original. Activity logs: MessagesTimeline working row removed, work entries grouped contiguously, ChatView active task progress tied to activePlan of current turn, ChatComposer exposes bannerItems/isWorking. Composer banners: ComposerSurface/Banner primitives, priority activity<urgent<notice, custom tasks content, accessible peek. Tests: MessagesTimeline.logic+session-logic+versionSkew+ChatView.logic 194/194, MessagesTimeline 37/37 pass. Note per PR: Compact/dismiss alignment and banner padding not fixed yet — author defers to Julius — hold merge until follow-up. Otherwise LGTM, no push.

[macroscopeapp]

🟡 Mediumchat/ComposerBanner.tsx:94

When the notice stack is expanded, the Peek button remains pointer-interactive and keyboard-focusable despite receiving opacity-0, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply pointer-events-none and disabled (or omit it from the DOM) while the stack is expanded.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ComposerBanner.tsx around line 94:
When the notice stack is expanded, the `Peek` button remains pointer-interactive and keyboard-focusable despite receiving `opacity-0`, so keyboard users tab to an undiscoverable “Show other notices” control and pointer events can still reach it. Hide it from interaction as well—conditionally apply `pointer-events-none` and `disabled` (or omit it from the DOM) while the stack is expanded.

[macroscopeapp]

🟡 Mediumchat/ChatComposer.tsx:3602

ComposerTasksBadge and ComposerTasksDrawer no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.

Also found in 2 other location(s)

apps/web/src/components/chat/ComposerTasksBadge.tsx:112

ComposerTasksBadge no longer accepts or renders an onDismiss action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.

apps/web/src/components/chat/ComposerTasksBadge.tsx:232

ComposerTasksDrawer no longer accepts or renders the former onDismiss action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed dismissTasks to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/chat/ChatComposer.tsx around line 3602:
`ComposerTasksBadge` and `ComposerTasksDrawer` no longer expose the former “Dismiss tasks for this turn” action, so users can only collapse an active task list; completed or stale task indicators remain attached until the underlying task state disappears. Restore the per-turn dismissal state and pass a dismiss handler to both render paths.
Also found in 2 other location(s):
- apps/web/src/components/chat/ComposerTasksBadge.tsx:112 -- `ComposerTasksBadge` no longer accepts or renders an `onDismiss` action, so users have no way to invoke the previously available “Dismiss tasks for this turn” control. When a task progress banner remains visible, it can only be collapsed, not dismissed for the rest of that turn.
- apps/web/src/components/chat/ComposerTasksBadge.tsx:232 -- `ComposerTasksDrawer` no longer accepts or renders the former `onDismiss` action, so an active task indicator cannot be dismissed for the current turn. The prior caller tracked the dismissed turn and passed `dismissTasks` to both the badge and drawer; the new component exposes only collapse, leaving users unable to hide task progress they explicitly dismissed.

[macroscopeapp]

UI consistency review of the restored composer banner/surface system. Three findings below; the two findings posted on the previous head (ComposerBanner.ToggleIcon inheriting the coarse-pointer hit-target pseudo-element, and ComposerBanner.Body losing the clipped panel's end/bottom padding) are still open on this head and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Notices with a description now bind both the icon and the action/dismiss controls to the titleRow, with the description rendered as a separate row underneath (ComposerBanner.Children). That reproduces the alignment regression this PR's description acknowledges as the reason #8693 was reverted: Compact / dismiss sit on the title line instead of being centered against the whole title + description block.

The primitive it replaced did this in one row: Alert (controlAlignment: "center") lays out icon | title+description column | actions in a single items-center flex row, so the controls center against the full block and only opt into first-line alignment explicitly.

Smallest fix: keep the description inside the same Row's ComposerBanner.Content (stacked, e.g. className="flex-col items-start gap-0.5" with the title span keeping font-medium) and reserve ComposerBanner.Children for item.children, so the row's items-center centers the icon and actions over both lines. The other half of the revert — banner edge padding, now p-1 on ComposerBanner.Root versus the old px-3 pt-2 sm:px-4 — belongs on Root rather than at each call site.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Attachment hardcodes the drawer inset (w-[calc(100%-2.75rem)], max-w-[45.25rem]), while this PR deletes the only declaration of --chat-composer-drawer-inset: 1.375rem from index.css. That variable still has an imperative consumer: ComposerCommandMenuLayer reads it with getComputedStyle(form ?? anchor).getPropertyValue("--chat-composer-drawer-inset") (ChatComposer.tsx:233) to compute the command menu's left and width. The read now always resolves to "" and silently takes the || 1.375 fallback, so the menu lines up only because 2.75rem happens to be twice that fallback, and the two owners will drift the next time this width changes.

Suggest keeping one owner: declare [--chat-composer-drawer-inset:1.375rem] on an ancestor the composer form inherits from (ComposerSurface.Shell) and derive the widths here from it, e.g. w-[calc(100%-2*var(--chat-composer-drawer-inset))] max-w-[calc(48rem-2*var(--chat-composer-drawer-inset))].

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This test was dropped when the working row left the timeline, but the follow-up commit restored WorkingTimelineRow/ThinkingActivityRow and the activeTurnStartedAt prop, and LiveActivityContent still emits gap-1.5 py-0.5 px-1 for the iconless variant — so the assertions still hold and the restored row is now unguarded, right as this PR reworks neighbouring row indentation (TurnPlanTimelineRow's chevron column and pl-6 → pl-8). Suggest restoring it as-is.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration at fe1774e. One new finding below (list semantics lost in the tasks/stash list migration). The findings from my earlier reviews on this PR are still open and are not reposted here:

• ComposerBannerStack.tsx — description notices bind icon/actions to the title row, so Compact/dismiss no longer center against the title + description block.
• ComposerBanner.tsxAttachment — hardcoded inset while --chat-composer-drawer-inset is deleted from index.css, leaving ComposerCommandMenuLayer's getPropertyValue read resolving to "".
• ComposerBanner.tsxToggleIcon — decorative aria-hidden span inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 hit overlay inside Row render={<button/>}.
• ComposerPendingUserInputPanel.tsx — ComposerBanner.Body supplies only inline-start padding, so option-button focus rings are clipped by the animating CollapsiblePanel.
• MessagesTimeline.test.tsx — the iconless Thinking/working-timer alignment test is still dropped while the row it covered is restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

The task list loses its list semantics in this migration: the old drawer rendered role="list" + role="listitem" explicitly (the deleted ComposerTasksBadge.test.tsx asserted both), while this <ul> relies on implicit roles. Tailwind's preflight sets list-style: none on ul, which makes WebKit drop the list role — and with it the aria-label on this container, since a generic element's label is not announced. Suggest re-asserting the role on the container (the li children keep listitem once the list role is explicit). ComposerStashMenu.tsx:133 has the same shape (render={<ul />} with aria-label="Stashed prompts") and needs the same fix.

Suggested change

	>
	render={<ulrole="list"/>}

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c0d3d53. Configure here.}

[macroscopeapp]

Reviewed the two new commits (c0d3d53 restoring the sync status, 4977016 moving the stash tab into the banner dock) plus the surrounding banner/surface migration.

One new finding on the restored ThreadSyncStatusPill (inline). The findings from earlier runs on this PR still apply at 4977016 and are not repeated here:

• ComposerBanner.ToggleIcon inherits buttonVariants' pointer-coarse:after:min-h-11/min-w-11 overlay on a decorative span.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus-visible ring is clipped by the collapsible panel's overflow-hidden (ComposerPendingUserInputPanel.tsx:203-262).
• ComposerBannerStackAlert binds actions/dismiss to the title row while the description renders as a separate row, so controls are no longer centered against the title + description block.
• The tasks list (ComposerBanner.Children render={<ul />}) relies on implicit list semantics, which Tailwind preflight's list-style: none drops in WebKit along with the container aria-label.
• apps/web/src/components/chat/MessagesTimeline.test.tsx still drops the working/thinking row assertions even though WorkingTimelineRow was restored.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

🟡 Mediumcomponents/ChatView.tsx:4556

activeComposerTasksProgress returns null while thread details are loading because it now derives entirely from activePlan, which reads threadActivities — but buildLoadingThreadFromShell forces activities: [] during the loading window. The previous code fell back to activeThreadShell?.planProgress, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.

Consider falling back to activeThreadShell?.planProgress when activePlan is null and the thread is still loading, so the shell-level progress remains visible during that window.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/ChatView.tsx around line 4556:
`activeComposerTasksProgress` returns `null` while thread details are loading because it now derives entirely from `activePlan`, which reads `threadActivities` — but `buildLoadingThreadFromShell` forces `activities: []` during the loading window. The previous code fell back to `activeThreadShell?.planProgress`, which is available on the shell even before full details arrive. This causes the task progress indicator and step controls to disappear during the thread-detail loading/sync phase and only reappear once the full detail payload lands.
Consider falling back to `activeThreadShell?.planProgress` when `activePlan` is `null` and the thread is still loading, so the shell-level progress remains visible during that window.

[macroscopeapp]

One new finding in this push's neighbourhood: the composer server-update notice lost the live/failure indicator that ServerUpdateProgress used to own, and now shows a static InfoIcon even in the error variant. Previously reported findings on the earlier commits (banner Attachment inset vs. the deleted --chat-composer-drawer-inset, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body end/bottom padding, notice description/action alignment, ThreadSyncStatusPill bypassing the banner row grid, task-list role="list", and the dropped working-row alignment test) still apply and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

This notice now uses a static InfoIcon for all three states, which drops the only live cue for a running update and puts an info icon on an error-variant banner. The removed code explained why: ServerUpdateProgress carried a pulsing dot while running and a destructive dot on failure, and only the idle offer needed an icon. ComposerServerUpdateStatus renders text only, so the pulse is gone and the failed row reads as informational next to the sibling notices that do pick situational icons (WifiOffIcon, AlarmClockIcon, GitBranchIcon) and a pulsing dot for live states.

Suggest keeping InfoIcon for the idle offer and restoring the dots for the other two states (ComposerBanner.Dot exists for exactly this and currently has no consumer, if you prefer routing it through the primitive):

Suggested change

	icon: <InfoIconaria-hidden/>,
	icon: updateInProgress ? (
	<span
	className="size-1.5 animate-status-pulse rounded-full bg-foreground"
	aria-hidden="true"
	/>
	) : updateFailed ? (
	<spanclassName="size-1.5 rounded-full bg-destructive"aria-hidden="true"/>
	) : (
	<InfoIconaria-hidden/>
	),

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the composer banner/surface migration again against the new commit (53c1702, "restore combined loading and syncing banners").

The sync status now composes ComposerBanner.Row / Icon / Content (ComposerActivityStatus.tsx), which resolves the icon-column misalignment flagged on 4977016. One new finding below on the verification gate for the primitives this PR introduces.

Findings raised on earlier commits that are still present at this head (not re-posted):

• ComposerBanner.ToggleIcon inherits the full buttonVariants base, including the pointer-coarse 44x44 ::after hit box, inside rows that are themselves buttons.
• ComposerBanner.Body supplies only padding-inline-start, so the pending-input option buttons' focus rings are clipped by the animating CollapsiblePanel.
• The task list relies on implicit ul/li roles after Preflight's list-style: none, dropping the list role and its aria-label in WebKit.
• Notice descriptions render as a second row, so actions/dismiss align to the title line instead of the whole block.
• ComposerCommandMenuLayer still reads --chat-composer-drawer-inset, whose only declaration this PR deletes.
• ChatView's server-update notice uses a static InfoIcon for running/failed/idle states.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

ComposerBanner and ComposerSurface now own the behaviors that four deleted test files pinned — attachment seam and placement (attached vs floating), per-variant outline/tint, stack-cap severity, tab vs inline rendering, and the sync status row — while ComposerBannerStack.test.tsx, ComposerStashBadge.test.tsx, ComposerTasksBadge.test.tsx and ThreadSyncStatusPill.test.tsx are removed and assertions are trimmed from ComposerCommandMenu.test.tsx / ComposerStashMenu.test.tsx. Nothing in apps/web renders ComposerBanner or ComposerSurface in a test, so the migrated contracts are unpinned.

This commit adds one more untested contract right here: width defaulting ("content" collapses to w-fit max-w-full flex-none and drops @container, so Row layout="wrap-actions" silently loses its container queries), plus the ChatComposer swap where threadSyncPhase suppresses activeTasksProgress/activeTaskSteps and takes the stack's attached slot.

Suggest a focused renderToStaticMarkup test for ComposerBanner.Root/Row covering attached vs floating placement, each variant's outline/tint tokens, and both width values, so these behaviors stay pinned the way the replaced components were.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency: one new finding on the latest push (combined loading/syncing banner). The earlier ThreadSyncStatusPill hand-rolled-row finding is resolved — ComposerActivityRow now composes Row/Icon/Content and shares the --composer-banner-icon-column grid. Findings from previous runs on this PR (server-update InfoIcon, banner description/action alignment, missing role="list" on the migrated task and stash lists, ToggleIcon inheriting buttonVariants' coarse-pointer overlay, ComposerBanner.Body dropping the clipped panel's end/bottom padding, the deleted --chat-composer-drawer-inset declaration still read by ComposerCommandMenuLayer, and the removed Thinking-row test) are still open and are not repeated here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Peek is now the only pointer affordance for revealing the hidden notices, but its hit area is the 12px cap itself (h-3). ComposerBannerStack skips onPointerEnter when event.pointerType === "touch" and collapses the stack on onPointerDownCapture over the front banner, so on a coarse pointer this 12px strip is the only way to open the stack — before this PR any tap inside group/banner-stack revealed it through hover/focus-within. Elsewhere the system guarantees coarse pointers a 44px box (buttonVariants' pointer-coarse:after:min-h-11).

Suggest growing the tappable box upward only, so it stays clear of the front banner's dismiss/actions directly below:

Suggested change

	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"absolute inset-x-0 bottom-0 z-0 mx-auto h-3 w-[96%] cursor-pointer rounded-t-2xl border border-b-0 shadow-[0_6px_18px_rgb(0_0_0/6%)]",
	"pointer-coarse:before:absolute pointer-coarse:before:inset-x-0 pointer-coarse:before:bottom-0 pointer-coarse:before:h-8",

^{Posted via Macroscope — UI Consistency}