Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cyberdesk.io/llms.txt

Use this file to discover all available pages before exploring further.

Diagnostics are critical during beta. Cyberdriver exposes local and remote diagnostics so support can understand what failed without guessing.

​
From the Cyberdriver app

Open Settings → Network and click Copy diagnostics. This copies a JSON payload with local configuration, service status, server targets, permissions, API key configured state, and other useful state.

​
From the dashboard

Cyberdesk can call: 
GET /internal/diagnostics
through the machine tunnel. The response includes:
  • Cyberdriver version
  • platform and hostname
  • Cyberdesk machine fingerprint
  • RustDesk peer ID
  • API/hbbs/hbbr server configuration
  • Cyberdesk tunnel API base
  • keepalive state and last activity time
  • display dimensions
  • log directory and latest log tail
  • virtual display platform additions on Windows

​
From the CLI

cyberdriver logs
Useful options: 
cyberdriver logs --tail 200000
cyberdriver logs --follow
cyberdriver logs --path "C:\path\to\file.log"

​
What to send support

When reporting a bug, include:
  1. The diagnostics JSON
  2. The latest log tail
  3. Your OS version
  4. Whether Cyberdriver is installed as a Windows service
  5. The exact action that failed, such as screenshot, click, type, connect, or API key save