From 6648ef4798bf1448bd3a73e7289dfbb2d1f8e75a Mon Sep 17 00:00:00 2001 From: digvijay208 Date: Wed, 15 Jul 2026 01:05:20 +0530 Subject: [PATCH] fix(command-center): question prompt no longer blocks thread scroll When a question/permission prompt appeared in a Command Center cell, the ComposerSlot wrapper had shrink-0, preventing the flex parent from keeping the ThreadView visible. Combined with ActionSelector's max-h-[80vh] (80% of the viewport, not the cell), the question card could consume the entire compact cell, making it impossible to scroll up to see past messages. Fix: in compact mode, drop shrink-0 and cap the slot at max-h-[50%] of the parent. The question prompt scrolls internally via overflow-y-auto if it's taller than half the cell, while the ThreadView above remains accessible. Non-compact behavior is unchanged. Fixes #2510 --- .../features/sessions/components/SessionView.tsx | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/packages/ui/src/features/sessions/components/SessionView.tsx b/packages/ui/src/features/sessions/components/SessionView.tsx index 5c84aaefa6..0811cef550 100644 --- a/packages/ui/src/features/sessions/components/SessionView.tsx +++ b/packages/ui/src/features/sessions/components/SessionView.tsx @@ -125,6 +125,11 @@ function ComposerWidth({ * Input region replacing the composer: `shrink-0` keeps it from being * compressed by the scroller above, and `min-h-0 overflow-y-auto` lets tall * content scroll inside itself. + * + * In compact mode (command center), the slot is height-capped at 50% of the + * parent so a tall question prompt cannot push the ThreadView out of view. + * The `shrink-0` is intentionally dropped for compact mode so the flex parent + * can keep the thread visible. */ function ComposerSlot({ compact, @@ -134,7 +139,13 @@ function ComposerSlot({ children: React.ReactNode; }) { return ( - + {children} );