🐝 OpenBee

Run Claude Code as your digital employee — command via Lark, DingTalk, WeCom, WeChat, or Telegram

中文

OpenBee is a digital employee solution that runs on your personal computer or server. You can communicate with it via Lark / DingTalk / WeCom / WeChat / Telegram to create workers, assign tasks, and much more — let your imagination run wild!

✨ Features

🤖 AI Workers	💬 Multi-IM Support	🧠 Persistent Memory
Each Worker is a Claude Code agent capable of multi-step task planning and independent execution	Native support for Lark, DingTalk, WeCom, WeChat, and Telegram — receive and reply in the same conversation	Workers retain long-term memory across sessions, knowing context just like a real employee
🔧 MCP Tool Invocation	⏰ Scheduled Tasks	🖥️ Web Console
Extend capabilities via MCP protocol — read files, call APIs, query databases	Cron-based scheduling for automatic, hands-free triggering	Visual interface for Worker management, task history, and real-time logs

🚀 Quick Start

Step 1: Install

📦 npm (Recommended)

npm install -g @theopenbee/cli

The platform-specific binary is downloaded automatically. Supports Linux / macOS / Windows (amd64 & arm64).

🔧 One-click Script

curl -fsSL https://raw.githubusercontent.com/theopenbee/openbee/main/install.sh | bash

🍺 brew (macOS) / scoop (Windows)

macOS (Homebrew):

brew install theopenbee/tap/openbee

Windows (Scoop):

scoop bucket add theopenbee https://github.com/theopenbee/scoop-bucket
scoop install theopenbee/openbee

📥 Manual Binary Download

Visit GitHub Releases, download the archive for your platform, extract it, and place the openbee executable in your PATH.

Step 2: Generate a config file

openbee config

The wizard will guide you through:

• Server port / host
• Claude executable path
• MCP API Key (can be randomly generated)
• IM platform(s) to enable (Lark / DingTalk / WeCom / WeChat / Telegram) and their credentials
• Advanced options (can be skipped to use defaults)

The config file is written to config.yaml in the current directory by default. Use -o to specify a custom path:

openbee config -o /path/to/config.yaml

Step 3: Start the service

openbee server -d

Step 4: Start using

• Open the Web Console (default http://localhost:8080) to manage Workers and view task status
• Send messages directly in any configured IM platform (Lark / DingTalk / WeCom / WeChat / Telegram) to interact with OpenBee

⚙️ How It Works

graph TD
    A["💬 IM Platforms\nLark / DingTalk / WeCom / WeChat / Telegram"] --> B["🔌 Platform Integration Layer"]
    B --> C["🧠 Central Brain\nClaude Code"]
    C --> D["📨 Task Assignment"]
    D --> E["🤖 Workers — Digital Employees\nClaude Code Agents"]
    E -. "Reply Results" .-> A
    C -. "Reply Results" .-> A

Loading

OpenBee consists of four core layers:

1. Platform Integration Layer Connects to IM platforms such as Lark, DingTalk, WeCom, WeChat, and Telegram to receive user messages in real time and reply with results in the same conversation.

2. Central Brain (Claude Code) The central brain receives all incoming messages, understands user intent, and decides how to handle them. Beyond task assignment, it is responsible for Worker management, session management, and other coordination duties. It can also reply results directly to the IM platform.

3. Task Assignment The central brain dispatches tasks to the appropriate Workers based on their capabilities and configuration. Scheduled tasks are also supported for automatic, time-based triggering.

4. Workers (Digital Employees) Each Worker is an independent Claude Code agent, equipped with persistent memory, tool invocation (MCP), and multi-step task planning. Workers execute assigned tasks autonomously and reply results directly to the IM platform — just like real employees.

🌟 Star History

🤝 Community

• 🐛 Bug reports / Feature requests → GitHub Issues
• 🤝 Contributing → Please read the Contributing Guide. You must agree to the Contributor License Agreement (CLA) before submitting.