Remote Access

Remote access lets a gateway publish an endpoint through the configured Pioneer relay. A desktop or mobile client can then connect to that gateway remotely. The gateway owns the tunnel. The desktop app edits gateway settings and displays status; tool calls, MCP servers, local files, tasks, provider requests, and artifacts remain on the gateway host.

​

What the desktop app controls

The desktop settings screen can: The relay server, local gateway address, service name, transport, and restart policy come from operator config under [gateway.remote_access].

​

Status values

Remote-access status is live runtime state from the gateway: Common error kinds include missing_key, missing_binary, local_gateway_unavailable, relay_resolve_failed, relay_connect_failed, tunnel_auth_failed, unsupported_transport, and restart_limit_reached.

​

Using the remote gateway

After remote access is connected, add the exposed gateway address to another client as a remote gateway. Create a one-time activation code on the gateway host with pioneer device create, then enter it in the client. Later requests use the client session created during activation. The mobile app does not start a gateway on the phone. It connects to a reachable gateway, so remote access is the normal path for using a personal workstation or server from mobile.

​

Configuration and protocol

• Configuration Reference lists [gateway.remote_access] operator defaults.
• Settings API documents remote_access snapshots, updates, key handling, and status notifications.
• Remote Access Architecture explains the pioneer-tunnel supervisor, rathole status projection, and secret handling.
• Gateway Architecture explains where remote access fits in gateway startup and shutdown.