openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@368c21e211
Some checks failed
Pages / Build and deploy (push) Has been cancelled
Details

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-05-08 23:02:43 +00:00
parent 275dfa0a76
commit 54a783e166
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.openclaw-sync/source.json
View File

@ -1,15 +1,15 @@
{
"repository": "openclaw/openclaw",
"sha": "2f26025085112c182796711a4e55f5cfbe38fe61",
"sha": "368c21e2118d203e6d83b00f0c2473596f8796a0",
"sources": {
"openclaw": {
"repository": "openclaw/openclaw",
"sha": "2f26025085112c182796711a4e55f5cfbe38fe61"
"sha": "368c21e2118d203e6d83b00f0c2473596f8796a0"
},
"clawhub": {
"repository": "openclaw/clawhub",
"sha": "5b63d5df6071a91cfd3e5e184bc44e212e977cc9"
}
},
"syncedAt": "2026-05-08T21:14:13.598Z"
"syncedAt": "2026-05-08T23:01:10.684Z"
}

2
docs/gateway/doctor.md
View File

@ -489,7 +489,7 @@ That stages grounded durable candidates into the short-term dreaming store while
<Accordion title="17. Gateway runtime best practices">
Doctor warns when the gateway service runs on Bun or a version-managed Node path (`nvm`, `fnm`, `volta`, `asdf`, etc.). WhatsApp + Telegram channels require Node, and version-manager paths can break after upgrades because the service does not load your shell init. Doctor offers to migrate to a system Node install when available (Homebrew/apt/choco).
Newly installed or repaired macOS LaunchAgents use a canonical system PATH (`/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin`) instead of copying the interactive shell PATH, so Volta, asdf, fnm, pnpm, and other version-manager directories do not change which Node child processes resolve. Linux services still keep explicit environment roots (`NVM_DIR`, `FNM_DIR`, `VOLTA_HOME`, `ASDF_DATA_DIR`, `BUN_INSTALL`, `PNPM_HOME`) and stable user-bin directories, but guessed version-manager fallback directories are only written to the service PATH when those directories exist on disk.
Newly installed or repaired macOS LaunchAgents use a canonical system PATH (`/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin`) instead of copying the interactive shell PATH, so Homebrew-managed system binaries remain available while Volta, asdf, fnm, pnpm, and other version-manager directories do not change which Node child processes resolve. Linux services still keep explicit environment roots (`NVM_DIR`, `FNM_DIR`, `VOLTA_HOME`, `ASDF_DATA_DIR`, `BUN_INSTALL`, `PNPM_HOME`) and stable user-bin directories, but guessed version-manager fallback directories are only written to the service PATH when those directories exist on disk.
</Accordion>
<Accordion title="18. Config write + wizard metadata">