Bug type

Behavior bug (incorrect output/state without crash)

Summary

Starting a node host always prints a debug console.log message ("node host PATH: ...") that should not be visible to end users.

Steps to reproduce

1. Install OpenClaw globally: npm install -g openclaw
2. Start a node host: openclaw node run --host 192.168.9.5 --port 18789
3. Observe unwanted output in terminal: "node host PATH: C:\Users<user>.local\bin;C:\Program Files\nodejs"

Expected behavior

No debug output should be printed on node start. The PATH information should either be removed entirely or gated behind a --verbose / debug log level flag.

Actual behavior

A debug line is printed to stdout on every node start:

node host PATH: C:\Users<user>.local\bin;C:\Program Files\nodejs

Source file: src/node-host/runner.ts — function runNodeHost()
https://github.com/openclaw/openclaw/blob/main/src/node-host/runner.ts

const pathEnv = ensureNodePathEnv();
// eslint-disable-next-line no-console
console.log(node host PATH: ${pathEnv}); // <-- this line
const client = new GatewayClient({

The eslint-disable comment confirms this was an intentional bypass of the no-console rule,
likely added during development/debugging and not removed before release.

Bundled dist output:
dist/node-cli-Byf3Em2G.js (line 2118)
dist/node-cli-E0JhUVjk.js (line 2117)

OpenClaw version

2026.3.13 (commit 61d171a)

Operating system

Windows 11 (Build 26200.8037)

Install method

npm global

Model

n/a (affects node host startup, independent of model)

Provider / routing chain

n/a (affects node host startup, independent of provider)

Config file / key location

src/node-host/runner.ts ; runNodeHost() ; line with console.log(node host PATH: ${pathEnv})

Additional provider/model setup details

No response

Logs, screenshots, and evidence

PS C:\> C:\Users\<user>\.openclaw\node.cmd

🦞 OpenClaw 2026.3.13 (61d171a) — Ah, the fruit tree company! 🍎

node host PATH: C:\Users\<user>\.local\bin;C:\Program Files\nodejs

Impact and severity

Affected: All users starting a node host on any OS
Severity: Low (cosmetic, no functional impact)
Frequency: 100% repro on every node start
Consequence: Unwanted debug output clutters terminal; may confuse users into thinking something is misconfigured

Additional information

Workaround: Manually comment out the console.log line in both dist files:
// console.log(node host PATH: ${pathEnv});

This workaround is overwritten on every openclaw update.