Remote Desktop

Control your IDE from anywhere via P2P-connected remote desktop.

Overview

Remote Desktop streams your IDE's screen to the dashboard and forwards mouse/keyboard input back. All data travels over a direct P2P WebRTC DataChannel — the server never sees or stores your screen data.

How It Works

1. Screenshot Capture — The daemon captures your IDE screen in real-time
2. Smart Detection — Only changed frames are sent (unchanged screens are skipped)
3. P2P Transfer — Screenshot data is sent directly to your browser via WebRTC
4. Input Forwarding — Your clicks and keystrokes are sent back via the same channel

Adaptive Frame Rate

The screenshot loop automatically adjusts speed:

• Screen changing → speeds up for smooth viewing
• Screen static → slows down to save bandwidth
• TURN relay → automatically reduces quality to 12 (vs 25 for direct) to reduce data usage

Daily Budget

Remote Desktop usage is tracked by active viewing time, not frame count:

• Budget resets at midnight UTC
• Closing Remote View pauses budget consumption
• Budget exhausted → screenshots pause until next day

See Plan Limits for per-plan budget details.

Security

• All data is encrypted via DTLS (WebRTC's built-in encryption)
• No screenshots are stored on the server
• P2P means data goes directly between your devices
• TURN relay (when used) is encrypted end-to-end

For usage instructions, see the Remote View Guide.