Open your claw from your other browsers and invite people into it, through an encrypted relay, without opening a port.
Read when: You want remote access with members, roles and devices, without a VPN or a shared password.
Labs · experimentalConfig: gateway.openclawIdNo production service addresses yet
OpenClaw ID is an experimental Labs feature. A helper process next to the Gateway, the tunnel child, keeps an outbound encrypted iroh (QUIC) connection to a relay. Your other browsers, the people you invite and your nodes reach the claw through that relay, at an address like https://<name>-<tag>.<loaderDomain>. Your OpenClaw ID account only proves who you are. Who gets in is decided by an owner key from your recovery kit and by a membership list that the Gateway itself keeps and signs.
Reach your claw from any browserThe claw gets its own address behind the relay, so you open it from a phone or another computer with no port forwarding, VPN or shared password.
Invite people with a roleAn invite link makes someone an Operator (chat, run tools, use connected services) or a Viewer (read conversations), so a team shares one claw safely.
Add computers as nodesA headless computer joins after you compare a 6-digit code, so its commands become available to your agents.
Stay in control with a kitThe recovery kit you save at setup holds the owner key, so you can move the claw to new keys after a computer changes.
How it works
The parts
Part
Runs on
What it does
OpenClaw ID service in the Gateway
Your Gateway
The authority. Keeps the owner key it pinned, owner devices, members, invites and nodes. Signs each change with the Gateway key and publishes it to Discovery.
Tunnel child
Your Gateway's computer
A separate Node process that owns the endpoint key, dials the relay, admits only keys on the membership list, and hands each stream to the Gateway over a private Unix socket.
iroh native binding
Your Gateway's computer
@openclaw/iroh-node, built with pnpm build:iroh. Not published, not in the npm package.
OpenClaw ID issuer
Hosted
An OpenID Connect sign-in. Only proves which account you hold; it never decides membership.
Discovery
Hosted
A mirror of the claw's signed snapshot, a mailbox for invites and approvals, link codes and claw names. It cannot forge a change.
iroh relay
Hosted
The only relay the tunnel uses. It asks Discovery which keys it may admit.
Loader
Hosted
Serves the Control UI at the claw's address and runs the Add a claw page at claws.<domain>/link.
Remote access page
Your Gateway (plugin openclaw-id-access)
People and Nodes: invite, approve, remove.
openclaw id
Your Gateway's computer
status, rebind, publish.
From src/gateway/openclaw-id/, extensions/openclaw-id-access/, packages/openclaw-id-protocol/docs/, crates/openclaw-iroh-node/README.md.
Keys
Key
Where it lives
What it does
Recovery kit (OCK1-…)
Only in the kit you save
Holds the secret the owner key is made from. Made in your browser, never sent to the Gateway.
Owner root
Nowhere at rest
Derived from the kit when needed. Signs the claw's binding.
Owner device key
Each owner browser
A non-extractable browser key. Up to 20 owner devices.
Endpoint key
<state dir>/openclaw-id/endpoint.key
The tunnel's identity on the relay. File mode 0600.
Gateway key
<state dir>/openclaw-id/gateway.key
Signs membership snapshots and Discovery requests.
Node key
The node: $OPENCLAW_STATE_DIR/node-openclaw-id/endpoint.key
The node's identity on the relay.
Words you will see
Word
Meaning
Claw
Your Gateway once it is linked: a fixed ID and an address <name>-<tag>.<loaderDomain>. Names are 1 to 57 characters; addresses are never reused.
Owner
A browser holding an owner device key that is on the claw's list. Can approve devices, invite and manage members.
Member
An OpenClaw ID account you invited, with a role.
Role
Operator: chat, run tools, use connected services, answer approvals. Viewer: read conversations only.
Device
One browser at the claw's address. A member can have up to 10.
Binding number
The version of the claw's signed binding. Browsers refuse an older one.
Signing in
On the Gateway's own computer: a popup to the issuer. The Gateway redeems the code and records who you are.
Through a personal sign-in (Tailscale Serve, a trusted proxy): a code you confirm in OpenClaw ID.
Not possible over a shared token or password connection, or through the tunnel.
Signing in grants nothing by itself.
What you need
What
Why
Addresses for the issuer, Discovery, relay and loader, plus a client ID
The hosted half of OpenClaw ID. Upstream has no production defaults yet; until relayUrl is set the status is unconfigured.
The iroh native binding
pnpm build:iroh in a source checkout. Needs rustup, a C toolchain and Rust 1.99.0. Restart the Gateway afterwards.
A browser on the Gateway's own computer
Turn on remote access refuses any other browser.
Outbound HTTPS
To the relay, Discovery and the issuer. No inbound port.
A kept state directory
The two key files and the state database must survive restarts.
Turn it on
Gateway computer, terminalBuild the native binding, then restart the Gateway:
pnpm build:iroh
Control UIOpen Settings → Labs and switch on OpenClaw ID remote access. Or set it in config:
The example addresses are upstream's placeholders. Changes apply without a restart.
Account menuClick your avatar at the bottom left, then Sign in with OpenClaw ID. Sign in in the popup. A message appears: "Signed in as {account}. Reach this claw from anywhere?"
Account menuClick Turn on remote access. With your account signed in, the link code fills itself; otherwise click Get a link code, which opens claws.<domain>/link.
DialogPick a Claw name (the default is claw). The dialog shows "Available: https://claw-xxxxx.<domain>". Click Continue.
DialogSave your recovery kit: Download as text file or Print or save as PDF. Tick I've saved my recovery kit somewhere safe and click Continue.
There is no owner reset in this version. Without the kit you cannot move the claw to new keys.
DialogFour steps run: "Securing {name}", "Setting up your access", "Setting up {host}", "Connecting {name}". The last screen says "Your claw address is https://{host}." Click Copy claw link.
Pages → Remote accessTo invite someone: Invite someone, enter their email, choose Operator or Viewer, click Create invite link and send it privately. When they open it, approve them under Waiting for you.
Pages → Remote access → NodesTo add a computer: Add node, give it a label, Create node command, run the command on that computer, compare the 6 digits, click Codes match — approve node.
Check it works
Where
What you see
openclaw id status
Remote access: on, the claw's address, and Binding: N (Discovery has N).
openclaw id status --json
tunnel.state: "running", relayOnline: true.
Account menu
"Remote access on" with an Online pill and the claw's address.
Gateway log
openclaw-id: tunnel ready, then tunnel: relay online.
Another browser
The claw's address loads the Control UI.
Settings → Devices
Browsers that came through the tunnel are marked (OpenClaw ID).
Limits
Limit
Value
Owner devices
20
Members
256, each with up to 10 browsers
Nodes
256
Open invites (people and nodes together)
100
Member invite link
Expires in 7 days
Node invite
10 minutes by default, at most 1 hour
Link code
10 minutes
Inactive devices removed after
Owners 90 days, members 30 days, nodes 30 days
Nodes that join by invitation
Cannot host sessions: --session-host is refused for these invitations
Protocol
v1-draft, not a stable contract
If something goes wrong
You see
What it means
What to do
"The OpenClaw ID transport is not available in this build."
The native binding is missing.
Run pnpm build:iroh and restart. The Gateway retries every 60 seconds.
"To turn on remote access, open OpenClaw on the computer that runs this claw."
Your browser is not on the Gateway's own computer.
Open the Control UI there, at the loopback address.
"Remote access is not ready yet. Try again shortly."
The tunnel has not started.
Wait, then check openclaw id status.
"Remote access is off: a key file is missing"
The key files are gone from the state directory.
openclaw id rebind with your recovery kit and a new link code.
"…doesn't match"
A key file was replaced.
Same: openclaw id rebind.
Status unconfigured
relayUrl is not set.
Add the service addresses.
On Urbicana today
Step
Today
Why
Fix and cost
Service addresses
Missing
No production defaults upstream (experimental-features.md:377).
Wait for upstream.
Native binding
Missing
The image copies no crates/ (Dockerfile).
Rust build stage for linux-x64-gnu. About 10 MB.
Labs switch
Reverts
Each boot replaces the gateway block (entrypoint.sh:105).
Seed gateway.openclawId in agent-proxy/src/proxy.ts. Small.
Turn on remote access
Disabled
The door adds forwarding headers, so the browser never counts as local (channel.ts:14-20).
Not decided.
No inbound port
Fits
The tunnel dials out; the Gateway can stay on loopback.
None.
Keys kept
Fits
State lives on the /data volume (entrypoint.sh:4,15).
None.
Videos to record
These need the service addresses, so none can be recorded yet. The steps are ready for when they can.
15 · Switch on OpenClaw ID
Gateway computer, its own browser
Settings → Labs → switch on OpenClaw ID remote access.
Click your avatar. The menu shows Sign in with OpenClaw ID.
Sign in in the popup.
"Signed in as {account}. Reach this claw from anywhere?" with Turn on remote access.
16 · Turn on remote access
Gateway computer, its own browser
Account menu → Turn on remote access. The link code is filled in.
Type a claw name. "Available: https://…".Continue.
Download the recovery kit, tick the box, Continue.
The four setup steps, then "Your claw address is https://{host}."
Copy claw link and open it on a phone. The Control UI loads.
17 · Invite a person
Any owner browser
Pages → Remote access → Invite someone.
Email, Viewer, Create invite link, Copy link.
The invitee opens the link and signs in.
The request appears under Waiting for you.Approve.
The person is listed under Members. Show Remove and its warning.