@foxden-app/foxclaw 0.3.5 → 0.3.7

package/README.md

@@ -40,7 +40,7 @@ FoxClaw（狸爪）的目标很直接：让你用手机控制本机的 Codex，
 - Git、Node、`.env` 都玩得转？直接往下看快速设置。
 - 卡住了？看 [故障排查](./docs/zh/troubleshooting.md)。
 
-最低要求：一个 Telegram bot token、你的 Telegram 数字用户 ID、Node.js 24、一份已登录的 `codex` CLI。首次安装大约 10–20 分钟。
+最低要求：一个 Telegram bot token、你的 Telegram 数字用户 ID、Node.js 24+、一份已登录的 `codex` CLI。首次安装大约 10–20 分钟。
 
 **30 秒体验**：启动 FoxClaw 后，给你的 Telegram 机器人发一句 `List files in DEFAULT_CWD`。Codex 会在本地检查那个目录，然后把结果发回 Telegram。
 
@@ -70,7 +70,7 @@ foxclaw doctor
 foxclaw start
 ```
 
-`foxclaw init` 会创建 `~/.foxclaw/.env`，并在终端里提示填写 Telegram bot token、Telegram 数字用户 ID 和默认工作目录。任何一项都可以直接回车跳过，之后再用 `$EDITOR ~/.foxclaw/.env` 手动修改。
+`foxclaw init` 会创建 `~/.foxclaw/.env`，并在终端里提示填写 Telegram bot token、Telegram 数字用户 ID 和默认工作目录。如果当前 shell 里有 `HTTP_PROXY`、`HTTPS_PROXY`、`ALL_PROXY` 等代理变量，也会询问是否写入 FoxClaw 配置，避免服务启动后 Codex 走不到同一条网络。任何一项都可以直接回车跳过，之后再用 `$EDITOR ~/.foxclaw/.env` 手动修改。
 
 跑 `doctor` 或 `start` 之前先把 `.env` 填好。私聊模式最小配置：
 

package/README_EN.md

@@ -40,7 +40,7 @@ FoxClaw is more than message forwarding. It provides Telegram panels for Codex w
 - Already comfortable with Git, Node, and `.env` files? Use the quick setup below.
 - Something failed? Check [Troubleshooting](./docs/troubleshooting.md).
 
-The minimum install needs only a Telegram bot token, your numeric Telegram user id, Node.js 24, and a logged-in `codex` CLI. A first install usually takes 10–20 minutes.
+The minimum install needs only a Telegram bot token, your numeric Telegram user id, Node.js 24+, and a logged-in `codex` CLI. A first install usually takes 10–20 minutes.
 
 **30-second demo**: after FoxClaw is running, send `List files in DEFAULT_CWD` to your Telegram bot. FoxClaw asks local Codex to inspect that folder on your computer and sends the answer back to Telegram.
 
@@ -70,7 +70,7 @@ foxclaw doctor
 foxclaw start
 ```
 
-`foxclaw init` creates `~/.foxclaw/.env` and prompts for the Telegram bot token, your numeric Telegram user id, and the default workspace. Press Enter on any field to skip it and edit later with `$EDITOR ~/.foxclaw/.env`.
+`foxclaw init` creates `~/.foxclaw/.env` and prompts for the Telegram bot token, your numeric Telegram user id, and the default workspace. If the current shell has proxy variables such as `HTTP_PROXY`, `HTTPS_PROXY`, or `ALL_PROXY`, it also asks whether to save them into the FoxClaw config so the service uses the same network path as your working Codex CLI. Press Enter on any field to skip it and edit later with `$EDITOR ~/.foxclaw/.env`.
 
 Fill `.env` before running `doctor` or `start`. Minimum private-chat config:
 

package/dist/main.js

@@ -12,6 +12,16 @@ const command = process.argv[2] || 'serve';
 loadEnv();
 const packageRoot = path.dirname(path.dirname(fileURLToPath(import.meta.url)));
 const entryPoint = fileURLToPath(import.meta.url);
+const PROXY_ENV_KEYS = [
+    'HTTP_PROXY',
+    'HTTPS_PROXY',
+    'ALL_PROXY',
+    'NO_PROXY',
+    'http_proxy',
+    'https_proxy',
+    'all_proxy',
+    'no_proxy',
+];
 async function main() {
     if (command === 'init') {
         await initConfig();
@@ -160,6 +170,7 @@ async function initConfig() {
         console.log(`Created ${envPath}`);
     }
     if (!canPromptForInit()) {
+        printProxyEnvHint(envPath);
         console.log(`Edit it manually, then run: foxclaw doctor`);
         return;
     }
@@ -174,6 +185,7 @@ async function configureEnvInteractively(envPath, existed) {
         if (existed) {
             const updateExisting = (await rl.question('Update Telegram/workspace setup fields now? [y/N]: ')).trim().toLowerCase();
             if (updateExisting !== 'y' && updateExisting !== 'yes') {
+                await maybeSaveProxyEnvFromShell(rl, envPath);
                 console.log(`Edit it manually, then run: foxclaw doctor`);
                 return;
             }
@@ -184,6 +196,7 @@ async function configureEnvInteractively(envPath, existed) {
         const updates = {};
         const skipped = [];
         const warnings = [];
+        Object.assign(updates, await maybeSaveProxyEnvFromShell(rl, envPath));
         const token = sanitizeEnvInput(await rl.question('Telegram bot token (TG_BOT_TOKEN): '));
         if (token) {
             updates.TG_BOT_TOKEN = token;
@@ -307,6 +320,64 @@ function writeEnvUpdates(envPath, updates) {
     }
     fs.writeFileSync(envPath, text);
 }
+async function maybeSaveProxyEnvFromShell(rl, envPath) {
+    const proxyUpdates = detectMissingProxyEnv(envPath);
+    const keys = Object.keys(proxyUpdates);
+    if (keys.length === 0) {
+        return {};
+    }
+    console.log(`Detected proxy env in this shell: ${keys.join(', ')}`);
+    const answer = (await rl.question('Save these proxy settings to FoxClaw .env for service use? [Y/n]: ')).trim().toLowerCase();
+    if (answer === 'n' || answer === 'no') {
+        console.log(`Skipped proxy env. Add it to ${envPath} if ChatGPT access needs a proxy.`);
+        return {};
+    }
+    writeEnvUpdates(envPath, proxyUpdates);
+    console.log(`Saved ${keys.join(', ')} to ${envPath}`);
+    return proxyUpdates;
+}
+function printProxyEnvHint(envPath) {
+    const proxyUpdates = detectMissingProxyEnv(envPath);
+    const keys = Object.keys(proxyUpdates);
+    if (keys.length === 0) {
+        return;
+    }
+    console.log(`[WARN] Proxy env detected in this shell but missing from ${envPath}: ${keys.join(', ')}`);
+    console.log(`[WARN] Add those proxy variables to ${envPath} if ChatGPT/Codex needs a proxy.`);
+}
+function detectMissingProxyEnv(envPath) {
+    const existing = readEnvFileKeys(envPath);
+    const existingCanonical = new Set(Array.from(existing, canonicalProxyEnvKey));
+    const updates = {};
+    for (const key of PROXY_ENV_KEYS) {
+        const value = process.env[key]?.trim();
+        if (!value || existing.has(key) || existingCanonical.has(canonicalProxyEnvKey(key))) {
+            continue;
+        }
+        updates[key] = value;
+    }
+    return updates;
+}
+function canonicalProxyEnvKey(key) {
+    return key.toUpperCase();
+}
+function readEnvFileKeys(envPath) {
+    const keys = new Set();
+    let text = '';
+    try {
+        text = fs.readFileSync(envPath, 'utf8');
+    }
+    catch {
+        return keys;
+    }
+    for (const line of text.split(/\r?\n/)) {
+        const match = line.match(/^\s*([A-Za-z_][A-Za-z0-9_]*)\s*=/);
+        if (match?.[1]) {
+            keys.add(match[1]);
+        }
+    }
+    return keys;
+}
 function formatEnvValue(value) {
     const cleaned = value.replace(/[\r\n]/g, '').trim();
     if (!/[\s#"\\]/.test(cleaned))
@@ -376,8 +447,52 @@ function runDoctorChecks() {
         console.log(`[FAIL] default cwd missing: ${cwd}`);
         passed = false;
     }
+    warnIfProxyEnvMissingFromLoadedEnv();
+    warnIfInstalledServiceNodeLooksWrong();
     return passed;
 }
+function warnIfProxyEnvMissingFromLoadedEnv() {
+    const envPath = serviceEnvPath();
+    const proxyUpdates = detectMissingProxyEnv(envPath);
+    const keys = Object.keys(proxyUpdates);
+    if (keys.length === 0) {
+        return;
+    }
+    console.log(`[WARN] proxy env is present in this shell but missing from ${envPath}: ${keys.join(', ')}`);
+    console.log(`[WARN] systemd/launchd services do not inherit your shell; add those variables to the FoxClaw env file if Codex needs a proxy.`);
+}
+function warnIfInstalledServiceNodeLooksWrong() {
+    if (process.platform !== 'linux') {
+        return;
+    }
+    const unitPath = path.join(process.env.XDG_CONFIG_HOME || path.join(process.env.HOME || '', '.config'), 'systemd', 'user', 'foxclaw.service');
+    let text = '';
+    try {
+        text = fs.readFileSync(unitPath, 'utf8');
+    }
+    catch {
+        return;
+    }
+    const execStart = text.match(/^ExecStart=(.+)$/m)?.[1]?.trim();
+    const nodePath = execStart ? systemdUnescape(execStart.split(/\s+/)[0] ?? '') : '';
+    if (!nodePath) {
+        return;
+    }
+    if (!fs.existsSync(nodePath)) {
+        console.log(`[WARN] installed service node is missing: ${nodePath}`);
+        console.log('[WARN] Run foxclaw start from a Node 24 shell to refresh the service unit.');
+        return;
+    }
+    const result = spawnSync(nodePath, ['-p', 'process.versions.node'], { encoding: 'utf8' });
+    const version = result.status === 0 ? result.stdout.trim() : '';
+    const major = Number.parseInt(version.split('.')[0] ?? '', 10);
+    if (Number.isFinite(major) && major >= 24) {
+        console.log(`[OK] service node >= 24: ${nodePath}`);
+        return;
+    }
+    console.log(`[WARN] installed service node is older than 24: ${nodePath}${version ? ` (${version})` : ''}`);
+    console.log('[WARN] Run foxclaw start from a Node 24 shell to refresh the service unit.');
+}
 function installSystemd() {
     if (!hasCommand('systemctl')) {
         console.error('systemctl not found (need systemd)');
@@ -543,6 +658,9 @@ function spawnChecked(commandName, args) {
 function systemdEscape(value) {
     return value.replace(/\\/g, '\\\\').replace(/ /g, '\\x20');
 }
+function systemdUnescape(value) {
+    return value.replace(/\\x20/g, ' ').replace(/\\\\/g, '\\');
+}
 function xmlEscape(value) {
     return value
         .replace(/&/g, '&')

package/docs/agent-assisted-install.md

@@ -39,7 +39,7 @@ DEFAULT_CWD=<paste absolute working directory here>
 
 Tasks:
 1. Inspect the machine first. If a FoxClaw service already exists, report it before changing services.
-2. Ensure Node.js 24+ is available. If not, install or activate Node 24 with nvm.
+2. Ensure Node.js 24+ is available. If not, install or activate Node 24+ by any suitable method; nvm is only one common option.
 3. Ensure the Codex CLI exists and is logged in. If login is required, stop and tell me exactly what I need to do.
 4. Install or update FoxClaw with npm install -g @foxden-app/foxclaw@latest.
 5. Run foxclaw init, then write ~/.foxclaw/.env. Never print or commit the bot token.

package/docs/install-for-beginners.md

@@ -25,17 +25,17 @@ You need:
 
 Use private chat first. Group and topic setup can wait until the bot replies reliably.
 
-## 2. Install Node.js 24
+## 2. Install Node.js 24+
 
-FoxClaw needs Node.js 24 because it uses the built-in SQLite runtime.
+FoxClaw needs Node.js 24+ because it uses the built-in SQLite runtime. It does not require nvm; you can use nvm, fnm, asdf, mise, Volta, Homebrew, or your system package manager.
 
-If you already have Node 24, this should print `v24...`:
+If you already have Node 24+, this should print `v24...` or newer:
 
 ```bash
 node -v
 ```
 
-If not, install Node 24 with `nvm`:
+If not, nvm is a good default for first-time users. Example:
 
 ```bash
 curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash
@@ -47,7 +47,7 @@ node -v
 npm -v
 ```
 
-If `node -v` still shows an old version, close the terminal, open a new one, and run:
+If you use nvm and `node -v` still shows an old version, close the terminal, open a new one, and run:
 
 ```bash
 nvm use 24

package/docs/troubleshooting.md

@@ -18,7 +18,7 @@ journalctl --user -u foxclaw.service -f
 
 | Symptom | Meaning | Fix |
 | --- | --- | --- |
-| `[FAIL] node >= 24` | Your current shell is using an older Node.js. | Run `nvm install 24 && nvm use 24`, then rerun `foxclaw doctor`. If the service uses old Node, reinstall it from a Node 24 shell with `foxclaw start`. |
+| `[FAIL] node >= 24` | Your current shell is using an older Node.js. | Install or activate Node.js 24+ by any method, then rerun `foxclaw doctor`. If the service uses old Node, reinstall it from a Node 24+ shell with `foxclaw start`. |
 | `[FAIL] codex cli available` | The `codex` command is not in PATH. | Install Codex CLI or fix PATH, then confirm `codex --version` works. |
 | `[FAIL] telegram bot token configured` | `TG_BOT_TOKEN` is missing from `.env`. | Copy the token from `@BotFather` into `.env`. |
 | `[FAIL] telegram allowed user configured` | `TG_ALLOWED_USER_ID` is missing from `.env`. | Get your numeric id from `@userinfobot` and add it to `.env`. |
@@ -26,7 +26,7 @@ journalctl --user -u foxclaw.service -f
 
 ## Node Or npm Is Missing
 
-If you see `node: command not found` or `npm: command not found`, install Node.js 24 with `nvm`:
+If you see `node: command not found` or `npm: command not found`, install Node.js 24+ using your preferred tool, such as nvm, fnm, asdf, mise, Volta, Homebrew, or your system package manager. This is an nvm example:
 
 ```bash
 curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash
@@ -38,7 +38,7 @@ node -v
 npm -v
 ```
 
-If it still fails, close the terminal, open a new one, and run:
+If you use nvm and it still fails, close the terminal, open a new one, and run:
 
 ```bash
 nvm use 24
@@ -48,7 +48,7 @@ nvm use 24
 
 If `npm install -g @openai/codex` fails with `EACCES`, `EPERM`, or `permission denied`, your global npm directory is not writable by your user.
 
-Recommended fix: use Node through `nvm`, then install again:
+Recommended fix: use a user-level Node.js 24+ install, then install again. This is an nvm example:
 
 ```bash
 nvm install 24
@@ -56,7 +56,7 @@ nvm use 24
 npm install -g @openai/codex
 ```
 
-Avoid `sudo npm install -g ...` unless you already understand how your Node installation is managed. Mixing `sudo`, system Node, and `nvm` is a common source of broken PATHs.
+Avoid `sudo npm install -g ...` unless you already understand how your Node installation is managed. Mixing `sudo`, system Node, and user-level Node managers is a common source of broken PATHs.
 
 If `codex` installs but FoxClaw still cannot find it, locate the binary:
 
@@ -192,6 +192,8 @@ A common cause is that your shell or project `.env` has proxy variables, while t
 systemctl --user cat foxclaw.service
 ```
 
+`foxclaw init` detects proxy environment variables in the current shell and asks whether to save them into the FoxClaw `.env`. If you skipped that step, `foxclaw doctor` warns when it sees proxy variables in the shell but not in the FoxClaw env file.
+
 Make sure the file referenced by `Environment=FOXCLAW_ENV=...` contains your proxy variables, for example:
 
 ```dotenv
@@ -209,7 +211,9 @@ foxclaw restart
 
 ## Service Starts With The Wrong Node Version
 
-The systemd installer captures the `node` binary from your current PATH. If you installed the service from a shell using Node 22 or older, reinstall it from a Node 24 shell:
+The systemd installer records the absolute path of the Node process that is currently running FoxClaw. It does not rely on systemd loading `nvm.sh` or any other shell init script. Whether you use nvm, fnm, asdf, mise, Volta, Homebrew, or system Node, run `foxclaw start` from a Node 24+ shell and the service will keep using that Node 24+ path.
+
+If you installed the service from a shell using Node 22 or older, reinstall it from a Node 24+ shell. Example for nvm users:
 
 ```bash
 nvm use 24
@@ -217,7 +221,7 @@ foxclaw start
 systemctl --user status foxclaw.service
 ```
 
-The status output should show a Node 24 path in `ExecStart`.
+The status output should show a Node 24+ path in `ExecStart`. `foxclaw doctor` also checks the installed service Node path and warns if it is missing or older than 24.
 
 ## Does It Run After Reboot?
 

package/docs/user-manual.md

@@ -16,15 +16,15 @@ Your code, shell access, Codex auth, and runtime state stay on the host machine.
 
 ## 1. Full Setup
 
-### 1.1 Install Node.js 24
+### 1.1 Install Node.js 24+
 
-FoxClaw requires Node.js 24. Check first:
+FoxClaw requires Node.js 24+ and does not require nvm. Check first:
 
 ```bash
 node -v
 ```
 
-If this is not `v24...`, install Node 24 with `nvm`:
+If this is not `v24...` or newer, install Node 24+ with nvm, fnm, asdf, mise, Volta, Homebrew, or your system package manager. This is an nvm example:
 
 ```bash
 curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash
@@ -100,7 +100,7 @@ Both install the same published npm package. Use one global package manager cons
 
 ### 1.6 Fill In The Config
 
-`foxclaw init` creates the default config file at `~/.foxclaw/.env` and prompts for the Telegram bot token, your numeric Telegram user id, and the default workspace. Press Enter on any field to skip it, then edit manually if needed:
+`foxclaw init` creates the default config file at `~/.foxclaw/.env` and prompts for the Telegram bot token, your numeric Telegram user id, and the default workspace. If the current shell has proxy variables such as `HTTP_PROXY`, `HTTPS_PROXY`, or `ALL_PROXY`, it also asks whether to save them into the FoxClaw config so the service-side Codex app-server uses the same network. Press Enter on any field to skip it, then edit manually if needed:
 
 ```bash
 $EDITOR ~/.foxclaw/.env

package/docs/zh/agent-assisted-install.md

@@ -38,7 +38,7 @@ DEFAULT_CWD=<把绝对工作目录粘贴在这里>
 
 任务：
 1. 先检查机器环境。如果已经存在 FoxClaw 服务，先报告再改服务。
-2. 确保 Node.js 24+ 可用；如果没有，请用 nvm 安装或切到 Node 24。
+2. 确保 Node.js 24+ 可用；如果没有，请用任意合适方式安装或切到 Node 24+，nvm 只是常见选择。
 3. 确保 Codex CLI 存在并且已经登录。如果需要登录，停下来告诉我具体要执行什么。
 4. 用 npm install -g @foxden-app/foxclaw@latest 安装或升级 FoxClaw。
 5. 运行 foxclaw init，然后写入 ~/.foxclaw/.env。不要打印或提交 bot token。

package/docs/zh/foxclaw-skill.md

@@ -5,7 +5,7 @@
 ## 适合什么时候用
 
 - 你想让 Codex 通过 SSH 帮另一台 Mac 安装 FoxClaw。
-- 你希望 agent 先检查环境，再决定如何安装 Node.js 24、Codex CLI 和 FoxClaw。
+- 你希望 agent 先检查环境，再决定如何安装 Node.js 24+、Codex CLI 和 FoxClaw。
 - 你不想手动复制每一步安装命令，但愿意提供 Telegram bot token、用户 ID 和默认工作目录。
 
 ## 基本流程

package/docs/zh/install-for-beginners.md

@@ -23,17 +23,17 @@ FoxClaw 跑在你的电脑上。手机发消息给 Telegram bot，bot 把消息
 - 一个 Codex 可以工作的目录，例如 `~/Projects` 或 `~/Desktop`
 - 第一次安装大约 10-20 分钟
 
-## 2. 安装 Node.js 24
+## 2. 安装 Node.js 24+
 
-FoxClaw 需要 Node.js 24，因为它使用 Node 内置 SQLite 运行时。
+FoxClaw 需要 Node.js 24+，因为它使用 Node 内置 SQLite 运行时。不强依赖 nvm；你可以用 nvm、fnm、asdf、mise、Volta、Homebrew 或系统包管理器安装。
 
-如果已经安装 Node 24，这条命令会输出 `v24...`：
+如果已经安装 Node 24+，这条命令会输出 `v24...` 或更高版本：
 
 ```bash
 node -v
 ```
 
-如果不是 Node 24，推荐用 `nvm` 安装：
+如果不是 Node 24+，推荐普通用户用 `nvm` 安装，示例：
 
 ```bash
 curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash
@@ -45,7 +45,7 @@ node -v
 npm -v
 ```
 
-如果 `node -v` 仍然显示旧版本，关闭终端，重新打开后运行：
+如果使用 nvm 后 `node -v` 仍然显示旧版本，关闭终端，重新打开后运行：
 
 ```bash
 nvm use 24

package/docs/zh/troubleshooting.md

@@ -18,7 +18,7 @@ journalctl --user -u foxclaw.service -f
 
 | 现象 | 含义 | 处理方式 |
 | --- | --- | --- |
-| `[FAIL] node >= 24` | 当前 shell 使用的是旧版 Node.js。 | 运行 `nvm install 24 && nvm use 24`，再重新执行 `foxclaw doctor`。如果服务仍用旧 Node，从 Node 24 的 shell 里重新执行 `foxclaw start`。 |
+| `[FAIL] node >= 24` | 当前 shell 使用的是旧版 Node.js。 | 先用任意方式安装或切换到 Node.js 24+，再重新执行 `foxclaw doctor`。如果服务仍用旧 Node，从 Node 24+ 的 shell 里重新执行 `foxclaw start`。 |
 | `[FAIL] codex cli available` | `codex` 命令不在 PATH 里。 | 安装 Codex CLI 或修正 PATH，再确认 `codex --version` 可用。 |
 | `[FAIL] telegram bot token configured` | `.env` 里缺少 `TG_BOT_TOKEN`。 | 从 `@BotFather` 复制 token，填入 `.env`。 |
 | `[FAIL] telegram allowed user configured` | `.env` 里缺少 `TG_ALLOWED_USER_ID`。 | 从 `@userinfobot` 获取数字 ID，填入 `.env`。 |
@@ -26,7 +26,7 @@ journalctl --user -u foxclaw.service -f
 
 ## Node 或 npm 不存在
 
-如果看到 `node: command not found` 或 `npm: command not found`，用 `nvm` 安装 Node.js 24：
+如果看到 `node: command not found` 或 `npm: command not found`，先用你习惯的方式安装 Node.js 24+，例如 nvm、fnm、asdf、mise、Volta、Homebrew 或系统包管理器。下面是 nvm 示例：
 
 ```bash
 curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash
@@ -38,7 +38,7 @@ node -v
 npm -v
 ```
 
-如果仍然失败，关闭终端，重新打开后运行：
+如果使用 nvm 后仍然失败，关闭终端，重新打开后运行：
 
 ```bash
 nvm use 24
@@ -48,7 +48,7 @@ nvm use 24
 
 如果 `npm install -g @openai/codex` 或 `npm install -g @foxden-app/foxclaw` 报 `EACCES`、`EPERM`、`permission denied`，说明当前全局 npm 目录不可写。
 
-推荐处理方式是通过 `nvm` 使用用户级 Node，然后重新安装：
+推荐处理方式是使用一个用户级 Node.js 24+，然后重新安装。下面是 nvm 示例：
 
 ```bash
 nvm install 24
@@ -57,7 +57,7 @@ npm install -g @openai/codex
 npm install -g @foxden-app/foxclaw
 ```
 
-除非你很清楚本机 Node 的安装方式，否则不要直接混用 `sudo npm install -g ...`。`sudo`、系统 Node 和 `nvm` 混在一起，常见结果是 PATH 断掉或服务启动时找不到命令。
+除非你很清楚本机 Node 的安装方式，否则不要直接混用 `sudo npm install -g ...`。`sudo`、系统 Node 和用户级 Node 管理器混在一起，常见结果是 PATH 断掉或服务启动时找不到命令。
 
 如果 `codex` 已安装但 FoxClaw 找不到它，先定位二进制：
 
@@ -193,6 +193,8 @@ tail -f ~/.foxclaw/logs/service.log
 systemctl --user cat foxclaw.service
 ```
 
+`foxclaw init` 会检测当前 shell 里的代理环境变量，并询问是否保存到 FoxClaw `.env`。如果你跳过了这一步，`foxclaw doctor` 会在发现“shell 有代理，但 FoxClaw env 没有代理”时给出 `[WARN]`。
+
 确认 `Environment=FOXCLAW_ENV=...` 指向的文件里有你的代理配置，例如：
 
 ```dotenv
@@ -210,7 +212,9 @@ foxclaw restart
 
 ## 服务用了错误的 Node 版本
 
-systemd 安装脚本会记录当时 PATH 里的 `node`。如果你从 Node 22 或更旧版本的 shell 里安装过服务，请从 Node 24 的 shell 重新安装：
+systemd 安装脚本会记录当时正在运行的 Node 绝对路径，不依赖 systemd 去加载 `nvm.sh` 或其它 shell 初始化脚本。无论你用 nvm、fnm、asdf、mise、Volta、Homebrew 还是系统 Node，原则都是：从 Node 24+ 的 shell 里执行 `foxclaw start`，服务之后就固定使用这个 Node 24+ 路径。
+
+如果你从 Node 22 或更旧版本的 shell 里安装过服务，请从 Node 24+ 的 shell 重新安装。nvm 用户示例：
 
 ```bash
 nvm use 24
@@ -218,7 +222,7 @@ foxclaw start
 systemctl --user status foxclaw.service
 ```
 
-状态输出里应该能看到 Node 24 的路径。
+状态输出里应该能看到 Node 24+ 的路径。`foxclaw doctor` 也会检查已安装服务里的 Node 路径，如果发现路径不存在或版本低于 24，会提示重新运行 `foxclaw start`。
 
 ## 重启后是否会自动运行
 

package/docs/zh/user-manual.md

@@ -16,15 +16,15 @@ FoxClaw 把本机 Codex 包成一个可从手机控制的服务。Telegram 或
 
 ## 1. 完整安装流程
 
-### 1.1 安装 Node.js 24
+### 1.1 安装 Node.js 24+
 
-FoxClaw 需要 Node.js 24。先检查：
+FoxClaw 需要 Node.js 24+，不强依赖 nvm。先检查：
 
 ```bash
 node -v
 ```
 
-如果不是 `v24...`，推荐用 `nvm`：
+如果不是 `v24...` 或更高版本，可以用 nvm、fnm、asdf、mise、Volta、Homebrew 或系统包管理器安装 Node 24+。下面是 nvm 示例：
 
 ```bash
 curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash
@@ -100,7 +100,7 @@ foxclaw init
 
 ### 1.6 填写配置
 
-`foxclaw init` 会创建默认配置文件 `~/.foxclaw/.env`，并提示填写 Telegram bot token、Telegram 数字用户 ID 和默认工作目录。任何一项都可以直接回车跳过，之后再手动编辑：
+`foxclaw init` 会创建默认配置文件 `~/.foxclaw/.env`，并提示填写 Telegram bot token、Telegram 数字用户 ID 和默认工作目录。如果当前 shell 里有 `HTTP_PROXY`、`HTTPS_PROXY`、`ALL_PROXY` 等代理变量，它也会询问是否写入 FoxClaw 配置，让服务里的 Codex app-server 使用同样的网络。任何一项都可以直接回车跳过，之后再手动编辑：
 
 ```bash
 $EDITOR ~/.foxclaw/.env

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@foxden-app/foxclaw",
-  "version": "0.3.5",
+  "version": "0.3.7",
   "description": "Foxden local execution claw for controlling Codex from trusted chat interfaces.",
   "type": "module",
   "main": "dist/main.js",