Personal Tunnels: Your Tools, Within Reach

A personal tunnel gives the tools running on your computer a private address under radienthq.com. Open that address from your phone or another device, sign in with your Radient account, and approve access, then use the tool as if you were sitting in front of it.

The address is yours alone: every request is checked against your Radient sign-in before it reaches your computer, and each tool gets its own address, so a link to one can never open the other.

#Create a tunnel in the console

1. Open the Tunnels page in the Radient console and choose Create tunnel.
2. Give the computer a name, then choose the tools to connect (Local Operator, OpenCode, or both) along with each tool's local port.
3. If another program already uses the connector's default port, open Advanced and change the connector port. It is fixed once the tunnel is created; to use a different connector port later, create a new tunnel.
4. Review the current monthly price (see Billing), then choose Create tunnel.
5. The Connect computer dialog shows the exact command to run on the computer that hosts your tools; copy it and run it there. It uses your Radient login to connect the tunnel.

#Manage a tunnel

Each tunnel card in the console shows the address for every enabled tool, plus the actions below.

• Connect computer: show the copy-and-run command again (lop tunnel connect <id>).
• Configure: change the computer's name, which tools are enabled, or a tool's local port. Saving invalidates existing browser grants, so a phone or browser that was already authorized may need to approve the address again. After changing a port, run the connect command again on the computer so the connector accepts it.
• Pause / Resume: pausing disconnects the connector and stops remote access; resuming brings it back. Your tools and any running sessions on the computer keep running either way.
• Remove: delete the tunnel. Its addresses stop working; the tools and sessions on your computer keep running, and you can create a new tunnel later.

The card's status tells you where the tunnel is: Ready for device means the addresses are configured and waiting; it does not report that the connector is online, so open a tool to check the connection. Paused means you paused it, Billing paused means remote access is suspended for billing, and Needs attention means setup hit a problem. Personal addresses stay the same when the computer reconnects.

#Billing

• The console shows the current monthly price when you create a tunnel, and a paid but inactive subscription asks you to accept that exact amount before it activates. If the price changes before you accept, review the new amount: the console will not charge a price you did not confirm.
• One subscription covers all the tunnels on your account. If your subscription is already active, a new tunnel adds no monthly charge.
• If your balance runs low, remote access pauses at a balance of −$1. Your configuration is saved: add credits, then choose Reactivate to restore access at the displayed rate.

#Open your tools from another device

1. Open a tool's personal address on your phone or another computer.
2. Sign in with the Radient account that owns the tunnel. The approval card names the tunnel and the address you are opening.
3. Check the access note and choose Open: you can view and control that tool's sessions, and the approval applies only to that address.

The computer and its connector must stay running and connected while you work. Opening a tool checks whether the computer is reachable.

#Connect Local Operator

Local Operator is the desktop app for running and steering agents on your computer. To connect this computer to its tunnel:

1. Sign in to Radient. In a terminal, run lop login radient and complete the browser sign-in. If you keep more than one Radient login, lop login-status lists the credential IDs you can pass to other commands as --credential-id.
2. Check the account. lop tunnel billing shows the account and the current monthly price. Setup needs a positive credit balance, so add credits in the console first if the balance is empty.
3. Connect the tunnel. For a tunnel created in the console, run lop tunnel connect <id> on the computer that will host the tools; add --no-start to save the configuration without starting the connector. To create the tunnel from the command line instead, run lop tunnel create, then lop tunnel install.
4. Check the status. lop tunnel status reports the connector and the address to open. When you are done, lop tunnel stop stops the connector on this computer.

#The phone portal

Local Operator's own phone portal is managed with lop mobile; confirm it is healthy with lop mobile status. Through a personal tunnel you reach it the same way as any other tool: open the tunnel address on the phone, sign in to Radient, and approve. No separate portal password needs to be copied for that route.

#Connect OpenCode

1. Start OpenCode's web server on the local port the tunnel expects: opencode web --port <port>. The tunnel does not start OpenCode for you.
2. Keep the port in sync. Change the OpenCode port in the console, or run lop tunnel configure --opencode-port <port> on the computer and restart the connector with lop tunnel restart.
3. If your OpenCode server requires Basic authentication, save its username and password in a private JSON file on the computer ({"username": "...", "password": "..."}, with 0600 permissions) and pass it with --opencode-auth-file <path> when you connect. Those credentials stay on your device and are never uploaded.

Local Operator and OpenCode share one connector, so a single lop tunnel connect serves both.

#See also

• Getting Started: the Radient basics.
• Radient Pass: how usage and credits work.
• Team plan: share agents and teams with your organization.