openclaw - ✅(Solved) Fix [Bug]: OpenClaw Control UI: Slash Command Menu Position Bug [2 pull requests, 2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#52089Fetched 2026-04-08 01:15:46
View on GitHub
Comments
2
Participants
3
Timeline
9
Reactions
0
Timeline (top)
referenced ×3commented ×2cross-referenced ×2labeled ×2

The slash command menu (/) is rendered off-screen (negative top position), making it invisible to users.

Root Cause

The slash command menu (/) is rendered off-screen (negative top position), making it invisible to users.

Fix Action

Fixed

PR fix notes

PR #52100: fix(ui): slash command menu rendered off-screen due to overflow:hidden

Description (problem / solution / changelog)

Summary

  • Fix slash command menu (/) being rendered off-screen at top: -324px in the Control UI chat interface
  • The .agent-chat__input container had overflow: hidden which clips the absolutely-positioned .slash-menu element (positioned above the input with bottom: 100%)
  • This regression was introduced during the CSS refactor in f4227e278

Changes

  • Changed overflow: hidden to overflow: visible on .agent-chat__input in ui/src/styles/chat/layout.css

Test plan

  • Open Control UI chat interface
  • Type / in the message input
  • Verify the slash command menu appears above the input box (not off-screen)
  • Verify the input box border-radius and visual appearance are preserved

Fixes #52089

🤖 Generated with Claude Code

Changed files

  • ui/src/styles/chat/layout.css (modified, +1/-1)

PR #52129: fix(control-ui): remove overflow:hidden that clipped slash command menu

Description (problem / solution / changelog)

Summary

  • Remove overflow: hidden from .agent-chat__input that created a clipping context hiding the absolutely-positioned .slash-menu
  • The menu uses position: absolute; bottom: 100% to render above the input, but overflow: hidden on the parent clipped it off-screen at top: -324px
  • border-radius still rounds the box's background/border without clipping positioned children

Root Cause

Commit f76a3c5225 (feat(ui): dashboard-v2 views refactor) introduced .agent-chat__input with overflow: hidden. The old .chat-compose container did not have this property. The slash menu, positioned absolutely above the container, became invisible.

Test plan

  • npm run build passes
  • Open Control UI → click input → press / → slash command menu appears above the input
  • Verify input box border-radius still renders correctly

Fixes #52089

🤖 Generated with Claude Code

Changed files

  • ui/src/styles/chat/layout.css (modified, +3/-1)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

Summary

The slash command menu (/) is rendered off-screen (negative top position), making it invisible to users.

Environment

  • OpenClaw Version: 2026.3.13
  • Browser: Chrome (latest)
  • OS: macOS 26.3.1 (arm64)
  • Gateway Mode: Local (http://127.0.0.1:18789)

Steps to reproduce

  1. Open OpenClaw Control UI (http://127.0.0.1:18789)
  2. Navigate to Chat interface
  3. Click on the message input textarea
  4. Press / key

Expected behavior

A command menu should appear above the input box showing available commands like /new, /reset, /status, etc.

Actual behavior

The command menu is rendered but positioned off-screen at top: -324px, making it invisible to the user.

OpenClaw version

2026.03.13

Operating system

macos 26.3.1

Install method

No response

Model

Kimi K2.5

Provider / routing chain

moonshot/kimi-k2.5

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

To fix the issue of the slash command menu being rendered off-screen, we need to adjust the CSS styling to ensure the menu is positioned correctly.

Step-by-Step Solution:

  1. Identify the CSS class responsible for the positioning of the command menu.
  2. Adjust the top property in the CSS to position the menu above the input box.
  3. Add a CSS rule to handle cases where the menu might still be cut off due to screen size or other elements.

Example Code:

/* Assuming the command menu's class is `.command-menu` */
.command-menu {
  position: absolute;
  top: 0; /* Adjust this value based on your layout */
  left: 0;
  background-color: #f9f9f9;
  border: 1px solid #ccc;
  padding: 10px;
  z-index: 1; /* Ensure it's on top of other elements */
}

/* Optional: Media query to handle different screen sizes */
@media (max-height: 768px) {
  .command-menu {
    top: auto;
    bottom: 40px; /* Assuming input box height is about 40px */
  }
}

Verification

  • Open the OpenClaw Control UI in Chrome.
  • Navigate to the Chat interface.
  • Click on the message input textarea.
  • Press the / key.
  • The command menu should now appear above the input box and be fully visible.

Extra Tips

  • Ensure that the CSS changes are applied correctly by checking the browser's developer tools.
  • Test the fix across different screen sizes and devices to ensure compatibility.
  • Consider adding JavaScript logic to dynamically adjust the menu's position based on the input box's position and screen size for a more robust solution.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

A command menu should appear above the input box showing available commands like /new, /reset, /status, etc.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING