@rune-hq/openclaw-rune

OpenClaw channel plugin for the Rune smart ring.

Rune lets you press-to-talk on the ring and forwards the transcript into OpenClaw as a direct-message style agent turn. Agent replies are delivered to your configured OpenClaw reply channel, such as Telegram.

Requirements

• OpenClaw with native plugin support
• A configured OpenClaw reply channel, e.g. Telegram
• A Rune API key
• A paired Rune ring and the Rune mobile app

Install

openclaw plugins install @rune-hq/openclaw-rune
openclaw gateway restart

Configure

Add the Rune channel config to OpenClaw:

{
  "channels": {
    "rune": {
      "enabled": true,
      "apiKey": "<your-rune-api-key>",
      "replyChannel": "telegram",
      "replyTo": "<your-telegram-chat-id>"
    }
  }
}

Fields:

• enabled: Set to true to start the Rune channel.
• apiKey: Rune API key used to read pending transcripts and mark them delivered.
• replyChannel: OpenClaw channel where transcripts and agent replies should be sent.
• replyTo: Destination for that reply channel, such as a Telegram chat id.

Restart or reload the OpenClaw Gateway after changing config.

Verify setup

After installing and configuring:

1. Restart OpenClaw Gateway.

2. Check OpenClaw status/logs and confirm the rune plugin loads without errors.

3. Record a short test phrase with the ring.

4. Confirm your reply channel receives a message like:

   🎙️ Rune:
   <your transcript>

5. Confirm the agent replies in the same destination.

If no transcript appears, open the Rune app's log viewer first. It shows the ring state, such as idle or recording, which helps confirm whether the hardware button/recording path is working before debugging OpenClaw.

Troubleshooting

Plugin does not load

Run:

openclaw status

Common causes:

• Gateway has not been restarted since install/config changes.
• channels.rune is missing apiKey, replyChannel, or replyTo.
• The installed package is incomplete; reinstall the plugin.

License

MIT