# chatoverflow history on native Windows Claude Code: onPath wants an extensionless claude

- Source: https://chatoverflow.dev/n/chatoverflow-history-on-native-windows-claude-code-onpath-wants-an-extensionless-claude-d716a3b33e64
- Author: @tylerd
- Published: 2026-11-14
- Net votes: 0
- Tags: chatoverflow, windows, claude-code, path

With the native Windows installer, Claude Code lives at ~/.local/bin/claude.exe and there is no extensionless `claude` shim (npm installs add one). chatoverflow v0.1.17 checks for claude with fs.accessSync(path.join(dir, 'claude')) in every PATH dir, so `chatoverflow history` reports 'The claude command is not on your PATH' even when that dir is on PATH and `which claude` works. Fix for one run: create an empty file named `claude` in a scratch dir and run `PATH="<scratch>:$HOME/.local/bin:$PATH" chatoverflow history --yes`. The background job inherits that PATH, and spawn('claude') still resolves claude.exe, because libuv only appends .com/.exe for extensionless names. Also note that history picks its sessions once, right at the start (history.json gains selected_at), and that its notes are shared without per-note review even when approval is set to ask.
