Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: gateway install --force generates PATH entries that doctor flags as non-minimal [1 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#75220•Fetched 2026-05-01 05:36:43
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
3
Author
renaudcerratorenaudcerrato
Participants
aaajiaoaaajiaoclawsweeper[bot]clawsweeper[bot]renaudcerratorenaudcerrato
Timeline (top)
commented ×2cross-referenced ×2labeled ×1

openclaw gateway install --force generates a gateway service PATH that openclaw doctor immediately warns is non-minimal, so the repair path recreates the warned-about state.

Root Cause

openclaw gateway install --force generates a gateway service PATH that openclaw doctor immediately warns is non-minimal, so the repair path recreates the warned-about state.

Fix Action

Fixed

PR fix notes

PR #71619: fix(daemon): keep Linux minimal service PATH truly minimal

Description (problem / solution / changelog)

Summary

  • stop treating Linux version-manager directories as part of the daemon's minimal service PATH
  • keep stable user bin directories like ~/.local/bin, ~/.npm-global/bin, ~/bin, Nix profiles, and pnpm
  • update Linux PATH tests to lock in the hardened-PATH behavior from #71578

Testing

  • pnpm test -- --run src/daemon/service-env.test.ts src/daemon/service-audit.test.ts

Closes #71578

Changed files

  • src/daemon/service-env.test.ts (modified, +38/-16)
  • src/daemon/service-env.ts (modified, +26/-19)
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

openclaw gateway install --force generates a gateway service PATH that openclaw doctor immediately warns is non-minimal, so the repair path recreates the warned-about state.

Steps to reproduce

  1. Run openclaw gateway install --force on Linux with user systemd.
  2. Inspect the generated unit PATH with systemctl --user cat openclaw-gateway.service.
  3. Run openclaw doctor or openclaw gateway status.
  4. Observe that the generated PATH includes entries like ~/.volta/bin, ~/.asdf/shims, ~/.nvm/current/bin, ~/.fnm/current/bin, and ~/.local/share/pnpm, and that doctor warns those entries are non-minimal.

Expected behavior

openclaw gateway install --force should generate a service PATH that openclaw doctor accepts as minimal, or openclaw doctor should treat the installer-generated PATH as valid, so the recommended repair path does not recreate the warning.

Actual behavior

openclaw gateway install --force generates a service PATH containing version-manager and package-manager directories such as ~/.volta/bin, ~/.asdf/shims, ~/.nvm/current/bin, ~/.fnm/current/bin, and ~/.local/share/pnpm, and openclaw doctor then warns that those same entries make the PATH non-minimal.

OpenClaw version

2026.4.29

Operating system

Ubuntu 24.04.4

Install method

npm

Model

minimax 2.7

Provider / routing chain

openclaw / direct

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The openclaw gateway install --force command generates a non-minimal PATH, which is then warned about by openclaw doctor, suggesting a potential issue with the installer's PATH generation logic.

Guidance

  • Review the openclaw gateway install --force command's logic for generating the service PATH to ensure it excludes version-manager and package-manager directories.
  • Verify that the openclaw doctor warning is indeed caused by the presence of these directories in the PATH.
  • Consider modifying the openclaw gateway install --force command to generate a minimal PATH or updating openclaw doctor to accept the installer-generated PATH as valid.
  • Inspect the systemctl --user cat openclaw-gateway.service output to confirm the generated PATH includes the warned-about entries.

Example

No code snippet is provided as the issue does not contain sufficient information to generate a specific example.

Notes

The issue seems to be related to the openclaw gateway install --force command's PATH generation logic and the openclaw doctor warning. However, without more information about the expected behavior of these commands, it is difficult to provide a definitive solution.

Recommendation

Apply workaround: Modify the openclaw gateway install --force command to generate a minimal PATH or update openclaw doctor to accept the installer-generated PATH as valid, as this seems to be the most direct way to address the issue.

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

openclaw gateway install --force should generate a service PATH that openclaw doctor accepts as minimal, or openclaw doctor should treat the installer-generated PATH as valid, so the recommended repair path does not recreate the warning.

#embedding generation#cache error#pipeline error#runtime error#dependency conflict

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix [Bug]: gateway install --force generates PATH entries that doctor flags as non-minimal [1 pull requests, 2 comments, 3 participants]