Add startup reminder for OpenClaw runtime isolation from nvm/pyenv-win
This commit is contained in:
@@ -14,6 +14,9 @@ Before doing anything else:
|
||||
2. Read `USER.md` — this is who you're helping
|
||||
3. Read `memory/YYYY-MM-DD.md` (today + yesterday) for recent context
|
||||
4. **If in MAIN SESSION** (direct chat with your human): Also read `MEMORY.md`
|
||||
5. Always remember runtime separation at session start:
|
||||
- System Node is managed by nvm, but OpenClaw/skills use dedicated Node in `F:/openclaw-runtime` and are not affected by nvm switching.
|
||||
- System Python is managed by pyenv-win, but OpenClaw uses its own dedicated Python environment and is not affected by pyenv switching.
|
||||
|
||||
Don't ask permission. Just do it.
|
||||
|
||||
|
||||
2
USER.md
2
USER.md
@@ -4,7 +4,7 @@
|
||||
- **What to call them:** Fang
|
||||
- **Pronouns:** (unknown)
|
||||
- **Timezone:** Asia/Tokyo
|
||||
- **Notes:** Prefers task plans before execution, wants alternative options considered
|
||||
- **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).
|
||||
|
||||
## Context
|
||||
|
||||
|
||||
Reference in New Issue
Block a user