Use client.terminate() instead of client.close() to avoid waiting for unresponsive clients to acknowledge the WebSocket close handshake. Add a 2-second safety timeout that closes the HTTP listener, destroys lingering sockets, and resolves the promise so session_shutdown does not block pi from exiting. |
||
|---|---|---|
| extensions/pi-remote-control | ||
| .gitignore | ||
| LICENSE | ||
| README.md | ||
| package-lock.json | ||
| package.json | ||
README.md
pi-remote-control
Install
pi install https://github.com/goofansu/pi-remote-control
Usage
Run /remote-control to open the menu:
- Turn on / Turn off — start or stop the server
- Configure URL — set the public base URL your proxy/tunnel exposes (saved to
~/.pi/agent/remote-control.json) - Status — show the QR code and connection URL (only when server is running)
On first use, you'll be prompted to configure the URL before the server starts.