[Bug]: Windows Desktop UI clips config panels and chat bubbles at high display scaling

[Jany-M]

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

1. Control UI overflow: at 4K/300% scaling, the config panel is clipped with no horizontal scrolling or responsive reflow.

1. Chat bubbles clipping: also clip on the right, with neither automatic wrapping nor horizontal scrolling.

Environment:
Windows 11 x64
OpenClaw Windows Desktop v2026.7.1-2
3840×2160 display
300% scaling

Steps to reproduce

1. Install Windows App
2. Go to Gateway -> Advanced -> Config (problem 1)
3. Create a chat, wait for answer (problem 2)

Expected behavior

All panels should be responsive based on screen resolution AND scaling, and at the very list, always have a horizontal scrollbar in all containers.

Actual behavior

Containers dont resize nested panels depending on screen resolution / scaling, impossible to interact with overflowing panels or read chat responses fully, as not even horizontal scrollbar is present.

OpenClaw version

v2026.7.1-2

Operating system

Windows 11

Install method

No response

Model

Qwen 3.6

Provider / routing chain

openclaw -> gateway -> win app

Additional provider/model setup details

No response

Logs

Screenshots, recordings, and evidence

Impact and severity

Hard to use chat or config anything meaningful. Quite blocking.

Additional information

No response

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed September 2, 2026, 1:33 PM ET / 17:33 UTC.

Summary
Keep open. Current main retains the reported release’s relevant Config and chat layout code, and the Config editor has a source-visible narrow-width overflow path; the chat-specific mechanism still needs a native Windows verification.

Reproducibility: no. live current-main reproduction was run. The Config source exposes fixed minimum widths behind a disabled horizontal scroll path, while chat text wrapping means the reported chat clipping needs native Windows confirmation.

Ways to help us reproduce this

• Add expected vs actual behavior.

Maintainer decision needed

Question	Recommendation
Should the high-scale repair standardize on responsive reflow for Config and chat, with horizontal scrolling limited to code or JSON content?	Prefer responsive reflow: Adapt or collapse Config regions at narrow logical widths and preserve wrapping chat bubbles, retaining horizontal scrolling only for code-like content.

Why: The report requests horizontal scrolling everywhere, while current UI already treats JSON as the intentionally scrollable non-wrapping surface; maintainers should set the accessible layout contract before a cross-surface repair.

Next step
The Config path is concrete, but the issue spans two UI owners and needs an agreed responsive-layout policy plus current-head high-DPI confirmation before implementation.

Review details

Best possible solution:

Make the Config editor adapt before its fixed-width columns obscure fields, with scrolling only for inherently non-wrapping content, then validate both Config and native chat at 300% scaling in an isolated WinUI run.

Do we have a high-confidence way to reproduce the issue?

No live current-main reproduction was run. The Config source exposes fixed minimum widths behind a disabled horizontal scroll path, while chat text wrapping means the reported chat clipping needs native Windows confirmation.

Is this the best way to solve the issue?

Unclear. A responsive layout is the likely maintainable direction, but maintainers need to choose whether horizontal scrolling is only a code/JSON fallback or a general UI policy.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The submitted high-DPI screenshots have not been reproduced on current main. The configuration defect is source-supported, but the chat clipping mechanism needs a real Windows run before selecting its precise repair.

Codex review notes: model internal, reasoning high; reviewed against 16cb6897941f.

Label changes

Label changes:

• add P1: At affected display scaling, users report being unable to read chat output or interact with gateway configuration.
• add impact:ux-friction: The desktop UI’s high-scale layout can make essential settings and responses inaccessible, but this is not a first-run release-blocking path.
• add issue-rating: 🐚 platinum hermit: Current issue advisory state selects this label.
• add clawsweeper:needs-live-repro: Current issue advisory state selects this label.
• add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.
• add clawsweeper:needs-maintainer-review: Current issue advisory state selects this label.
• add clawsweeper:needs-product-decision: Current issue advisory state selects this label.

Label justifications:

• P1: At affected display scaling, users report being unable to read chat output or interact with gateway configuration.
• impact:ux-friction: The desktop UI’s high-scale layout can make essential settings and responses inaccessible, but this is not a first-run release-blocking path.

Evidence reviewed

What I checked:

• Config layout has a narrow-width overflow path: The editor grid reserves 300 DIP for the tree and 400 DIP for the detail column even after the JSON pane collapses, while the detail ScrollViewer explicitly disables horizontal scrolling. Generated fields add 300 to 350 DIP minimum widths, so a narrow logical window can leave controls inaccessible. (src/OpenClaw.Tray.WinUI/Pages/ConfigPage.xaml:126, 16cb6897941f)
• Current chat code wraps ordinary bubble text but lacks high-scale coverage: User and assistant bubbles cap their width at 720 DIP, and the shared text builder enables wrapping. This does not establish why the submitted chat image clips, so a real high-DPI run is needed to distinguish Markdown or control-layout overflow from ordinary text rendering. (src/OpenClaw.Tray.WinUI/Chat/ReactorChatTimeline.cs:404, 16cb6897941f)
• The reviewed UI paths are unchanged since the reported release: The Config editor and native chat timeline files compare identically between current main and v2026.7.1-2, the version named in the report. Current main therefore does not demonstrably contain a fix for this layout problem. (src/OpenClaw.Tray.WinUI/Pages/ConfigPage.xaml:121, 16cb6897941f)
• Feature-history routing: History associates the config editor revamp with Ranjesh and the native Reactor chat migration with Karen; both paths have since received additional changes, so these are routing candidates rather than attribution of the report. (src/OpenClaw.Tray.WinUI/Pages/ConfigPage.xaml:121, 9de9b5ba0f8a)

Likely related people:

• Ranjesh: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
• Karen: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[github-actions]

This issue has been automatically marked as stale due to inactivity.
Please add updated OpenClaw Windows details or it will be closed.

[Jany-M]

any update? issue is still relevant in latest OC windows desktop version