anomalyco / anomalyco/opencode

Web UI status popover: MCP/plugin list cannot be scrolled (no max-height)

Open
#43,668 0 comments 0 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Aug 20, 2026.

2.0
Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Summary

In the Web UI, the status popover (top-right status icon) shows MCP servers and plugins in tabs, but the list has no max-height or scroll container. With many entries (e.g., 82 plugins) the list stretches beyond the viewport and cannot be scrolled, so lower items are unreachable.

Environment

  • opencode version: 0.0.0-beta-17728
  • OS: Linux 7.0.0-29-generic (Ubuntu) x86_64
  • Terminal: TERM_PROGRAM=Orca TERM=xterm-256color COLORTERM=truecolor
  • Shell: /bin/bash
  • Install/channel: beta
  • Server: background service http://0.0.0.0:49374

Reproduction

  1. Open the Web UI and click the status icon at the top right
  2. Open the plugins tab (or MCP/LSP tab)
  3. With a large number of entries the list extends past the viewport; wheel/trackpad scrolling does not move the list
  4. Lower entries are invisible and unreachable

Expected Behavior

The popover list should scroll (max-height with overflow-y auto) so all entries are reachable.

Actual Behavior

The list has no max-height and no scroll container. The Tabs component uses overflow-hidden and the tab content is a plain flex column, so there is no scroll target; scrolling falls through to the page.

Additional Context

  • Root cause: packages/app/src/components/status-popover.tsx / status-popover-body.tsx render the lists without a scroll container
  • CSS only adds overflow-y: auto to tabs-content for data-orientation="vertical", which this popover does not use

Suggested fix

  • Add max-height (e.g., 60vh) and overflow-y-auto to the popover body or tab content
  • Or wrap the entry lists in a scroll-view container

Related known issues (similar popover/file-tree rendering gaps, not this exact symptom searched under issue)

  • #28906/#28918 file tree does not render
  • #34223 file tree toggle hidden by desktop gate

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.