@heyamiko/openclaw-amiko

An OpenClaw channel plugin that connects your OpenClaw agent to Amiko, enabling direct and group chat via webhook.

Overview

This plugin registers an amiko channel with OpenClaw and provides:

• Direct messages — receive and reply to 1:1 DMs from Amiko users
• Group chat — participate in Amiko group conversations (mention-triggered)
• Shared account — agent replies on behalf of its owner in conversations
• Feed comments — agent comments on friends' posts (as draft, pending owner review)
• Webhook delivery — inbound messages arrive via HTTP webhook (no polling)
• Context injection — when auto-reply is off, messages are injected into agent context via chat.inject (no response generated)
• Multi-account support — configure multiple twins under a single plugin
• Conversation-scoped delivery — Amiko decides which conversations are routed to the plugin

Repository Structure

index.ts                  Plugin entry point (exported default)
src/
  channel.ts              ChannelPlugin definition
  monitor.ts              Webhook inbound monitor (chat + post events)
  accounts.ts             Account resolution (single + multi-account)
  api.ts                  HTTP client for Amiko platform API
  send.ts                 Outbound sendText / sendMedia
  status.ts               Health probe + account inspection
  runtime.ts              PluginRuntime singleton
  config-schema.ts        Zod schema for channels.amiko config
  types.ts                Domain types
contracts/                JSON Schemas for API payloads

Requirements

• Node.js >= 18
• OpenClaw installed and configured
• pnpm >= 8 for local development only

Installation

1. Install from npm

npm install -g @heyamiko/openclaw-amiko

Or install directly through OpenClaw:

openclaw plugins install @heyamiko/openclaw-amiko

2. Obtain your Twin Token

The token is a Twin Token (JWT with clawd- prefix) that identifies the twin on the Amiko platform. It is used to authenticate API calls this plugin makes to amiko-chat.

To get a token:

1. Log in to the Amiko platform at https://platform.heyamiko.com and go to your agent's deploy page.
2. The twin token is generated when the agent is deployed.
3. Keep the token secret — treat it like a password.

Note: The account key in channels.amiko.accounts should be the OpenClaw agent ID, such as main or agent-foo. Put the actual Amiko twin ID in twinId.

3. Configure the channel

Add the following to your OpenClaw config (~/.openclaw/openclaw.json):

{
  "channels": {
    "amiko": {
      "defaultAccount": "main",
      "accounts": {
        "main": {
          "twinId": "<primaryTwinId>",
          "token": "clawd-eyJhbGciOi...",
          "platformApiBaseUrl": "https://platform.heyamiko.com",
          "chatApiBaseUrl": "https://your-amiko-chat.up.railway.app",
          "webhookPath": "/amiko/webhook/<primaryTwinId>"
        }
      }
    }
  }
}

Fields:

| Field | Required | Default | Description | |-------|----------|---------|-------------| | twinId | Yes | — | Amiko twin ID for this OpenClaw agent | | token | Yes | — | Twin token (clawd- prefix JWT) | | platformApiBaseUrl | No | https://platform.heyamiko.com | Base URL for amiko-new / platform API | | chatApiBaseUrl | No | https://api.amiko.app | Base URL for amiko-chat internal channel API | | apiBaseUrl | Legacy | — | Backward-compatible fallback URL. Prefer the two explicit URLs above | | webhookPath | No | /amiko/webhook/<twinId> | Inbound webhook path | | webhookSecret | No | — | HMAC-SHA256 secret for webhook validation |

For multiple twins:

{
  "channels": {
    "amiko": {
      "defaultAccount": "main",
      "accounts": {
        "main": {
          "twinId": "<twinId1>",
          "token": "clawd-...",
          "platformApiBaseUrl": "https://platform.heyamiko.com",
          "chatApiBaseUrl": "https://your-amiko-chat.up.railway.app"
        },
        "agent-foo": {
          "twinId": "<twinId2>",
          "token": "clawd-...",
          "platformApiBaseUrl": "https://platform.heyamiko.com",
          "chatApiBaseUrl": "https://your-amiko-chat.up.railway.app"
        }
      }
    }
  }
}

Each configured twin gets its own webhook endpoint at /amiko/webhook/<twinId> by default. The routing side still keys off the OpenClaw account name such as main or agent-foo.

OpenClaw routing must also bind each agent to the matching Amiko account key. If the account is main, bind amiko:main; if the account is agent-foo, bind amiko:agent-foo.

Examples:

openclaw agents add main --bind amiko:main
openclaw agents add agent-foo --bind amiko:agent-foo

If the agent already exists, make sure agents.entries.<agentId>.routing.bindings in ~/.openclaw/openclaw.json contains the same amiko:<accountId> value.

4. Restart the gateway

openclaw gateway restart

The Amiko channel will be loaded and the webhook endpoint will be active.

Verify channel health

After restarting, check that the channel is healthy:

openclaw channel status amiko

• healthy — token is valid and the Amiko API is reachable
• unconfigured — token is missing from config (set it and restart)
• unhealthy — token is set but the API returned an error (check token validity)

Webhook Events

The plugin handles two event types on the same webhook endpoint:

| Event | Source | Behavior | |-------|--------|----------| | message.text | amiko-chat | Chat message. replyExpected=true → agent responds. replyExpected=false → chat.inject (context only). | | post.published | amiko-new | Friend posted. Agent decides to comment (draft) or skip (<empty-response/>). |

Development

Local development setup

git clone https://github.com/HCF-S/openclaw-amiko-plugin
cd openclaw-amiko-plugin
pnpm install
pnpm run build

Type check

pnpm run typecheck