Bug type
Behavior bug (incorrect output/state without crash)
Beta release blocker
No
Summary
On Windows 11 Pro with OpenClaw 2026.5.7, openclaw node install creates an OpenClaw Node Scheduled Task that runs C:\Users\[Username]\.openclaw ode.cmd, and at Windows login that task opens a persistent visible openclaw-node cmd window in the taskbar instead of running invisibly in the background.
Steps to reproduce
- On Windows 11 with OpenClaw 2026.5.7, run PowerShell as Administrator.
- Run:
openclaw node uninstall
openclaw node install --host 192.168.0.96 --port 18789 --display-name PC --force
- Confirm install output says:
Installed Scheduled Task: OpenClaw Node
Task script: C:\Users\Admin\.openclaw
ode.cmd
- Restart/sign in to Windows.
- Observe a persistent visible cmd window titled
openclaw-node in the taskbar.
- Confirm the Startup-folder fallback is absent and the Scheduled Task is running:
openclaw node status --json
schtasks /Query /TN "OpenClaw Node" /FO LIST
Expected behavior
Per the openclaw node docs, openclaw node install installs the headless node host as a background user service, so after Windows login the OpenClaw Node Scheduled Task should be running without leaving a persistent visible openclaw-node cmd window in the taskbar. Ref: https://docs.openclaw.ai/cli/node
Actual behavior
Observed result: after openclaw node install --host 192.168.0.96 --port 18789 --display-name PC --force reported Installed Scheduled Task: OpenClaw Node and Task script: C:\Users\Admin\.openclaw ode.cmd, Windows login still opened a persistent visible cmd window titled openclaw-node in the taskbar; openclaw node status --json showed the node service runtime.status as running, and schtasks /Query /TN "OpenClaw Node" /FO LIST showed Status: Running, Logon Mode: Interactive only, and Task To Run: C:\Users\Admin\.openclaw ode.cmd.
OpenClaw version
2026.5.7
Operating system
Windows 11 Pro 10.0.26200 Build 26200
Install method
npm global
Model
N/A
Provider / routing chain
N/A
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response
Bug type
Behavior bug (incorrect output/state without crash)
Beta release blocker
No
Summary
On Windows 11 Pro with OpenClaw 2026.5.7,
openclaw node installcreates anOpenClaw NodeScheduled Task that runsC:\Users\[Username]\.openclaw ode.cmd, and at Windows login that task opens a persistent visibleopenclaw-nodecmd window in the taskbar instead of running invisibly in the background.Steps to reproduce
openclaw-nodein the taskbar.Expected behavior
Per the
openclaw nodedocs,openclaw node installinstalls the headless node host as a background user service, so after Windows login theOpenClaw NodeScheduled Task should be running without leaving a persistent visibleopenclaw-nodecmd window in the taskbar. Ref: https://docs.openclaw.ai/cli/nodeActual behavior
Observed result: after
openclaw node install --host 192.168.0.96 --port 18789 --display-name PC --forcereportedInstalled Scheduled Task: OpenClaw NodeandTask script: C:\Users\Admin\.openclaw ode.cmd, Windows login still opened a persistent visible cmd window titledopenclaw-nodein the taskbar;openclaw node status --jsonshowed the node serviceruntime.statusasrunning, andschtasks /Query /TN "OpenClaw Node" /FO LISTshowedStatus: Running,Logon Mode: Interactive only, andTask To Run: C:\Users\Admin\.openclaw ode.cmd.OpenClaw version
2026.5.7
Operating system
Windows 11 Pro 10.0.26200 Build 26200
Install method
npm global
Model
N/A
Provider / routing chain
N/A
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response