Unbelievable — just stumbled upon a god-tier project on GitHub that absolutely demolishes all the automation pain points in the WeChat ecosystem. This is openilink-hub, released not long ago. In a nutshell, it’s an open-source WeChat Bot management platform + App Marketplace. It’s self-hostable and comes with a built-in app store that covers 20+ mainstream tools (Lark, Slack, Discord, DingTalk, GitHub, Notion, and more) plus AI models — all in one go. Written in Go, supports one-click Docker deployment, and is fully security and privacy focused.

Core highlights at a glance:

• Freeloaders rejoice: Completely open-source and free, supports local or private cloud deployment — you own all your data.
• Built-in App Marketplace: 20+ common office and AI tools are ready to use out of the box — no need to write complex API integrations yourself.
• Universal Connector: Sync WeChat messages to Discord, Slack, or Lark with one click — group management and notification automation are a breeze.
• 7 Language SDKs: Developers, take note — whether you use Python, Node, or Java, you can easily integrate and do secondary development.
• Perfect AI Agent Carrier: Hook it up with Coze, LangChain, or a local model — you’ll have a WeChat digital employee in minutes.

This is pretty savage. In the past, setting up this kind of WeChat automation would require stepping on countless pitfalls. Now, one project does it all. If you know, you know — anyone doing community automation or AI deployment should jump in without hesitation.

GitHub link: https://github.com/openilink/openilink-hub…

openilink/openilink-hub

Source: https://github.com/openilink/openilink-hub

免责声明:本项目基于公开的 iLink 协议进行独立开发,仅供学习交流与技术研究使用。项目与 iLink 协议的官方团队无任何关联或授权关系。若相关权利方认为本项目存在侵权,请通过 Issue 联系我们,我们将在确认后第一时间予以下架处理。

Disclaimer: This project is independently developed based on the publicly available iLink protocol for learning and research purposes only. It is not affiliated with or endorsed by the official iLink team. If any rights holder believes this project infringes upon their rights, please contact us via an Issue and we will take it down promptly upon confirmation.

微信 ClawBot iLink 协议的开源消息管理平台 + App 应用市场

Open-source message management platform + App Marketplace for WeChat ClawBot (iLink protocol)

Scan to bind your WeChat account, extend capabilities with one click via the app marketplace — Lark / Slack / Discord / GitHub / Notion and 20+ apps. Install and use.

Multi-bot management · 20+ Apps · Platform interoperability · Productivity tools · Life assistants · AI Tools · 7 language SDKs · Passkey login

License Go (https://go.dev) React (https://react.dev) Docker (https://hub.docker.com/r/openilink/openilink-hub) GitHub Stars (https://github.com/openilink/openilink-hub/stargazers) Release (https://github.com/openilink/openilink-hub/releases)

Official site & docs (https://openilink.com) · Online demo (https://hub.openilink.com) · Quick Start · App Marketplace · SDK · English

快速开始 (Quick Start)

# One-click install (Linux / macOS)
curl -fsSL https://raw.githubusercontent.com/openilink/openilink-hub/main/install.sh | sh

# Start
oih

# Or use Docker (choose one)
docker run -d -p 9800:9800 openilink/openilink-hub:latest # Docker Hub
# or:
docker run -d -p 9800:9800 ghcr.io/openilink/openilink-hub:latest # GHCR

Open http://localhost:9800, register an account (the first to register becomes admin automatically), scan the QR code to bind your WeChat account, and you’re done.

Default uses SQLite — no database needed, no configuration required. Want PostgreSQL? Just set DATABASE_URL.

Windows users: Native Windows is not supported. Please use one of the following:

• Docker (recommended): docker run -d -p 9800:9800 openilink/openilink-hub:latest
• WSL2: Run the Linux method above inside WSL’s Ubuntu/Debian

What Is This?

In March 2026, WeChat launched the ClawBot plugin, with the underlying protocol called iLink (Smart Link) — the first time the official platform allows programmatic sending and receiving of WeChat messages.

But iLink is just a raw channel: you can receive messages, send replies, and that’s it. You still have to handle context_token, CDN encryption, 24-hour expiry, multi-bot management…

OpeniLink Hub handles all of that, and via the App Marketplace lets you extend functionality with one click:

• Scan QR code to bind, manage multiple bots from a web dashboard
• Install features from the marketplace — integrate Lark / Slack / GitHub / Notion, check weather, track expenses, AI chat — no coding required
• Forward messages simultaneously via WebSocket / Webhook / AI channels to your service
• Get notified before the 24-hour window expires to avoid missing renewal
• Message trace — see exactly where a problem occurs

flowchart TD
    subgraph WeChat
        A[微信 ClawBot 插件]
    end
    A -->|iLink 协议| B[OpeniLink SDK]
    subgraph OpeniLink["OpeniLink Hub"]
        C[消息调度]
    end
    B --> C
    C --> D[App: 平台互通飞书 / Slack / Discord / 钉钉 / 企业微信]
    C --> E[App: 效率工具GitHub / Google / Notion / Linear]
    C --> F[App: 生活工具天气 / 汇率 / 记账 / 地图 / RSS ...]
    C --> G[App: OpenClaw]
    C --> H[自定义 App]
    C --> I[WebSocket 实时推送]
    C --> J[Webhook 转发]
    C --> K[AI 自动回复]
    D --> L[第三方平台消息互通 + AI Tools]
    E --> M[项目管理 / 文档协作 / 代码仓库]
    F --> N[日常查询 / 自动化 / 个人助手]
    G --> O[AI Agent Gateway]
    H --> P[你的业务系统]
    I --> Q[实时客户端]
    J --> R[HTTP 回调服务]
    K --> S[LLM]

Relationship with OpenClaw?

OpenClaw is an AI Agent framework; OpeniLink Hub is a message management platform — two different things.

In Hub, OpenClaw is a built-in App — just enable it from the marketplace. Of course you can completely ignore OpenClaw and choose other apps, or directly use WebSocket/Webhook to connect your own services.

Simply put: OpenClaw handles AI logic, Hub handles message sending/receiving and app distribution — each does its own thing, and you can connect them as you wish.

Why Use Hub?

Problems When Integrating iLink Yourself

Comparison with Other Open-Source Projects

There are several iLink-related open-source projects on GitHub, but most are low-level SDKs or Agent bridging tools. Hub is the only complete platform that includes a management dashboard + app marketplace + multi-channel distribution.

Core Features

App Marketplace · Extend your bot without writing code. 20+ official apps covering platform interoperability (Lark, Slack, Discord, DingTalk, WeCom), productivity (GitHub, Google Workspace, Notion, Linear), life tools (weather, currency, expense, maps, RSS), and more. Installed with PKCE OAuth for security. Supports third-party developers to publish apps.

Multi-Bot Management · Scan QR codes to bind multiple WeChat accounts, unified dashboard for status, pre-expiry notifications to prevent disconnection.

Note: The WeChat 24-hour window currently cannot be silently auto-renewed by Hub in the background. Hub supports “pre-expiry notification” — it reminds you before the window expires, and after you reply, the window restarts.

Multi-Channel Message Delivery

• App — installed apps automatically receive matched messages via WebSocket or Webhook delivery
• WebSocket — real-time push with millisecond latency
• Webhook — HTTP callback, connect to any service
• AI auto-reply — integrate OpenAI-compatible API for automatic bot conversation

Message Tracing · Complete chain from receipt to delivery — see at a glance how long each step took, quickly locate issues.

Passkey Login · Fingerprint, Face ID, hardware key — also supports GitHub / LinuxDo OAuth.

Management Dashboard · User management, role permissions, OAuth configuration, global AI settings, App management — all in one place.

App Marketplace

The core extension mechanism of Hub. Each App is an independent service that interacts with Hub via a standard protocol.

What Can You Install?

Platform Interoperability — Bidirectional message sync between WeChat and third-party platforms + AI Tools for natural language operations

Productivity Tools — Operate mainstream SaaS platforms from WeChat via natural language

Life Tools — Lightweight and practical, zero-config or free API to run

Developer & Infrastructure

App Types

How to Install?

1. Go to the “App Marketplace” in the Hub dashboard
2. Find the App you want, click “Install”
3. Complete authorization via PKCE OAuth
4. The App starts receiving messages — done

How to Develop?

Apps interact with Hub via:

• Receiving events: WebSocket connection or Webhook callback
• Defining commands: Declare tools and commands — triggered via /command or @mention
• Sending replies: Call Hub API to send messages

Refer to openilink-app-echo for a quick start.

Mock Server (Local Development & Debugging)

No need to run a real Hub + WeChat Bot — use the Mock Server for local development and testing:

# Start Mock Server, deliver events via Webhook to your App
go run ./cmd/appmock --webhook-url http://localhost:8080/webhook

# Inject a simulated message to trigger your App
curl -X POST http://localhost:9801/mock/event \
  -d '{"sender":"alice","content":"@test-app hello"}'

# See what messages your App sent
curl http://localhost:9801/mock/messages

The Mock Server reuses the real Bot API handler — behavior is identical to production. See full docs at docs/mock-server.md.

Architecture Overview

flowchart TB
    subgraph Client["客户端"]
        direction TB
        WX[微信号扫码绑定] --> Provider[ProvideriLink]
        UI[Web UIReact] --> API[REST APIGo]
    end
    Provider --> Broker[Message Broker]
    API --> Broker
    Broker --> AppDispatch[App 调度]
    Broker --> WS[WebSocket实时客户端]
    Broker --> WH[Webhook回调]
    Broker --> AI[AI Sink自动回复]
    AppDispatch --> BuiltinApps[内置 AppBridge / OpenClaw]
    AppDispatch --> MarketApps[市场 AppEcho / Command Service]
    AppDispatch --> CustomApps[自定义 App]
    subgraph Storage["存储"]
        DB[(SQLite / PostgreSQL数据)]
        MinIO[(MinIO媒体存储)]
        PK[PasskeyWebAuthn]
    end

Deployment Guide

Data Storage

Default SQLite, zero config. Data file locations:

• Linux: ~/.local/share/openilink-hub/openilink.db
• macOS: ~/Library/Application Support/openilink-hub/openilink.db
• root/service: /var/lib/openilink-hub/openilink.db

Set DATABASE_URL=postgres://... to switch to PostgreSQL.

Register as System Service

oih install   # Install systemd (Linux) / launchd (macOS) service
oih uninstall # Uninstall service

Docker Compose (Production)

Suitable for scenarios requiring PostgreSQL + MinIO:

services:
  postgres:
    image: postgres:17-alpine
    environment:
      POSTGRES_USER: openilink
      POSTGRES_PASSWORD: <change to strong password>
      POSTGRES_DB: openilink
    volumes:
      - pgdata:/var/lib/postgresql/data

  hub:
    image: openilink/openilink-hub:latest   # or ghcr.io/openilink/openilink-hub:latest
    ports:
      - "9800:9800"
    environment:
      DATABASE_URL: postgres://openilink:<password>@postgres:5432/openilink?sslmode=disable
      RP_ORIGIN: https://hub.example.com
      RP_ID: hub.example.com
      SECRET: <random string>
    depends_on:
      - postgres

volumes:
  pgdata:

Just put an Nginx / Caddy in front as an HTTPS reverse proxy.

Build from Source

cd web && pnpm install && pnpm run build && cd ..
go build -o oih .
./oih

CLI Commands

SDK Ecosystem

7 languages — pick the one you’re comfortable with:

Related Projects

Apps (full list in App Marketplace)

More apps: amap · weather · currency · expense · reminder · cron · rss · qrcode · command-service · runner

Other

Environment Variables

Configuring OAuth Login

GitHub OAuth

1. Go to GitHub Developer Settings (https://github.com/settings/developers) → OAuth Apps → New OAuth App
2. Homepage URL: https://hub.example.com
3. Callback URL: https://hub.example.com/api/auth/oauth/github/callback
4. Get Client ID and Secret, fill in environment variables

LinuxDo OAuth

1. Create an app at connect.linux.do (https://connect.linux.do)
2. Callback URL: https://hub.example.com/api/auth/oauth/linuxdo/callback
3. Fill in environment variables

Callback URL format: {RP_ORIGIN}/api/auth/oauth/{provider}/callback

Tech Stack

Contributing

Issues and PRs are welcome!

• For App development, refer to openilink-app-echo
• Submit plugins to openilink-webhook-plugins
• For SDK issues, go to the corresponding language repository

License

MIT — free to use, including commercial use.

OpeniLink (https://openilink.com) · Making WeChat Bot integration simpler

English

OpeniLink Hub is a self-hosted, open-source WeChat Bot management and message relay platform built on top of the iLink protocol — WeChat’s first official Bot API, launched in March 2026. It wraps WeChat’s raw messaging into a complete system: bind multiple accounts via QR code, install apps from the marketplace to add features like stock queries and image generation, forward messages through WebSocket / Webhook / AI auto-reply — all managed from a web dashboard.

Key Highlights

• App Marketplace (20+) — Platform integration (Lark, Slack, Discord, DingTalk, WeCom), productivity (GitHub, Google Workspace, Notion, Linear), utilities (weather, expense, RSS, maps…), all with AI Tools
• Multi-bot management — Bind and manage multiple WeChat accounts, auto session renewal
• Message tracing — Full delivery timeline for every message, pinpoint issues instantly
• Multi-channel delivery — Apps, WebSocket, Webhook, and AI auto-reply in parallel
• Passkey (WebAuthn) — Passwordless login with biometric / hardware key support
• Built-in SQLite — Zero-config database with optional PostgreSQL
• 7 language SDKs — Go, Node.js, Python, PHP, Java, C#, Lua

Quick Start

# One-line install
curl -fsSL https://raw.githubusercontent.com/openilink/openilink-hub/main/install.sh | sh

# Start
oih

# Or use Docker (either registry works)
docker run -d -p 9800:9800 openilink/openilink-hub:latest # Docker Hub
# or:
docker run -d -p 9800:9800 ghcr.io/openilink/openilink-hub:latest # GHCR

Visit http://localhost:9800 — first user becomes admin. Zero config needed.

Website: openilink.com · Live Demo: hub.openilink.com