Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: Control UI Skills Search Box Shows Gateway URL Instead of Empty [1 pull requests, 1 comments, 2 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#53648•Fetched 2026-04-08 01:25:21
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
HelloMemeHelloMeme
Participants
HelloMemeHelloMemeHollychou924Hollychou924
Timeline (top)
labeled ×2commented ×1cross-referenced ×1

In the OpenClaw Control UI, the search box in the left-side skills menu displays the gateway WebSocket address ws://127.0.0.1:xxxxxx by default, instead of being empty or showing placeholder text.

Root Cause

Search box shows: ws://127.0.0.1:xxxxx Users need to manually delete this text to search for skills At first glance, it appears there are no skills because the search box is filled with the gateway address

Fix Action

Fixed

PR fix notes

PR #53663: fix(ui): prevent skills search autofill

Description (problem / solution / changelog)

Summary

  • mark both skills search fields as type="search" and disable browser text helpers that can repopulate saved gateway values
  • add browser tests for the global Skills tab and per-agent Skills panel to lock the input attributes

Testing

  • npx vitest run src/ui/views/skills.browser.test.ts src/ui/views/agents-panels-tools-skills.browser.test.ts --config vitest.config.ts
  • pnpm check

Risk

  • low; only touches search input attributes and adds focused browser coverage

Closes #53648

Changed files

  • ui/src/ui/views/agents-panels-tools-skills.browser.test.ts (modified, +62/-1)
  • ui/src/ui/views/agents-panels-tools-skills.ts (modified, +4/-0)
  • ui/src/ui/views/skills.browser.test.ts (added, +46/-0)
  • ui/src/ui/views/skills.ts (modified, +4/-0)
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Summary

In the OpenClaw Control UI, the search box in the left-side skills menu displays the gateway WebSocket address ws://127.0.0.1:xxxxxx by default, instead of being empty or showing placeholder text.

Steps to reproduce

Open OpenClaw Control UI (http://127.0.0.1:xxxxx/) Look at the left-side skills menu Observe the default text in the search box

Expected behavior

Search box should be empty or show placeholder text (e.g., "Search skills...") Users should be able to directly type skill names to search

Actual behavior

Search box shows: ws://127.0.0.1:xxxxx Users need to manually delete this text to search for skills At first glance, it appears there are no skills because the search box is filled with the gateway address

OpenClaw version

2026.3.23-2

Operating system

Ubuntu24.04 ARM64

Install method

npm

Model

deepseek-v3

Provider / routing chain

openclaw -> deepseek

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, we need to update the search box in the left-side skills menu to display a placeholder text instead of the gateway WebSocket address.

Steps:

  • Update the HTML template for the search box to include a placeholder attribute.
  • Clear the default value of the search box in the JavaScript code.

Example Code:

<!-- Update the HTML template -->
<input type="search" id="skills-search" placeholder="Search skills...">
// Clear the default value of the search box in JavaScript
document.getElementById('skills-search').value = '';

Alternatively, you can use a framework-specific solution if you're using a JavaScript framework like React or Angular.

React Example:

import React, { useState } from 'react';

function SkillsSearch() {
  const [searchQuery, setSearchQuery] = useState('');

  return (
    <input
      type="search"
      value={searchQuery}
      onChange={(e) => setSearchQuery(e.target.value)}
      placeholder="Search skills..."
    />
  );
}

Verification

To verify that the fix worked, open the OpenClaw Control UI and check that the search box in the left-side skills menu is empty or displays the placeholder text "Search skills...". Users should be able to directly type skill names to search without having to manually delete the gateway address.

Extra Tips

Make sure to update the code in the correct file and restart the application after making changes. If you're using a version control system like Git, commit your changes and push them to the remote repository.

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

Search box should be empty or show placeholder text (e.g., "Search skills...") Users should be able to directly type skill names to search

#api#ssr#installation#tensor shape#autograd error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING