Skip to main content
The Inkbox OpenClaw plugin is a standalone OpenClaw channel plugin. It connects an OpenClaw agent to an Inkbox identity and supports email, SMS/MMS and voice calls, iMessage, contacts, notes, contact rules, A2A task delegation, and an Inkbox tunnel when those capabilities are configured. This is a plugin, not an Inkbox SDK skill. It lives in its own repository and wires Inkbox directly into OpenClaw’s plugin SDK, gateway, tools, HTTP routes, CLI, and bundled OpenClaw task skills.

View plugin on GitHub

​
Install

For sponsored group conversations, check the Companion receiver requirements before installing or updating. Install and configure upstream OpenClaw first. The plugin currently targets OpenClaw 2026.5.27 or newer.
bash
Install the Inkbox plugin from source:
bash
Configure Inkbox and start or restart the gateway:
bash
OpenClaw requires the explicit install acknowledgement because the plugin’s gateway setup helper invokes the OpenClaw CLI. The setup wizard creates or connects an Inkbox agent, offers to connect iMessage, offers to provision a phone number, configures signed inbound messaging, and presents the available phone-call voice stacks when a calling channel is available. If the gateway is already running, restart it so it reloads the Inkbox channel config. Keep the gateway process running. On startup the plugin opens an Inkbox tunnel, configures identity-owned notification delivery, wires the incoming-call URL and call media WebSocket, and routes configured email, SMS/MMS, iMessage, and call channels into OpenClaw sessions.

​
Companion mode

The Companion contract requires SDK 0.7.3 or later. Confirm your installed OpenClaw adapter supports the current receiver contract. Updating only the SDK does not establish plugin compatibility. Enable the separate Companion toggle, then use active exact bidirectional allows to make senders eligible. The preference can be enabled before rules or channel resources exist. The adapter must load all authorized snapshot pages before one combined OpenClaw input and keep later live messages behind its initialization checkpoint. Replies retain the original activation’s email audience or canonical text/iMessage conversation ID. Historical commands and approvals remain context. Host denials still apply; incomplete context or uncertain acceptance must not release partial initialization. Installing or updating does not enable Companion mode. Rebuild and restart the gateway after upgrading. See Companion mode for email authentication, consent, dedicated-line iMessage groups, and revocation.

​
Available capabilities

Depending on your setup choices and account availability, your OpenClaw agent can have:
  • An email address - send, receive, search, and reply from an Inkbox mailbox
  • A phone number, when available - SMS/MMS and voice calls, inbound and outbound
  • iMessage, when connected - continue OpenClaw conversations from iMessage threads
  • An Inkbox tunnel - inbound webhooks and WebSocket connections reach the local OpenClaw gateway without a public server
  • Contacts and notes - persistent Inkbox records the agent can create, update, and read
  • Contact rules - mailbox and phone reachability controlled from Inkbox

​
What Inkbox adds

OpenClaw itself stays upstream. The plugin adds an Inkbox channel, tool group, CLI setup wizard, gateway webhook routing, and package-included task skills without requiring an OpenClaw fork.

​
After install

Run a quick health check:
bash
Use any channels you configured. If the agent has a phone number, text START to it from every phone the agent needs to text. This opts that phone number in to SMS from the agent. You can also email the agent mailbox, use iMessage when connected, or call the agent phone number when available; the gateway routes each configured channel into OpenClaw.