Skip to content

[Bug]: Chat workspace rail sections have no scrollbar, file list overflows #98566

Description

@645648406-max

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Chat workspace rail sections (.chat-workspace-rail__section) have overflow-y: visible by default. When the file list is long (40+ files), content overflows without a scrollbar.

Steps to reproduce

  1. Open /chat page
  2. Click "展开会话工作区" (expand workspace rail)
  3. Navigate to a workspace directory with many files (e.g. root with 40+ files)
  4. Observe the "项目文件" section content overflows without a scrollbar

Expected behavior

Each .chat-workspace-rail__section should have overflow-y: auto. When file list exceeds container height, a scrollbar should appear and content should not overflow.

Actual behavior

Section scrollHeight (1760px) >> clientHeight (502px). Content overflows container bounds. The parent .chat-workspace-rail__scroll has overflow-y: auto, but child sections default to overflow: visible, so content leaks out.

OpenClaw version

2026.6.11

Operating system

Windows 10

Install method

npm global

Model

N/A (UI bug)

Provider / routing chain

N/A (UI bug)

Additional provider/model setup details

No response

Logs

Screenshots, recordings, and evidence

No response

Impact and severity

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.bugSomething isn't workingclawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.no-staleExclude from stale automationregressionBehavior that previously worked and now fails

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions