Choose a route
A connection requires correct target identity, a reachable route and valid client authorization. Configuring a route addresses reachability, not all three requirements.
Endpoint versus route
An endpoint identifies a device; a route is one way to reach it. Multiple routes can belong to one endpoint, but switching routes must not bypass identity checks.
| Route | Use case | Requirements |
|---|---|---|
| Local | Same-computer use | Local daemon and user access |
| SSH | Existing trusted SSH infrastructure | SSH authentication, host pin and AnyTTY grant |
| Direct | LAN or explicitly reachable address | Listener, ports and reachable pairing route |
| Cloud | Cross-network discovery and relay | Enrollment, pairing and available service paths |
Choose a starting point
Use anytty and local for desktop-only work. Use Direct for a reachable LAN, SSH for existing administrative access, or Cloud-assisted P2P/Relay across networks.
Cloud is not required for Local, SSH or Direct, and enrolling does not automatically grant an App terminal access.
Configure in order
- Verify the target daemon and a local terminal.
- Prepare one reachable route.
- Issue and redeem a client invitation.
- Test that route and open an existing task.
- Add backup routes and automatic selection afterward.