openclaw - 💡(How to fix) Fix MC Skills UI: gateway path label shows wrong profile directory [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#60504Fetched 2026-04-08 02:50:16
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Timeline (top)
commented ×1
RAW_BUFFERClick to expand / collapse

Bug Report

Summary: In Mission Control Skills section, the gateway path label incorrectly shows ~/.openclaw/skills (gateway) even when running under a non-default profile.

Steps to Reproduce:

  1. Run OpenClaw with a non-default profile (e.g. --profile new)
  2. Open Mission Control and navigate to Skills
  3. Observe the gateway path label on custom skills

Expected: ~/.openclaw-new/skills (gateway) Actual: ~/.openclaw/skills (gateway)

Impact: Cosmetic only. Verified that skills are correctly loaded from the active profile directory, hot-reload works, and creating a skill via MC correctly writes to the active profile. The label is just hardcoded to the default profile path instead of resolving against the active profile.

Environment: Windows 10, OpenClaw profile: new

extent analysis

TL;DR

Update the gateway path label in Mission Control to use the active profile directory instead of the hardcoded default profile path.

Guidance

  • Verify that the active profile directory is correctly set when running OpenClaw with a non-default profile.
  • Check the code responsible for rendering the gateway path label in Mission Control to see where the hardcoded default profile path is being used.
  • Update the code to use a variable or function that resolves to the active profile directory, such as ~/.openclaw-<profile_name>/skills.
  • Test the updated code with different profiles to ensure the gateway path label is correctly displayed.

Example

# assuming a function get_active_profile_dir() that returns the active profile directory
gateway_path_label = f"{get_active_profile_dir()}/skills (gateway)"

Notes

This fix assumes that the active profile directory is correctly set and accessible when running OpenClaw with a non-default profile. If the issue persists after updating the code, further investigation into the profile management and directory resolution may be necessary.

Recommendation

Apply workaround: update the code to use the active profile directory, as this is a cosmetic issue and does not affect the functionality of OpenClaw.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING