i like it, thanks! Some button-icons are missing,

[danilovmy]

In TAB chat view, native view (not browser layout)
Below right i see a strange buttons.

windows 10 , companion version 0.6.3.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 20, 2026, 5:12 AM ET / 09:12 UTC.

Summary
Keep this issue open: the reporter’s Windows 10 screenshot matches a current native chat source path where composer action icons still hardcode Segoe Fluent Icons, while the repository already has a cross-version icon-font helper/fallback pattern.

Reproducibility: yes. from the provided Windows 10 screenshot and current-main source: the native composer action row uses exact Segoe Fluent Icons font selection for the reported buttons. I did not run a live Windows 10 UI reproduction in this Linux review environment.

Next step
A focused repair can replace hardcoded native chat icon font usage with the existing cross-version icon fallback pattern and add a regression guard.

Review details

Best possible solution:

Fix the native chat icon rendering by using the existing SymbolThemeFontFamily/FluentIconCatalog pattern or an explicit MDL2 fallback for composer and adjacent chat action glyphs, then verify on Windows 10.

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

Yes, from the provided Windows 10 screenshot and current-main source: the native composer action row uses exact Segoe Fluent Icons font selection for the reported buttons. I did not run a live Windows 10 UI reproduction in this Linux review environment.

Is this the best way to solve the issue?

Yes, a narrow font fallback/helper repair is the best path; this does not need a new feature, setting, or chat workflow change.

AGENTS.md: found, but no applicable review policy affected this item.

Remaining risk / open question:

• I did not live-run current main on a Windows 10 WinUI desktop; the confidence comes from the reporter’s screenshot plus current source inspection.
• Other native chat/A2UI icon TextBlocks also use exact Segoe Fluent Icons, so a fix should avoid repairing only the visible composer row if adjacent Windows 10 icon paths share the same failure.

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

Label changes

Label changes:

• add P2: The issue is a normal-priority native chat UI bug in a released Windows 10 setup with limited blast radius.
• add impact:other: The report affects visible native chat controls, which is maintainer-visible UI impact outside the owned data/auth/session taxonomy.
• add issue-rating: 🐚 platinum hermit: Current issue advisory state selects this label.
• add clawsweeper:needs-live-repro: Current issue advisory state selects this label.

Label justifications:

• P2: The issue is a normal-priority native chat UI bug in a released Windows 10 setup with limited blast radius.
• impact:other: The report affects visible native chat controls, which is maintainer-visible UI impact outside the owned data/auth/session taxonomy.

Evidence reviewed

Acceptance criteria:

• ./build.ps1
• dotnet test ./tests/OpenClaw.Shared.Tests/OpenClaw.Shared.Tests.csproj --no-restore
• dotnet test ./tests/OpenClaw.Tray.Tests/OpenClaw.Tray.Tests.csproj --no-restore
• Manual Windows 10 native chat smoke: open the Hub Chat tab in native mode and verify the attach, voice, speaker, tool-toggle, send, and stop icons render instead of boxes.

What I checked:

• Issue screenshot proof: The downloaded issue image shows the native chat composer action row rendering five button icons as missing-glyph boxes on Windows 10/v0.6.3.
• Current-main source still hardcodes the icon font: The native composer IconButton helper sets each glyph TextBlock to new FontFamily("Segoe Fluent Icons"), which is consistent with Windows 10 rendering missing glyph boxes when that font is unavailable. (src/OpenClaw.Tray.WinUI/Chat/OpenClawComposer.cs:688, c0514bd2d026)
• Affected composer action row: The affected action row builds attach, voice, speaker, tool-toggle, send, and stop buttons from those glyph TextBlocks, matching the lower-right buttons shown in the report. (src/OpenClaw.Tray.WinUI/Chat/OpenClawComposer.cs:711, c0514bd2d026)
• Existing fallback pattern exists: FluentIconCatalog.Build already routes PUA glyphs through SymbolThemeFontFamily, with source comments explicitly naming the Windows 10 MDL2 fallback path. (src/OpenClaw.Tray.WinUI/Helpers/FluentIconCatalog.cs:106, b175439fbfd4)
• Latest release also contains the bug path: The v0.6.3 tag source still uses new FontFamily("Segoe Fluent Icons") in the native composer, so the reporter’s release and current main both need the fallback repair. (src/OpenClaw.Tray.WinUI/Chat/OpenClawComposer.cs:709, 85445c78066b)
• No canonical duplicate found: GitHub searches for the central problem did not find a viable existing issue or PR owning missing Windows 10 native chat icons; the provided referencing merged PRs are unrelated setup/auth changes whose bodies only mention test counts or older issue numbers.

Likely related people:

• AlexAlves87: Blame and PR search tie the native composer and icon catalog introduction to merged PR refactor: extract WslGatewayKeepAliveService from App.xaml.cs #605, including the hardcoded composer icon font and the fallback helper. (role: introduced behavior; confidence: high; commits: b175439fbfd4; files: src/OpenClaw.Tray.WinUI/Chat/OpenClawComposer.cs, src/OpenClaw.Tray.WinUI/Helpers/FluentIconCatalog.cs)
• kenehong: Merged PR Show chat usage in assistant timestamp footer #551 recently changed the native chat composer and timeline around usage/action presentation, including several current lines in the action row. (role: recent area contributor; confidence: medium; commits: ff38d8499c48; files: src/OpenClaw.Tray.WinUI/Chat/OpenClawComposer.cs, src/OpenClaw.Tray.WinUI/Chat/OpenClawChatTimeline.cs)
• ranjeshj: Merged PR Apply bkudiess tray UX PR stack #780 recently touched FluentIconCatalog.cs and broad tray UX surfaces that already use the theme icon-font pattern. (role: adjacent owner; confidence: medium; commits: 429be9ba9368; files: src/OpenClaw.Tray.WinUI/Helpers/FluentIconCatalog.cs, src/OpenClaw.Tray.WinUI/Windows/HubWindow.xaml, src/OpenClaw.Tray.WinUI/Pages/SessionsPage.xaml)

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.

[clawsweeper]

🦞⚠️
Automatic implementation stopped before completion.
Reason: The automatic implementation worker stopped before all deterministic gates completed. Open the workflow run for the exact blocker.
Worker: https://github.com/openclaw/clawsweeper/actions/runs/27866675253

[shanselman]

@danilovmy this is super interesting, we haven't tested on Windows 10. I wonder if you're missing a font? Checking on this

[shanselman]

@niels9001 what do you think

[niels9001]

@niels9001 what do you think

Copilots PR is The Way: Segoe Fluent Icons only ships inbox with Windows 11, not Windows 10. So we'd need to bundle it with the app or use SymbolThemeFontFamily instead. The latter ensures that Segoe Fluent Icons is used, or when not available (like on Windows 10), fallbacks to Segoe MDL2 Assets.

[danilovmy]

@shanselman thanks.
after update today 21.06.2026 + installing Segoe Fluent Icons on windows 10 all works.
I did it all together, and can not say, what exactly helps: change the version or font.