Reachable from anywhere
Reachable from anywhere
Four OpenClaw features that let people, apps and other computers reach your Gateway without opening a port.
Read when: You want to open your agent from other devices, let people or apps in, or let it work on your laptop.
A Gateway used to be a program you opened on the computer it runs on, or through a door you built in front of it. These four features make it a service that your other browsers, invited people, AI apps and your laptop can reach. Each one connects outward from the Gateway, or has the remote computer connect in, so no Gateway port faces the internet.
The four at a glance
| Feature | Who connects | Who dials whom | Upstream status | On Urbicana today |
|---|---|---|---|---|
| OpenClaw ID | Your other browsers, invited people, nodes | The Gateway's tunnel dials an iroh relay; clients reach it through the relay | Labs Protocol v1-draft. No production service addresses yet. | Blocked No services, no native binding in the image, setup needs the Gateway's own computer. |
| MCP Relay | ChatGPT, Claude, Codex | The Gateway dials mcp.openclaw.ai; the apps connect there | Released 2026.10.10. Bundled plugin, off by default. | Blocked The relay connects, but pairing is refused on a trusted-proxy Gateway. |
| Device folder | A paired laptop (a node) | The laptop dials the Gateway | Released 2026.10.10. | Blocked The Urbicana door refuses a laptop: it has no sign-in cookie. |
| Spawn on a device | Your agent, onto a paired laptop | The laptop dials the Gateway | Main only Landed 12 Nov, not in a release. | Blocked Same door as the device folder; members get the code with their next image. |
How they reach the Gateway
Solid accent arrows work today. The dashed arrow is the laptop's path, which the Urbicana door refuses. The two relays on the right are reached by the Gateway dialing out.
What stands in the way on Urbicana
Every row was read in the code. Each blocker names where it is and what would remove it. None of these fixes has been made.
| # | Blocker | Blocks | Where | Fix and cost |
|---|---|---|---|---|
| 1 | The door refuses every request without its signed browser cookie, so a laptop cannot reach the join address, the node socket or the worker routes. | Device folder, spawn | agent-proxy/src/proxy.ts:1152-1161 | Let /j/*, the node WebSocket, /__openclaw__/worker, /__openclaw__/worker-bundle/* and /__openclaw__/worker-transfer/* through without the cookie. The Gateway checks the join code and the device token itself. A small change in agent-proxy, and a security decision: these routes then face the internet. |
| 2 | OpenClaw's docs say a new node cannot authenticate to a trusted-proxy Gateway. The code accepts the join code's bootstrap token on the socket anyway. Nobody has tried it. | Device folder, spawn | docs/nodes/node-host.md:31, src/gateway/server/ws-connection/auth-context.ts:192-231 | After fix 1, join one laptop end to end. If it is refused, nodes need token auth, which the door's trusted-proxy mode excludes. Cost unknown until tried. |
| 3 | MCP Relay refuses owner grants on a trusted-proxy Gateway. Person grants need Cloudflare Access headers and gateway.roles, which the member setup has neither of. | MCP Relay | extensions/mcp-relay/src/service.ts:213-221, src/gateway/auth.ts:228-242 | Either a core change that accepts the door as a verified identity source (a security-owner decision in core, not a plugin), or members who come in through OpenClaw ID, whose grants skip this check (auth.ts:206-209). The second waits on blockers 4 to 7. |
| 4 | OpenClaw ID needs a hosted issuer, Discovery service, relay and loader. Upstream has not published production addresses. | OpenClaw ID | docs/concepts/experimental-features.md:377 | Wait for upstream's services. Their code is not in the repository. |
| 5 | The iroh native binding is not in the member image. Without it the tunnel reports "unavailable". | OpenClaw ID | Dockerfile (copies no crates/) | Add a Rust 1.99.0 build stage for linux-x64-gnu and copy the binding to /app/crates/openclaw-iroh-node/. About 10 MB and extra build minutes. |
| 6 | Every boot replaces the whole gateway config block with the seed's, so the Labs switch for OpenClaw ID turns itself off at the next start. | OpenClaw ID | agent-proxy/fly/entrypoint.sh:105 | Put gateway.openclawId in the seed (gatewayConfig in agent-proxy/src/proxy.ts). Small. |
| 7 | Turn on remote access and the popup sign-in work only for a browser on the Gateway's own computer. Everything through the door arrives with forwarding headers. | OpenClaw ID | src/gateway/openclaw-id/channel.ts:14-20 | Not decided. The openclaw id commands work inside the machine, but linking a claw needs the browser. |
entrypoint.sh:118-126); its relay socket needs no inbound port; OpenClaw ID's keys would persist on the /data volume.Videos to record
Because of the blockers above, record these on a Gateway you run yourself with OpenClaw's default token auth, plus a second computer for the laptop parts. Each feature page lists the steps for every video.
| # | Video | Page | Can be recorded now |
|---|---|---|---|
| 1 | Switch on MCP Relay | MCP Relay | Yes |
| 2 | Connect Claude with a code | MCP Relay | Yes with a Claude plan that allows custom connectors |
| 3 | Connect ChatGPT by signing in | MCP Relay | Yes |
| 4 | Talk to your agents from Claude | MCP Relay | Yes |
| 5 | Revoke an app | MCP Relay | Yes |
| 6 | Connect a laptop | Device folder | Yes with the Gateway on HTTPS |
| 7 | Work in a laptop folder | Device folder | Yes |
| 8 | Edits land on the laptop | Device folder | Yes |
| 9 | The laptop goes to sleep | Device folder | Yes |
| 10 | Limit the allowed folders | Device folder | Yes |
| 11 | Run the tests on my laptop | Spawn on a device | Yes on a build from main |
| 12 | Results come home | Spawn on a device | Yes on a build from main |
| 13 | The device goes offline mid-run | Spawn on a device | Yes on a build from main |
| 14 | Hosting switched off: error and fix | Spawn on a device | Yes on a build from main |
| 15 | Switch on OpenClaw ID and sign in | OpenClaw ID | No needs service addresses |
| 16 | Turn on remote access | OpenClaw ID | No |
| 17 | Invite a person | OpenClaw ID | No |
| 18 | Add a node by invitation | OpenClaw ID | No |
| 19 | Approve a second owner browser | OpenClaw ID | No |