ClawKit bridge that pairs OpenClaw with WhisprAI Connect My Computer.
Install
openclaw plugins install clawhub:@clawkit/clawkit-for-whispraiClawKit for WhisprAI
ClawKit for WhisprAI lets a user pair their own OpenClaw computer with WhisprAI so Archie can act as a private local assistant.
Hosted WhisprAI does not need direct access to 127.0.0.1, a home router, a public tunnel, or the user's OpenClaw gateway. The plugin polls WhisprAI for queued work, runs the local OpenClaw agent, and sends Archie the result.
In WhisprAI this is surfaced through Settings → OpenClaw Helper and the Archie choices In the cloud, Cloud + my computer, and On my computer.
Archie Modes
| Mode | What it means | Best device |
|---|---|---|
| In the cloud | Archie uses the shared admin-managed OpenClaw Cloud/VPS tool. No personal computer is linked. | Mobile or desktop |
| Cloud + my computer | Archie can use the shared cloud for VPS/Kali work and can also ask the user's linked computer when the task needs that computer. | Set up on desktop; usable later from mobile |
| On my computer | Archie routes local-computer tasks to the user's paired OpenClaw computer through the outbound relay. | Desktop setup; mobile can use it after pairing |
This plugin is the local/connector side for the last two modes. In Cloud + my computer, WhisprAI can present the setup as a lightweight connector. Under the hood it still uses OpenClaw to run the secure outbound relay, but the user should only need to download, open, and approve pairing.
Early Public Release
This is an early public release. It is useful now for pairing WhisprAI with OpenClaw, but it will be updated continuously as real users test more computers, operating systems, relay flows, and assistant workflows.
Constructive feedback is very welcome, especially:
- Installer or connector steps that felt confusing.
- Pairing steps that felt confusing.
- Relay jobs that did not complete.
- OpenClaw responses that were not returned to Archie.
- Security or privacy concerns.
- Better wording for non-technical users.
- Ideas for safer approval flows and richer assistant actions.
Open an issue on GitHub:
https://github.com/MarcSean1971/clawkit-for-whisprai/issues
Product Promise
Bring Archie to your own computer, without exposing your computer to the public internet.
The plugin is designed for people who want WhisprAI to be more than a chat app. With OpenClaw paired locally, Archie can use the user's own OpenClaw setup, local files, configured tools, browser, GitHub access, coding tools, and approval flows.
What It Does
- Pairs this computer with WhisprAI using an explicit pairing flow.
- Uses OpenClaw plugin config for persistent relay settings.
- Keeps temporary pairing state in memory instead of reading or writing local state files.
- Polls WhisprAI for queued jobs.
- Runs
openclaw agentlocally with the queued user request. - Sends Archie the assistant reply.
- Skips silent lifecycle jobs such as chat-opened events without posting noisy fallback replies.
- Extracts visible assistant text from OpenClaw JSON, JSONL, and plain-text output while suppressing internal metadata.
- Provides a local status endpoint and CLI commands.
- Allows the user to revoke the pairing.
Commands
| Command | Purpose |
|---|---|
openclaw whisprai status | Show local pairing and relay state without printing secrets. |
openclaw whisprai connect | Print the local connect URL. |
openclaw whisprai pair start | Create a short pairing code. |
openclaw whisprai pair complete | Complete pairing from CLI or test flows. |
openclaw whisprai pair exchange | Exchange a pairing code with WhisprAI when supported by the hosted app. |
openclaw whisprai relay poll | Poll once for queued WhisprAI work. |
openclaw whisprai relay run | Run the relay loop in the foreground. |
openclaw whisprai revoke | Disconnect this computer from WhisprAI. |
Local Gateway Routes
| Route | Purpose |
|---|---|
GET /whisprai/status | Gateway-authenticated JSON status. |
GET /whisprai/connect | Gateway-authenticated local pairing helper page. |
POST /whisprai/pair/start | Create a short pairing code. |
POST /whisprai/pair/complete | Store relay and inbound details after confirmation. |
POST /whisprai/revoke | Disconnect this computer from WhisprAI. |
Install From ClawHub
openclaw plugins install @clawkit/clawkit-for-whisprai
openclaw plugins enable clawkit-whisprai
openclaw gateway restart
openclaw whisprai status
Development Install
From this repository:
npm test
openclaw plugins install -l . --force
openclaw gateway restart
openclaw whisprai status
Pairing Flow
- The user opens WhisprAI Settings and chooses OpenClaw Helper.
- On desktop, the user downloads the Windows, macOS, or Linux helper.
- The helper installs or updates OpenClaw and the plugin, starts the gateway, and asks for a short-lived pairing code.
- WhisprAI exchanges the pairing code for relay and inbound details.
- The plugin stores or receives those details through OpenClaw plugin config for persistence.
- The plugin polls for work and runs OpenClaw locally when Archie needs help.
- The user can revoke pairing at any time.
If OpenClaw is already installed, setup should update OpenClaw and reinstall the latest plugin package without wiping existing OpenClaw config, plugins, approval settings, or WhisprAI pairing history.
If the user later opens WhisprAI from mobile, they can still ask Archie to use the paired desktop computer as long as that computer is awake, online, and the connector is running. The phone itself is not paired; it is only the control surface.
Persistent Configuration
Marketplace-safe mode does not read or write a local state file. Temporary pairing details can exist while the plugin process is running, but production use should configure the relay details in OpenClaw plugin settings:
| Config key | Purpose |
|---|---|
whispraiUrl | WhisprAI app URL. |
relayUrl | Hosted WhisprAI relay endpoint. |
relayToken | Secret token used to poll queued work. |
inboundUrl | Hosted WhisprAI result endpoint. |
inboundSecret | Secret used to send results back. |
agentId | Local agent name shown in WhisprAI. |
pollIntervalMs | Relay polling interval. |
openclawCommand | Optional OpenClaw executable path or command. Leave empty to use openclaw from PATH. |
openclawArgsPrefix | Optional advanced argument array inserted before agent, useful for custom launch setups. |
After changing config, restart the OpenClaw gateway and run:
openclaw whisprai status
Production Flow
- WhisprAI queues work in the hosted relay.
- The plugin polls the relay with the local relay token.
- The plugin runs:
openclaw agent --session-id whisprai:<conversation_id> --message <request> --json --timeout 600
- The plugin extracts the visible assistant reply from OpenClaw output.
- Silent lifecycle jobs and
NO_REPLYoutputs are acknowledged without posting a user-visible response. - The plugin posts visible replies to WhisprAI using the inbound secret.
- The relay job is acknowledged as completed or failed.
Security Model
- Pairing is explicit and revocable.
- Relay and inbound secrets should be configured through OpenClaw plugin settings.
- The plugin no longer reads or writes a local state file for pairing details.
- Status output masks secrets.
- Hosted WhisprAI should never expose OpenClaw gateway URLs or secrets to normal users.
- The plugin does not open public inbound access to the user's computer.
- The plugin does not let one WhisprAI user access another user's paired computer.
- Sensitive computer actions should continue to rely on OpenClaw approval flows.
Important: this plugin intentionally launches the local openclaw executable with node:child_process. That is the core bridge behavior. ClawHub or other scanners may flag this as command execution. The command is scoped to openclaw agent, and users should install it only if they want WhisprAI to be able to ask their local OpenClaw agent for help.
Advanced users can set openclawCommand and openclawArgsPrefix in OpenClaw plugin config when the gateway process cannot find openclaw on PATH. This is useful for Windows services, scheduled tasks, or custom OpenClaw installations.
Privacy Notes
The plugin sends the queued WhisprAI request to the local OpenClaw agent and sends the assistant reply back to WhisprAI. It does not intentionally collect analytics or send local files by itself. Any tool, file, browser, GitHub, or computer action comes from the user's local OpenClaw configuration and approval model.
Example CLI Pairing
openclaw whisprai pair complete \
--code 123-456 \
--relay-url https://<project-ref>.supabase.co/functions/v1/openclaw-relay \
--relay-token <OPENCLAW_RELAY_TOKEN> \
--inbound-url https://<project-ref>.supabase.co/functions/v1/openclaw-inbound \
--inbound-secret <OPENCLAW_INBOUND_SECRET> \
--agent-id main
openclaw whisprai relay poll
Package Shape
index.js: OpenClaw plugin entry, CLI commands, local routes, relay polling, and agent handoff.extract-agent-text.js: extracts user-visible assistant text from OpenClaw JSON/stdout.extract-agent-text.test.mjs: focused parser tests.openclaw.plugin.json: native OpenClaw manifest.docs/clawhub-listing.md: marketplace listing draft.docs/product-strategy.md: positioning and roadmap.
Roadmap
- Friendlier mobile/desktop pairing guidance for non-technical users.
- Stronger relay diagnostics and self-healing status messages. v0.1.10 keeps the public package on the correct ClawKit for WhisprAI name/source, documents the new Archie modes, and preserves the silent-job handling, visible-reply extraction, and configurable OpenClaw launch settings from earlier releases.
- Better Cloud + my computer connector copy, including temporary vs remembered links.
- Richer job types beyond simple assistant text.
- Better user consent screens before sensitive local actions.
- Optional GitHub issue/PR workflows through the user's OpenClaw tools.
- Signed release and verification guidance.