Use remote access from the browser or mobile

Host requirements

Remote access depends on a registered desktop host. The desktop keeps the real workspace, files, local tools, runtimes, and active WebUI session.

Before opening a remote session, confirm:

• the desktop is signed in
• the device is registered to the current account
• remote access is enabled or provisioned
• the host has an active network connection

Connection model

The remote client does not run a separate hosted copy of ContextGo. It connects through the account and relay layer back to the desktop host.

If the host loses connectivity or exits the session, the remote client cannot continue the task independently.

Mobile behavior

The mobile app or mobile browser session is a control surface for the host. Uploads, file access, runtime execution, and connector access still resolve on the desktop side.

If remote access is unavailable

Check the following in order:

1. Confirm the correct account is signed in.
2. Confirm the desktop device is shown in the device list.
3. Confirm the host is online and has not lost its outbound connection.
4. Confirm local security or network policy is not blocking the device-side connection.