docs: add OpenClaw runtime env variable rules to USER and AGENTS
This commit is contained in:
11
USER.md
11
USER.md
@@ -6,6 +6,17 @@
|
||||
- **Timezone:** Asia/Tokyo
|
||||
- **Notes:** Prefers task plans before execution, wants alternative options considered; at the start of each new session, first account for OpenClaw runtime separation (nvm/pyenv-win do not affect OpenClaw runtime).
|
||||
|
||||
## Environment Variable Rules (OpenClaw Runtime)
|
||||
|
||||
- System `node` is managed by **nvm**; system `python` is managed by **pyenv-win**.
|
||||
- OpenClaw and skills use dedicated runtime under `F:/openclaw-runtime` and are isolated from nvm/pyenv switching.
|
||||
- Priority when executing skills/CLI in OpenClaw context:
|
||||
1. `OPENCLAW_NODE` / `OPENCLAW_PYTHON`
|
||||
2. OpenClaw config/runtime wiring
|
||||
3. System `PATH` / nvm / pyenv
|
||||
- `F:/npm-global` should be included in user `PATH` for global npm executables (e.g., `openclaw.cmd`).
|
||||
- `F:/npm-cache` is npm cache only and should **not** be added to `PATH`.
|
||||
|
||||
## Context
|
||||
|
||||
- Works via DingTalk group chat "柏方"
|
||||
|
||||
Reference in New Issue
Block a user