"Remain running after close" does not keep local server alive on Windows 11 (v0.3.0)

[MicMarvin]

Summary

On Windows 11, enabling the setting that says Voicebox should remain running after the application is closed does not appear to work. When the GUI is open, the local API/server works normally on http://127.0.0.1:17493/ and http://127.0.0.1:17493/docs. As soon as I close the GUI, the server stops listening and the browser returns ERR_CONNECTION_REFUSED.

Environment

• OS: Windows 11
• Voicebox version: v0.3.0
• Install method: Windows MSI from the official website / download page
• Hardware: NVIDIA RTX PRO 6000 Blackwell Max-Q Workstation Edition

Expected behavior

With the "remain running after close" setting enabled, closing the Voicebox GUI window should leave the local backend/server running so that the local API remains reachable on port 17493.

Actual behavior

When I close the GUI, the local server shuts down. Visiting the local URL after closing the app gives:

Hmmm… can't reach this page
127.0.0.1 refused to connect.
ERR_CONNECTION_REFUSED

Steps to reproduce

1. Install Voicebox v0.3.0 on Windows 11.
2. Enable the setting that says the app remains running after the application is closed.
3. Open Voicebox.
4. Visit http://127.0.0.1:17493/docs in a browser.
5. Confirm the Voicebox API docs load successfully.
6. While the app is open, check that port 17493 is listening:

netstat -ano | findstr :17493

7. Close the Voicebox GUI.
8. Revisit http://127.0.0.1:17493/docs or http://127.0.0.1:17493/.
9. Check the port again with:

netstat -ano | findstr :17493

Expected

Closing the GUI should leave the local backend/server running.

Actual

Closing the GUI stops the server. Port 17493 is no longer listening, and the local URL returns ERR_CONNECTION_REFUSED.

Relevant log lines

Arguments: [... '--port', '17493', '--parent-pid', '3032', '--host', '0.0.0.0'] Parent watchdog started, monitoring PID 3032 Uvicorn running on http://0.0.0.0:17493

This makes it look like the backend is still tied to the GUI process on Windows, despite the setting implying it should remain running after close.

Can you confirm whether this is a known issue in v0.3.0?