Set up OP for OpenClaw agents
Install the OP plugin for OpenClaw, expose the local webhook endpoint, restart OpenClaw, and send the first SMS from the OP CLI.
Install the plugin
openclaw plugins install JoshMayerr/openclaw-op-plugin --enableExpose OpenClaw locally
cloudflared tunnel --url http://localhost:<openclaw-port>Configure OP
openclaw plugin setup op \
--phone +1HUMAN_NUMBER \
--webhook-url https://your-tunnel.trycloudflare.com/webhooks/opSend a text
openclaw restart
op send \
--to +1RECIPIENT_NUMBER \
--body "hello from OpenClaw via OP"Why OpenClaw needs a webhook URL
The OpenClaw plugin provides the OP channel runtime, setup entry, and an op send CLI path for one-off outbound SMS. Once OpenClaw loads the channel config, the useful workflow is two-way: inbound messages, replies, OTPs, and delivery events all attached to the same agent phone number.
That is why the setup step asks for a webhook URL. OP sends inbound events there, and OpenClaw can decide what to do next inside the agent workflow.
Use a tunnel for local development
If your OpenClaw runtime is on your laptop, the public internet cannot reach it directly. Start a Cloudflare tunnel against the OpenClaw port, then pass the resulting HTTPS URL to the OP plugin setup command.
When you deploy OpenClaw to a stable environment, replace the tunnel URL with your production webhook URL. The rest of the OP setup stays the same.
Keep the phone number attached
The point of OP is not just one test SMS. It gives OpenClaw a durable phone identity that can receive codes, get replies, and remain associated with the delegated account or task.
Use the same OP number for follow-up messages and verification flows so the agent is not constantly swapping identities between tools.
About OpenClaw CLI command names
The plugin package exposes an op command entry for hosts that surface plugin commands, and an openclaw-op binary fallback with the same arguments. Use openclaw-op send if your OpenClaw host does not expose plugin commands as op.
For end-to-end verification, also text your OP number from an allowed phone and confirm the OP channel receives the webhook and replies.
Final step: ask the agent what OP unlocks
After the first message works, give the agent one more instruction. This turns setup into a useful handoff instead of stopping at a successful test SMS.
Read https://www.op.inc/skills.md and https://api.op.inc/docs.
Now tell me what you can do with OP from here.
Include:
- the OP number you are using
- how you can send texts
- how you can receive replies or OTP codes
- whether webhooks or polling make more sense for this project
- whether I should use the shared free number or lease a dedicated number
- any voice-call capabilities that are relevant
- 3 useful next workflows you can handle for me
Before sending real messages to anyone else, ask for my approval.For the broader setup map, read Set up OP for AI agents.