TapTapAI OpenClaw Plugin

TapTapAI plugin for OpenClaw with outbound backend connectivity.

• Primary: wss://.../ws/openclaw/v2
• Fallback: https://.../relay/*

There are no chat setup commands.

Plugin ID: taptapai-openclaw

Setup/pairing is done via the taptapai CLI (recommended) or by manually editing OpenClaw config.

Recommended setup (terminal)

On the OpenClaw host:

taptapai setup

Manual setup (advanced)

1) Enable plugin

openclaw plugins enable taptapai-openclaw

2) Install plugin files/deps (if needed)

mkdir -p ~/.openclaw/extensions
cp -r openclaw-plugin ~/.openclaw/extensions/taptapai
cd ~/.openclaw/extensions/taptapai && npm install --omit=dev

3) Configure (no channels)

Use plugin config under plugins.entries.taptapai-openclaw.config:

# Required
openclaw config set plugins.entries.taptapai-openclaw.config.backendWsUrl "wss://your-backend.example.com/ws/openclaw/v2"
openclaw config set plugins.entries.taptapai-openclaw.config.relayUrl "https://your-backend.example.com"

# Optional (first run only). The plugin clears it after successful setup.
openclaw config set plugins.entries.taptapai-openclaw.config.setupPassword "choose-a-strong-password"

# Optional
openclaw config set plugins.entries.taptapai-openclaw.config.pollIntervalMs 1000
openclaw config set plugins.entries.taptapai-openclaw.config.logLevel "info"

4) Restart gateway

systemctl --user restart openclaw-gateway.service

5) Pair iOS using logs

journalctl --user -u openclaw-gateway.service -n 200 --no-pager | grep -E "Pair token:|QR payload:"

Use the emitted token (or QR payload) in the iOS app.

After successful setup, setupPassword is removed from config automatically.

Rotation

To rotate (new token; old token becomes invalid), use:

taptapai rotate-credential

This prompts for the original setup password, verifies it, and then increments N.

Manual rotation (advanced)

If you are not using the CLI, the plugin can still bootstrap/rotate from a one-time setupPassword:

1. Set a new one-time password:

openclaw config set plugins.entries.taptapai-openclaw.config.setupPassword "new-strong-password"

2. Restart the gateway.

The plugin will generate a new token (increments N), overwrite the cached secret, update config, and rewrite pairing artifacts.

Show current token/QR (no rotation)

If you just need the current token + QR again, run taptapai setup (it prints the current token/QR without rotating).

Or manually:

openclaw config set plugins.entries.taptapai-openclaw.config.emitPairingArtifacts true

Restart the gateway; the plugin rewrites the pairing artifacts and clears the flag.

Configuration

| Option | Required | Description | |---|---|---| | backendWsUrl | Yes | Backend WS URL (wss://.../ws/openclaw/v2) | | relayUrl | Yes | Relay fallback URL (https://...) | | pollIntervalMs | No | Relay poll interval (ms) | | setupPassword | First run | One-time password used to derive token; auto-cleared | | wsToken / token | No | Auto-managed after setup | | emitPairingArtifacts | No | If true, write pairing artifacts and clear the flag | | emitPairingArtifactsIncludeDataUrl | No | If true, also write QR data URL artifact | | logLevel | No | error/warn/info/debug |

Verification

journalctl --user -u openclaw-gateway.service -n 200 --no-pager | grep -i "taptapai\|WS connected\|Pair token"

Troubleshooting

• If setup did not run, prefer taptapai setup. If doing manual setup, ensure setupPassword is set and restart gateway.
• If backend WS does not connect, ensure backendWsUrl is wss://.
• If relay is used, ensure relayUrl is https://.