How tunnels work
The CLI starts an outbound tunnel attachment. Incoming requests to its assigned public address are forwarded back to the local target while that attachment is connected.
Tunnel guide
A public route to your running local service.
Use the tunnel-only path when the process is already running and you do not need the full imported-project workflow.
Basic usage
Forward traffic from a public URL to one or more local ports:
# One service
r3v tunnel http://localhost:3000
# Several at once
r3v tunnel http://localhost:3000 http://localhost:3033
# Under names you choose
r3v tunnel http://localhost:3000=api http://localhost:3033=webLegacy cluster-agent path
A separate legacy cluster-agent package exists for operator-managed Kubernetes connections. It is not required for the local quickstart and should be evaluated against the target release before use.
R3V_CLUSTER_AGENT_KEY
R3V_CLUSTER_AGENT_ORG_ID
R3V_CLUSTER_AGENT_CLUSTER_ID
R3V_CLUSTER_AGENT_ORG_ID
R3V_CLUSTER_AGENT_CLUSTER_ID
This bootstrap path describes one explicitly configured organization and cluster. It is not a general multi-cluster or governance guarantee.