Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix [Feedback] The OpenClaw workspace detection tip feels hostile/unprofessional [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
NousResearch/hermes-agent#16629•Fetched 2026-04-28 06:52:06
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
lizhelong0907lizhelong0907
Participants
lizhelong0907lizhelong0907
Timeline (top)
labeled ×3

Error Message

  1. Running hermes claw cleanup archives the OpenClaw directory, which breaks OpenClaw for users who still want to use it. The tip doesn't warn about this side effect.
RAW_BUFFERClick to expand / collapse

The onboarding tip 'Heads up — an OpenClaw workspace was detected at ~/.openclaw/...' has a needlessly hostile tone.

Issues:

  1. .openclaw and .hermes are completely separate directories — there is no actual conflict.
  2. The phrasing ('can still get confused', 'instead of Hermes's') implies OpenClaw is a problem to be eliminated rather than a legacy setup to optionally migrate.
  3. Running hermes claw cleanup archives the OpenClaw directory, which breaks OpenClaw for users who still want to use it. The tip doesn't warn about this side effect.
  4. The tip says the agent 'dutifully reads' OpenClaw config — this framing is confusing and sounds like a bug report rather than a neutral migration notice.

Suggested improvement: The message could simply say: 'A legacy OpenClaw directory was detected. If you'd like to migrate your config and skills to Hermes, run hermes claw migrate. To see this message again: hermes claw cleanup --dry-run.'

That is factual, non-judgmental, and doesn't make users feel like they're doing something wrong by having OpenClaw installed.

extent analysis

TL;DR

Update the onboarding tip message to a neutral, informative tone that suggests migration to Hermes without implying conflict with OpenClaw.

Guidance

  • Review the current onboarding tip message for tone and accuracy, ensuring it does not imply OpenClaw is a problem.
  • Consider rephrasing the message to focus on the option to migrate to Hermes, using language similar to the suggested improvement.
  • Verify that running hermes claw cleanup archives the OpenClaw directory and ensure the tip warns about this side effect or provides an alternative to preserve OpenClaw functionality.
  • Test the revised message with users to ensure it is clear and non-judgmental.

Example

The suggested improvement provides a clear example of a revised message: 'A legacy OpenClaw directory was detected. If you'd like to migrate your config and skills to Hermes, run hermes claw migrate. To see this message again: hermes claw cleanup --dry-run.'

Notes

The solution assumes that the goal is to maintain support for both OpenClaw and Hermes, allowing users to choose their preferred setup without feeling pressured to migrate.

Recommendation

Apply workaround: Update the onboarding tip message to a neutral tone, as suggested, to improve user experience and clarity regarding the relationship between OpenClaw and Hermes.

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…
#API middleware#SSR setup#ISR setup#authentication setup#request 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