What happened?
On Windows, codemap watch start reports success and leaves a running codemap process with a matching .codemap/watch.pid, but codemap watch status immediately says Watch daemon not running.
Expected behavior
After watch start succeeds, watch status should report the daemon as running when the PID in .codemap/watch.pid is still alive.
Actual output
PS> Get-Process codemap | Stop-Process -Force
PS> codemap watch start
Watch daemon started (pid 12532)
PS> codemap watch status
Watch daemon not running
PS> Get-Process -Id 12532
NPM(K) PM(M) WS(M) CPU(s) Id SI ProcessName
------ ----- ----- ------ -- -- -----------
12 21.15 21.88 8.55 12532 1 codemap
PS> Get-Content .codemap\watch.pid
12532
**Environment
OS: Windows 11
Editor: Cursor 3.6.31
codemap version: 4.1.7
Install method: Scoop
What happened?
On Windows,
codemap watch startreports success and leaves a runningcodemapprocess with a matching.codemap/watch.pid, butcodemap watch statusimmediately saysWatch daemon not running.Expected behavior
After
watch startsucceeds,watch statusshould report the daemon as running when the PID in.codemap/watch.pidis still alive.Actual output
**Environment
OS: Windows 11
Editor: Cursor 3.6.31
codemap version: 4.1.7
Install method: Scoop