Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Control UI: long exec approval cards can be slow/unscrollable, hiding allow buttons [1 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#60125•Fetched 2026-04-08 02:35:59
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
c-mholmc-mholm
Participants
c-mholmc-mholm

In OpenClaw Control UI, approval cards for long exec commands can render so slowly / with such poor scroll behavior that the Allow buttons are not reachable.

Root Cause

In OpenClaw Control UI, approval cards for long exec commands can render so slowly / with such poor scroll behavior that the Allow buttons are not reachable.

Fix Action

Fix / Workaround

In this incident, the user had to use browser devtools/inspect console to trigger allow-always as a workaround.

Impact

  • Blocks or severely delays admin operations.
  • Increases risk of mistaken approvals (user can’t comfortably review or interact).
  • Encourages unsafe workaround behavior via devtools.

Workaround used

  • Browser devtools/inspect console to trigger allow-always.
RAW_BUFFERClick to expand / collapse

Bug report draft: Control UI approval cards can become unusable when command is long

Summary

In OpenClaw Control UI, approval cards for long exec commands can render so slowly / with such poor scroll behavior that the Allow buttons are not reachable.

Environment

  • OpenClaw version: 2026.4.1 (da64a97)
  • Surface: Control UI (openclaw-control-ui)
  • Host: Linux 6.8.0-106-generic, Node 22.22.0
  • Context: exec approval flow for gateway-host commands

What happened

When a long command is submitted for approval, the approval card:

  1. takes a long time to appear, and/or
  2. is too long to interact with reliably,
  3. with the bottom action area (allow-once, allow-always, deny) effectively unreachable in normal UI interaction.

In this incident, the user had to use browser devtools/inspect console to trigger allow-always as a workaround.

Expected behavior

  • Approval card should render quickly and remain responsive.
  • Command content should be scrollable without hiding critical action buttons.
  • Action buttons should remain pinned/sticky and always reachable.
  • Very long commands should be collapsed by default (expand/copy), not force giant card layouts.

Actual behavior

  • Card feels hung / delayed.
  • Long command body dominates UI.
  • Buttons are hard or impossible to reach by normal scrolling.

Reproduction (high level)

  1. In Control UI, trigger an exec that requests approval and includes a long multiline command.
  2. Wait for approval card.
  3. Attempt to scroll to and click allow buttons.
  4. Observe lag and/or inaccessible action controls.

Impact

  • Blocks or severely delays admin operations.
  • Increases risk of mistaken approvals (user can’t comfortably review or interact).
  • Encourages unsafe workaround behavior via devtools.

Workaround used

  • Browser devtools/inspect console to trigger allow-always.

Suggestions

  • Make action footer sticky.
  • Cap visible command preview height with internal scroll area.
  • Add explicit "Copy full command" and "Expand" controls.
  • Add loading/ready indicator for approval card lifecycle.
  • Add keyboard shortcut fallback for actions.

Notes

Observed during install-recovery session where approvals were frequent; problem was especially noticeable on long command cards.

extent analysis

TL;DR

Implementing a sticky action footer and capping the visible command preview height with an internal scroll area can improve the usability of approval cards for long commands.

Guidance

  • Make the action footer sticky to ensure that the Allow buttons are always reachable, regardless of the command length.
  • Introduce a cap on the visible command preview height and add an internal scroll area to prevent the command from dominating the UI.
  • Consider adding explicit "Copy full command" and "Expand" controls to improve user interaction with long commands.
  • Add a loading/ready indicator for the approval card lifecycle to provide feedback to the user during the rendering process.

Example

<!-- Example of a sticky action footer -->
<div style="position: sticky; bottom: 0;">
  <button>Allow Once</button>
  <button>Allow Always</button>
  <button>Deny</button>
</div>

Notes

These suggestions focus on improving the usability of approval cards for long commands, but may not address the underlying performance issue causing the delay in rendering.

Recommendation

Apply the suggested workaround by implementing a sticky action footer and capping the visible command preview height, as this can provide an immediate improvement to the usability of approval cards for long commands.

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

  • Approval card should render quickly and remain responsive.
  • Command content should be scrollable without hiding critical action buttons.
  • Action buttons should remain pinned/sticky and always reachable.
  • Very long commands should be collapsed by default (expand/copy), not force giant card layouts.
#GPU setup#container setup#orchestration issue#cache issue#memory leak

Still need to ship something?

×6

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

Back to top recommendations

TRENDING