AI Engineer Europe 2026

Claws Out: Securing and Building with OpenClaw

Loading slides…

Read the talk

Claws Out: Securing and Building with OpenClaw

Nick Taylor’s trusted-proxy contribution removes duplicated authentication work, then supports a live development loop from Discord to an MCP app inside ChatGPT.

From a talk by Nick Taylor

Before you start: Familiarity with reverse proxies, HTTP headers and basic React or TypeScript will help you follow the configuration and MCP app examples.

Why authenticate again behind a proxy?

Why should OpenClaw ask for another credential when an identity-aware proxy already controls access? Nick Taylor, a Montreal-based developer advocate at Pomerium, encountered exactly that friction. His February contribution addressed access to OpenClaw’s control plane: even after putting a proxy in front of it, he still had to supply a token for the WebSocket connection.

GitHub issue titled “Allow disabling auth with LAN binding for reverse proxy setups,” showing a summary and proposed solution beside the speaker.Open full source frame
A GitHub feature request proposes allowing proxy-managed authentication for LAN access.

The duplicated work extended to device pairing. An identity-aware proxy combines an identity provider, a policy engine and a reverse proxy—the pattern Taylor introduces through Google Cloud’s IAP. The identity provider establishes who is connecting; policy decides whether that identity may access the application; the proxy gates the connection. Pomerium is an open-core implementation of this approach, but OpenClaw still required its own setup after the proxy had admitted the user.

Taylor opened issue #1560, another user running Caddy supported the proposal, and maintainer Peter supplied the feature criteria. The existing flow required pasting an authentication token into the UI for the WebSocket connection. Taylor also reports that the UI put the token in a query string, a behavior he regarded as primarily appropriate for local use. Switching to his phone meant another pairing step, sometimes requiring him to return to another device to complete it.

The resulting trusted-proxy authentication contribution became his first merged OpenClaw contribution. Its central change was to let an explicitly trusted proxy supply the authentication boundary that the gateway had previously required users to satisfy separately.

0:150:31
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

0:15 · section reference included

Make the trust boundary explicit

The configuration separates which proxy is trusted from which headers carry identity. gateway.auth.mode selects trusted-proxy; gateway.trustedProxies contains one or more addresses for the proxy gating access to the gateway; and gateway.auth.trustedProxy contains the identity-header settings.

Within trustedProxy, userHeader identifies the header used as the user identity, requiredHeaders specifies headers that must be present, and optional allowUsers restricts accepted identities. Taylor describes a JWT-bearing header in his setup and leaves out allowUsers because Pomerium’s policies already determine who may enter. The distinction matters: trusting a header from an authorized proxy is not the same operation as independently validating a JWT signature.

A compact configuration using the email-identity and JWT-assertion separation shown in the current trusted-proxy guide looks like this; 192.0.2.10 stands for the deployment’s actual proxy address:

json

{
  "gateway": {
    "trustedProxies": ["192.0.2.10"],
    "auth": {
      "mode": "trusted-proxy",
      "trustedProxy": {
        "userHeader": "x-pomerium-claim-email",
        "requiredHeaders": ["x-pomerium-jwt-assertion"]
      }
    }
  }
}

The proxy must control the forwarded identity headers, and clients must not be able to bypass it and impersonate that trusted source. Configuration is available through onboarding or the terminal UI.

For Taylor’s demonstrated version, the practical result was no separate WebSocket token and no repeated device pairing. He describes the security improvement as potential, while the reduction in setup friction is immediate. Current OpenClaw documentation adds an explicit browser-approval policy: one-time approval remains required unless deviceAutoApprove is enabled, and its default is false. The recording’s pairing behavior therefore should not be assumed for a current installation.

3:594:13
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

3:59 · section reference included

Test the device that has never connected

The first implementation missed a pairing-related bug because Taylor tested locally with a device that was already paired. Anthony reported the problem and Sid fixed it. That is a specific testing lesson for authentication changes: existing session state can hide a broken first-use path. A successful connection from a familiar browser does not exercise the same conditions as a new device arriving without prior approval.

The contribution also moved through a rapidly changing repository. Taylor started with issue #1560 and PR #1710, then went on vacation. He reports that repository numbering advanced from roughly 1,500 to almost 16,000 during his two-week absence. These are issue and pull-request identifiers, not counts of users. He says the original PR was closed as stale, and getting the eventual contribution merged required substantial rebasing.

5:275:51
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

5:27 · section reference included

McClaw, Discord and a workspace without SSH

Taylor’s own instance, McClaw, runs on his desk in Montreal. He primarily talks to it through Discord, with WhatsApp also configured. He previously used Telegram but moved away after his CEO raised concerns about its encryption. The precise distinction is that Telegram Cloud Chats use client-server encryption, while Secret Chats provide end-to-end encryption; ordinary Telegram conversations are not simply transmitted in plaintext. His choice of Discord is a workflow preference here, not evidence of stronger message confidentiality.

McClaw helped implement the trusted-proxy contribution itself. That exposed a separate permission problem: Taylor gave the agent full access through the GitHub CLI, and it published a pull request before he had finished reviewing the work. He returned the PR to draft. Securing access to an agent’s control plane does not determine what the agent may do with credentials once it is running.

After the authentication feature merged, building from his phone became enjoyable enough that Taylor created Clawspace through Discord. It lets him browse, read and edit OpenClaw workspace files without opening an SSH session. The value is personal and concrete: a small interface removes a recurring obstacle in his own workflow, without needing to become a tool everyone else adopts.

6:517:05
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

6:51 · section reference included

Put a live workspace inside ChatGPT

The live demonstration starts with a limited MCP app built from an existing template. The AI Engineer website exposes developer-facing entry points, including llms.txt and an MCP server. Taylor uses the conference as the subject for an app he can register in ChatGPT and then extend through OpenClaw.

The initial connection follows a short sequence:

  1. Create the application in ChatGPT and configure OAuth.
  2. Register the MCP server and complete the connection.
  3. Inspect the available tools: echo and searchSpeakers.
  4. Invoke the app with Echo hello.

The tool call returns an associated interface inside the conversation. MCP Apps provide this UI extension to MCP: the result can be an interactive widget rather than only text. The Echo widget displays hello, exposes action buttons and can be enlarged within ChatGPT.

An Echo widget in ChatGPT shows “hello” under Echoed Message, with Call Echo Tool, Update Context, Clear, Send to Chat, and Open Docs buttons. Discord is open alongside it.Open full source frame
ChatGPT displays the embedded Echo interface with the echoed message “hello” and action buttons.

Taylor then asks McClaw to change the echoed message to AIE EU in the Echo widget. Underneath the chat interface, this is a web development loop: React renders the widget, Vite serves the application, and React Refresh with Vite hot module reloading carries workspace edits into the running interface. McClaw changes the MCP app’s files while Taylor remains in ChatGPT.

Two access boundaries make that arrangement work. Trusted-proxy authentication governs access to OpenClaw’s gateway. Separately, Pomerium gates a public URL for the MCP service in the workspace, allowing ChatGPT to reach it through controlled access. Protecting the gateway alone does not automatically protect every service the agent starts; the MCP endpoint needs its own gate. Taylor can then keep developing against the same interface he is using to exercise the app.

8:438:52
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

8:43 · section reference included

Expose the service, preserve the boundary

Pomerium is Taylor’s choice for this setup, but he also points to Caddy with OAuth as an alternative. The architectural requirement in his workflow is to make a local service reachable by an external host while retaining an access gate. He briefly mentions NGINX, then narrows his deprecation remark to a Kubernetes ingress controller. The relevant retirement announcement concerns the community Ingress NGINX controller, whose maintenance was scheduled to end in March 2026—not NGINX generally.

That infrastructure changes where development can happen. Taylor recalls seeing Replit’s phone-based building experience and wondering why he would ever want to program that way. Now he routinely enjoys building through chat on his phone. Clawspace is his example of the payoff: make a tool that fits the way you actually work, even if its audience is only you.

The freedom still depends on limits. Taylor closes by warning about accidental public exposure and destructive agent actions, including reports of deleted email. Trusted-proxy authentication is useful to him because it makes controlled access less cumbersome; it does not replace careful decisions about which services are exposed or which credentials an agent receives. The invitation is to build personal tools and enjoy the process while keeping those boundaries deliberate.

15:1515:27
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

15:15 · section reference included

Resources

From the talk

Updates since the talk

Transcript download
Full transcript

Loading transcript…