Your computer, within reach
AvailableOpen your local tools from another device.
A personal tunnel gives a tool on your computer its own Radient address. You sign in as the owning account, approve that address, and reach the running tool through the connector.
Used with Local Operator
Local Operator supplies the lop connector and the phone-accessible agent surface. Create the tunnel in the console, connect it with lop, and keep the computer and connector online while you work.
Availability
Available
Console setup and published guide
Access
Owning account
Sign-in and per-address approval
Requirement
Computer online
The connector must also be running
Billing
Separate subscription
Current monthly quote shown in console
One request, four explicit hops
The trace makes the security and availability assumptions visible: a browser grant belongs to an address, the edge checks it, and the local gateway can answer only while your computer is connected.
Request trace / owning-account access
01 / DEVICE
Connector online
The computer runs Local Operator or OpenCode and the Radient connector.
02 / GRANT
Owner approves
The visitor signs in as the owning account and approves the named personal address.
03 / EDGE
Address checked
The request is checked against the grant for that address, not accepted as a public link.
04 / GATEWAY
Tool connected
The gateway reaches the connector and the enabled local tool; the computer must remain reachable.
Computer / connector
lop login radient
lop tunnel connect <id>
lop tunnel statusWhat the trace does not mean
This is not end-to-end encryption, offline access or a private network. It is authenticated remote access to an online computer, with a separately priced monthly subscription quoted in the console.
Mechanism
How it works
- 01
Create the named tunnel
Choose Local Operator, OpenCode or both in the console and configure each local port. Each enabled tool receives its own address.
- 02
Connect the owning computer
Authenticate with lop login radient, then run the console’s connect command for the tunnel id and check lop tunnel status.
- 03
Approve the browser address
On your phone or other computer, sign in as the account that owns the tunnel and approve the named address before opening the tool.
- 04
Keep the path online
Requests cross the Radient edge and the connector to your local tool. The computer, tool and connector must remain running and connected.
Concrete use case
Check a long-running local agent from your phone
You leave Local Operator running on a workstation while it processes a repository task. Away from your desk, you open that workstation’s tunnel address, sign in as the owning account, approve the address, and inspect the same local session without copying a portal password into a chat.
The agent and files stay on the workstation. Remote access still depends on that workstation, its connector and the tool staying online.
Before you rely on it
Requirements, limits, security and cost
Requirements
- A Radient account with a positive balance for setup
- The current tunnel subscription accepted in the console
- The host computer, local tool and connector online
Limits
- Remote access pauses when the connector or computer is unavailable
- Changing tool configuration can invalidate existing browser grants
- This is remote access to a running tool, not an offline replica
Security
- Sign in as the owning account and approve each named address
- A grant is scoped to the tunnel address it was made for
- Not end-to-end encrypted and not a private-network or offline-access promise
Cost
- A separate monthly subscription; the console quotes the current amount
- One subscription covers all personal tunnels on the account
- Model and tool usage continues to use Radient credits
Feature questions