The Auth Friction OpenClaw Left Unresolved
OpenClaw’s default auth model treats your proxy as untrusted. Even when Pomerium or another identity-aware proxy was already blocking the door, you still had to paste an auth token into the UI for the WebSocket connection. That token lands in the query string. Device pairing was required on every new client, too. Taylor found both steps unnecessary once a trusted proxy was in place, and opened GitHub issue 1560 to propose removing them. Peter Stipe agreed and laid out the acceptance criteria.
How Trusted Proxy Auth Mode Works
The new config has three changes. The mode field becomes trusted_proxy. A trusted_proxies list holds the IP addresses of proxies allowed to assert identity. A trusted_proxy block then specifies a user_header (Taylor uses a JWT) and optional fields like required_header and allowed_users. Because Pomerium’s policy engine controls who gets through, Taylor omits allowed_users entirely. No token prompt in the UI, no device pairing required. Access control sits one layer upstream, enforced before the request ever reaches OpenClaw’s gateway.
Open Source Velocity and the Rebase Tax
After the merge, Anthony reported a bug. Sid fixed it. Taylor had tested only on his local environment where a device was already paired, so he never hit the edge case. The community stepped in.
The PR itself tells a separate story. Taylor opened issue 1560, drafted a PR in the 1700s, then went on vacation. Two weeks later the issue count had jumped from roughly 1,500 to nearly 16,000. He had to rebase before the feature could land.
“OSS for the win.” — Nick Taylor
Building an MCP Server Live via Pomerium Proxy
Taylor registers a small MCP server in ChatGPT during the live MCP build in ChatGPT via OpenClaw (08:45). The server starts with two tools: echo and search-speakers. From Discord, he types instructions to OpenClaw, which edits the React/Vite source files live. Hot module reloading surfaces the changes in ChatGPT immediately. Pomerium gates the public URL that ChatGPT calls, so no token is needed. He then adds a “more” button that sends a follow-up prompt to the LLM and streams a response back.
Notable Quotes
OSS for the win. Nick Taylor · ▶ 6:04
it’s the age of personal software. Nick Taylor · ▶ 8:17
you can still expose it in a secure way. Nick Taylor · ▶ 15:41
Key Takeaways
- Trusted proxy auth mode removes manual token entry and device pairing for OpenClaw behind an identity-aware proxy.
- Pomerium’s policy engine handles access control, so OpenClaw’s allowed-users list is unnecessary in that setup.
- An MCP server with embedded UI can be registered in ChatGPT and edited live from a mobile client without direct SSH access.