continuedev / continuedev/continue
Bug: Accept/Reject buttons clipped in narrow sidebar (GUI layout overflow)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Bug Description
When the VS Code sidebar panel is narrow (~300px) or after extended chat sessions with many code blocks and terminal outputs, the Accept/Reject buttons in PendingToolCallToolbar are clipped (partially or fully hidden).
This makes it impossible for users to approve or reject tool calls, blocking the conversation flow.
Root Cause
- Flexbox with
shrink-0— buttons cannot shrink and are pushed outside visible area - Viewport-relative
max-width—calc(100vw - 24px)uses viewport width (e.g., 1920px) instead of container width (e.g., 300px sidebar) - Missing shrink constraints — flex hierarchy lacks
min-w-0at critical points
Fix
PR #13131 fixes this by:
- Switching toolbar from flexbox to CSS Grid (
grid-cols-[minmax(0,1fr)_auto]) - Replacing
calc(100vw - 24px)with container-relative100% - Adding
min-w-0andoverflow-hiddenthroughout the chat UI hierarchy
Impact
- Before: Buttons clipped in narrow sidebar, users cannot approve/reject tool calls
- After: Buttons always visible, consistent layout containment
Reproduction
- Open Continue sidebar in VS Code
- Resize sidebar to minimum width (~300px)
- Trigger a tool call (e.g., ask to edit a file)
- Observe: Accept/Reject buttons are clipped
Related
- PR: #13131 (fix ready for review)
- Pure CSS/Tailwind fix, no logic changes
- All 47/48 CI checks pass (only
jetbrains-testsflaky upstream)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the PendingToolCallToolbar and the changes described in PR #13131. Review the narrow-sidebar reproduction in VS Code and verify the CSS/Tailwind layout behavior at roughly 300px and after long chat sessions. Done means the Accept/Reject buttons remain fully visible and usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tailwindcss, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100