[Bug]: [Windows] BLE TCP Bridge Terminates When Vibecoding Keyboard is Closed

[laxer84]

What happened?

When I launch Vibecoding Keyboard, the BLE TCP Bridge is also launched automatically.

I noticed two issues:

Vibecoding Keyboard cannot be minimized to the system tray, so the application has to remain open even though I only need the BLE TCP Bridge.

What did you expect to happen?

Expected Behavior
It would be useful if the BLE TCP Bridge could run independently of Vibecoding Keyboard. This would allow users to:

Start the BLE TCP Bridge without requiring Vibecoding Keyboard to remain open.
Close Vibecoding Keyboard while keeping the BLE TCP Bridge running.
Run the BLE TCP Bridge as a standalone background application or service.

Is it possible to make the BLE TCP Bridge operate independently from Vibecoding Keyboard?

Steps to reproduce

.

Related area

BLE communication

Platform / OS

Windows 11

App / repo version

v0.1.1

Logs, screenshots, or extra context

No response

[ZephyrKeXiner]

Thank you for your feedback! We will check this bug as soon as possible!