OpenClaw x Beav3r

OpenClaw x Beav3r connects OpenClaw approval events to the Beav3r approval service.

The integration uses a local plugin and bridge to send requests into Beav3r, then returns the final decision back into the OpenClaw flow.

What this integration is for

Use this integration when:

OpenClaw is already part of your execution flow
you want a prebuilt connector instead of wiring the SDK path yourself
you want a fast path to a working approval loop

Packages

this integration is free to use
the plugin package is @openclaw/openclaw-approvals
the bridge package is @beav3r/openclaw-beav3r-bridge
the fastest setup path is Docker-based local setup

Minimal setup

The shortest path is:

create a Beav3r project
generate a Beav3r API key
bootstrap the OpenClaw plugin and bridge
pair a signer device
run a test approval through OpenClaw

From the integration workspace, the documented Docker-first path is:


npm run install:docker

The setup flow should:

ask for BEAV3R_URL
ask for BEAV3R_API_KEY
generate local secrets and env values
start the plugin and bridge containers

Advanced setup

Use the advanced path when you want more control over the runtime shape.

Typical reasons:

you want to run the bridge outside Docker
you want to point at a self-hosted Beav3r server
you want to manage plugin and bridge processes separately

Local dev shape:

the plugin runs as the OpenClaw-facing adapter
the bridge runs as the Beav3r-facing relay
the bridge points at your hosted or self-hosted Beav3r server

Runtime model

The current flow is:

OpenClaw raises an approval
the plugin normalizes and hands the request to the bridge
the bridge relays the request into Beav3r
a mobile signer approves or rejects
the terminal decision returns through the bridge to OpenClaw

What success looks like

Success means:

plugin and bridge health checks pass
the bridge authenticates to Beav3r
the signer receives the approval
the OpenClaw request resolves with the final decision

Overview LangGraph