Use detached: true on Windows

[anaisbetts]

Unfortunately, the fix in #55 was not sufficient - the behavior of spawn depends on the "console'ness" of the originally launched process, which has the effect of development behavior for Claude Desktop on Windows being different than in production, since the launching process is Claude.exe (a Win32 Subsystem app) vs yarn start which is effectively a Console Subsystem app.

[jspahrsummers]

On Windows, setting options.detached to true makes it possible for the child process to continue running after the parent exits. The child process will have its own console window.

Both of these sound like the opposite of what we want, no? We definitely don't want servers to persist past the lifetime of their host application, and we're trying to eliminate its own console window.

[anaisbetts]

Both of these sound like the opposite of what we want, no? We definitely don't want servers to persist past the lifetime of their host application, and we're trying to eliminate its own console window.

It appears that this documentation doesn't line up with the actual behavior (I suspect this behavior is describing node.exe which is inherently a Console Subsystem app where Electron in production is not; Electron itself also patches spawn)

Without detached, conhost.exe is attached:

With detached:

And we can see in Process Explorer that when Claude.exe exits, the node.exe does too

[jspahrsummers]

Okay, I trust you!

Can you add a comment to the code to this effect?