Monitoring CaptureGem Recordings Locally

CaptureGem’s Record tab shows each model’s status, and its Monitor tab shows live previews of active recordings. The app has no web dashboard or remote-access feature. Its background recorder, recorderd, does answer a local HTTP API, documented in the standalone Linux guide: port 28471 by default, with routes such as /getInitialState, /getQueueState and /getBandwidth, plus a WebSocket bound to loopback. That API has no authentication.

A practical local monitoring routine

Keep CaptureGem open in its normal desktop session and review the Record and Monitor tabs. Click the small status dot in the top-right corner to open Queue Status, which lists conversions and unfinished recordings, and use Show System Monitor in Settings for the recorder’s health messages. Check the recording output folder and app logs when a stream behaves unexpectedly. Confirm success by opening a finished file, rather than treating a status indicator as proof of a playable recording.

For remote access to your computer, use a remote desktop solution you trust and keep CaptureGem’s local recorder interfaces private. If you build your own status page on the recorder’s API, run it on the same machine or reach the API through a VPN or an SSH local-forward. Never open the recorder’s HTTP or proxy ports (28471 and 28474 by default) to the internet, and don’t put a Discord webhook into a public page. The recorder accepts requests from any web page, so close a tunnel when you no longer need it. Automated fleet monitoring would require a separately designed and authenticated integration; the app does not provide one as a customer feature.