# Mingle

> Mingle brings Claude Code, Codex or another agent you already have into WeChat, Feishu, Slack, Telegram and more as a bot, with a name, a role and a memory. It runs on your computer. There is no Mingle server.

Key facts:

- Website: https://mingle.build/ (English), https://mingle.build/zh/ (Chinese)
- Source: https://github.com/earayu/Mingle (MIT)
- Latest release: https://github.com/earayu/Mingle/releases/latest (v0.1.0)
- Install on macOS or Linux: `curl -fsSL https://github.com/earayu/Mingle/releases/latest/download/install.sh | sh`
- Install on Windows (PowerShell): `irm https://github.com/earayu/Mingle/releases/latest/download/install.ps1 | iex`
- Price: free. No account, no Mingle server, no telemetry.

## What it does

- You create an agent on your own computer: a name, a role (ROLE.md), a memory (MEMORY.md, notes/) and a home folder.
- A coding agent you already have installed and signed in to drives it: Claude Code, Codex, OpenCode, Kimi Code, Qwen Code, Grok Build, Pi. Tested end to end with Claude Code and Codex. Mingle never calls a model itself.
- The agent joins WeChat, WeCom, Feishu, DingTalk, QQ, Slack, Discord, Telegram as a bot, through each app's official bot API. People message it directly or @ it in a group.
- One agent keeps one long-lived session and one memory across every chat app. There are no session commands; the owner can send /stop.
- It keeps tasks and reminders, shows progress (a reaction, then a live reply), sends and receives files, and reports back where it was asked.
- Managed from a desktop app (macOS, Windows, Linux; menu bar or tray, auto-update), a local web console on 127.0.0.1, or the `mingle` command.
- Bot credentials are stored only in the macOS Keychain, Windows DPAPI or the Linux Secret Service.

## Command line

Build from source (Node.js 24, pnpm): `git clone https://github.com/earayu/Mingle.git && cd Mingle && pnpm install && pnpm build`, then run `node dist/cli/main.js`.

- `mingle start [--port 7419] [--no-open]`: run Mingle and open the console
- `mingle status`: agents and their connections
- `mingle harnesses`: harnesses installed on this computer
- `mingle agent create --name <n> --harness <id> [--model <m>] [--role <text> | --role-file <path>]`
- `mingle connect <agent> telegram`: bot token on standard input
- Inside a session, agents use `mingle message reply|send|read|search`, `mingle chat list|info`, `mingle file get`, `mingle task create|list|update`, `mingle reminder set|list|cancel`, and `mingle manual` for their full guide.
- Add `--json` for machine-readable output.

## Docs

- [README](https://github.com/earayu/Mingle#readme): status, install, quick start
- [Product design and architecture](https://github.com/earayu/Mingle/blob/main/docs/spec.md) (Chinese)
- [Interface design](https://github.com/earayu/Mingle/blob/main/DESIGN.md) (Chinese)
- [Changelog](https://github.com/earayu/Mingle/blob/main/CHANGELOG.md)
- [Releasing](https://github.com/earayu/Mingle/blob/main/docs/releasing.md)

## Common questions

- **Does my data go to a Mingle server?** No. There is none. Messages still pass through the chat app and your model provider.
- **Do I need an API key?** No, if your harness is signed in with a subscription. An API key set for Claude Code or Codex also works.
- **Is the app signed?** Not yet. On macOS, allow it in System Settings → Privacy & Security; on Windows, choose More info → Run anyway.