Remote sessions
Connecting
Two things must already be in place: the target machine has control permission enabled, and you hold a device grant that is in effect.
Pick the machine from the device cards on the client's home screen. Cards lay out in 2 or 3 columns depending on window width and carry a platform icon (macOS / Windows / Linux / Android / iOS).
Connecting does not ask for the account code again — that was verified when the grant was approved.
If it will not connect, start with troubleshooting.
LAN direct connect
Besides picking a device, the connect box on the home screen also accepts a 32-character hexadecimal host ID, or an IPv4 address in IP:port form.
Multi-session tabs
The client holds up to 8 concurrent remote sessions side by side as tabs.
| Action | How |
|---|---|
| Switch tab | Ctrl / Cmd + 1 – 8 |
| Close tab | The close button on the tab |
| Reorder | Drag the tab |
There is no Ctrl/Cmd+W
The close shortcut was removed on purpose — it gets sent to the remote machine, and the result is that you close the other side's window. Use the close button on the tab.
Other behaviour:
- connecting to a machine that already has a tab open switches to that tab instead of opening a second one;
- at the 8-session limit you get an explicit message rather than a silent failure;
- background tabs do not pull video frames, and they pause stats and clipboard sync, so leaving one open costs you no bandwidth;
- keyboard focus follows the active tab;
- going back to the home screen does not disconnect — only closing the tab or disconnecting explicitly does. The home screen shows the current session count.
How many you can run at once is also bounded by your plan's concurrency ceiling; if you exceed it see quota exceeded.
TIP
A background tab still occupies a concurrency slot. When you are done with a machine, close its tab.
Quality and performance
The remote picture runs over a video path tuned for low latency — under normal network conditions, latency is usually well under 100 ms.
Settings expose encoding options including codec preference (H.264 / VP9 / VP8 / AV1) and a resolution ceiling (the encoder scales by long edge). For the exact set of options, the app itself is authoritative.
What affects the experience:
- Network — upstream bandwidth and jitter matter more than raw bandwidth. A phone hotspot is usually fine, but quality drops when jitter is high.
- Resolution — the bigger the host's screen, the more pixels to encode and ship. A 4K display is much harder work than 1080p.
- Content — a static code editor is easy; full-screen video or fast scrolling costs noticeably more bandwidth.
Audio, clipboard and files
The client supports audio (Opus), clipboard sync and file transfer. The interface is available in Simplified Chinese, English and Traditional Chinese.
Input
Once connected, your keyboard and mouse are injected into the host machine.
- A macOS host needs the Accessibility permission to accept input — with only Screen Recording granted you see the picture but nothing responds. See troubleshooting.
- A Windows host needs an interactive logged-in session.
- When connecting across platforms (Windows controlling macOS, say), the app itself is authoritative for how some modifier keys and shortcuts behave.
Ending a session
Closing the session tab ends it. Ending a session does not affect the grant — the grant stays valid until it expires or is revoked.
Next
- Troubleshooting — black screen, cannot connect, input does nothing
- Security model — where session data goes