OpenClaw's Control UI command palette has a small but noticeable readability fix: opening it no longer blurs the entire session behind it.
The change landed in PR #142944, titled fix(ui): keep command palette background readable. The bug affected users who opened the palette with Cmd/Ctrl+K and still needed to reference the session beneath it. The shared modal backdrop blurred the whole background, making session names, recent messages, and composer context harder to read.
Command palettes work best when they feel like an overlay on top of current work, not a full interruption. If a user opens the palette to jump, search, or run an action, the surrounding context often matters.
What Changed
The command palette now overrides the shared modal backdrop for this specific surface. Blur is disabled, while a subtle 12% theme-aware dim remains.
Other modals keep their existing backdrop behavior. That separation matters because the palette has different ergonomics from a modal dialog. A confirmation or settings modal may reasonably push the rest of the interface into the background. A command palette is often used while scanning the current session.
According to the PR, the change is limited to two files, with 25 additions and no deletions. It is a focused UI fix rather than a larger redesign.
The Practical Difference
The user impact is simple: session names, messages, and composer context remain legible while the command palette is open in light or dark mode.
That improves several common workflows:
- Switching sessions while checking the current thread name.
- Running a command based on the visible message context.
- Searching commands without losing the visual anchor of the current workspace.
- Using keyboard navigation without the interface feeling visually disconnected.
The PR includes before-and-after screenshots for both dark and light themes. In the before state, the underlying sessions are blurred. In the after state, the command palette still stands apart, but the background remains readable.
Validation
The PR reports direct verification that the palette backdrop computes to backdrop-filter: none with 12% dimming in both themes. It also confirms keyboard navigation, focus trapping, Escape dismissal, outside-click dismissal, and focus restoration.
The generic modal path was checked too, and it retains the existing blur(4px) backdrop. That is a useful guardrail because the fix should not flatten every modal in the app just to repair the command palette.
Focused component tests passed with 62 tests green. The command palette end-to-end checks passed across desktop and phone viewports, covering both loading and loaded states. The PR also reports node scripts/check-changed.mjs passing and an independent scoped review with no actionable P2 issues.
The author notes one limitation: attaching to an existing live Chrome session was not possible because Chrome was not running, and the task did not allow restarting the operator Gateway or mutating live configuration. The proof therefore comes from isolated Playwright Chromium against a mocked Gateway fixture, not an authenticated live-Gateway session.
Why It Matters
This is the kind of detail that makes a dense operational UI feel better under repeated use. OpenClaw's Control UI is where users steer sessions, inspect work, and jump between tools. The command palette should help that flow, not erase the very context that tells users what they want to do next.
No new command model shipped here. No dramatic feature flag. Just a targeted readability fix that makes Cmd/Ctrl+K less disorienting.