Support
Start with connection state.
SystemLens fails explicitly. Offline, unsupported, denied, and unavailable are different states—and missing evidence is never presented as healthy.
PC offline
Open the companion, check its status, then reconnect. Confirm that outbound HTTPS and WebSocket access are available.
Pairing failed
Create a new code. Pairing redemption is rate-limited; codes expire after 10 minutes and can be redeemed only once.
Evidence unavailable
Keep the explicit unsupported, unavailable-without-elevation, access-denied, timeout, or failed result. Do not treat missing evidence as healthy.
What to include in a support request
Include the companion version, approximate time, collector name, and stable error code. Never send a device credential, bearer token, pairing code, raw Event Log dump, or private document.
Open-source support
Use the public GitHub repository for non-sensitive source, build, fixture, and documentation issues. Never post credentials or private telemetry. Use GitHub’s private vulnerability-reporting flow for security reports; no placeholder inbox is presented as active.