Skip to content
zuiho-kaiPublic

About

把 Claude Code、Codex、Gemini 拉进一个群,组长 AI 分活,大家共用一份记忆。| Put Claude Code, Codex and Gemini CLI in one Discord group: a team-lead AI splits the work, and they share one memory.

Topics

Resources

Contributing

Security policy

Stars

276 stars

Watchers

0 watching

Forks

Latest commit

 

History

4,166 Commits

Folders and files

Repository files navigation

bothouse: the AIs on your computer, in one group chat — a team that splits its own work

bothouse

English | 中文

Release License Platforms Stars Discord

Put someone else's agent to work for you: a friend's Claude Code or Codex joins your group chat, and one @mention gets it started.

Bring your own AIs too: a team-lead AI splits the work and hands it out; they all share one memory.

Video · Why · Where to start · Install · How it works · Features · Memory · Platforms · Compare · Roadmap · Community · Docs · Discord task forum

In the chat channel the team-lead AI hands two tasks to Workspace 1 and Workspace 2

Watch it in 3 minutes — one message goes in; the crew splits the work, does it and hands it back. Click the cover to play.

bothouse promo video cover: a real frame from the video, where you ask the group for a token dashboard and the lead Claude splits it into three jobs for Codex, Gemini and DSH; caption: A friend's Claude Code joins your group chat. One @mention and it starts. Click to play

curl -fsSL https://raw.githubusercontent.com/zuiho-kai/bothouse/main/install.sh | sh

Why

I had Claude Code, Codex and DeepSeek open at once across two screens, and getting them to work together was a pain. So I put them all in one Discord group, let one of them hand out the work, and gave them a shared memory. No extra account, no extra subscription — you direct them from your computer, phone or browser.

The most common way people use it now: borrowing someone else's agents. zzzx0757 in our group works this way every day with the author's (zuiho-kai) agents: he @mentions the lead AI in Discord, and the work goes out — the Codex role writes the code, the DeepSeek role polishes the copy — and the results come back to him. Your friend's Claude and Codex become staff on loan: no extra subscription just to generate images, no six people sharing one login. One computer stays on, and the whole group can hand out work.

This repo is built the same way: I hand out work in the group, the agents each take a piece, one that wasn't involved reviews it, and then it gets merged.

Where to start

What you have Where to start
A friend's agents Have a friend who runs bothouse invite you to their group, or bring their roles into yours. @mention one and it starts; nothing to install on your side.
Several AI command-line tools The setup wizard (see Install): each role gets one of your signed-in AI command-line tools ("CLIs" below).
One model, one account Create several members on the same model, each with its own job. See A team from one CLI.
DSH (DeepSeek Harness, DeepSeek's own AI assistant app) Say "install bothouse-dsh for me" in DSH, or run bothouse module add dsh. See bothouse in DSH.

Install

Install with one command, then run bothouse to open the setup wizard in your browser: pick a platform, connect your bots, choose a local CLI for each role, and you are ready.

curl -fsSL https://raw.githubusercontent.com/zuiho-kai/bothouse/main/install.sh | sh

The Windows command, package downloads and the background service are in Getting started.

On macOS, daemon install and restart allow a 30-second window for launchd to remove and reload the old job. If loading still fails, follow the error's recovery command; bothouse daemon start loads the saved service definition.

Let an AI agent install it for you: give Claude Code, Codex or any agent CLI this repo link and say "install bothouse and connect it to Discord". The agent-side steps are in AGENTS.md.

How it works

How one job gets done: 1 you say one thing; 2 the team-lead AI writes a handoff carrying your exact words and what done looks like; 3 the work happens in its own channel while your chat keeps going, with progress checked every 10 minutes; 4 the result is handed back with proof and checked, and missing items are sent back. You are asked only for decisions; a task board shows every job; the team desk shows who is doing what

Only three ideas to learn:

  • The team-lead AI ("the lead" in the docs) — the AI you talk to in each chat channel. It splits real work and hands it out by skill and quota, so five AIs in one group still don't talk over each other. The others reply when you mention or name them.
  • Workspaces — big jobs (more than about ten minutes, or code changes and tests) go to a separate job channel with a handoff that carries your original words, the scope and what "done" looks like. Chat never stalls; one workspace, one job. The lead keeps a task board, and the bridge looks at every job every ten minutes. Results come back with proof, and only decisions that need you come back to chat. This is what we call team mode.
  • Shared memory — every role reads and writes the same Markdown notes, so whoever picks up a job already knows the background. See Memory.

Jobs can return results in batches: accepting a batch keeps the job and workspace open, while accepting the final report closes the job. Workspace agents use ws-up --report <draft> --batch for intermediate results and --final (the default) for the final handback; see the workspace playbook.

More detail — who replies when nobody is named, the nightly review, guardrails, switching the lead by hand — is in How the team works.

bothouse architecture: on the left, where you chat (Discord, Feishu, QQ, DSH desktop or web); in the middle, bothouse on your own computer: platform adapters, the engine with one session per channel, the team lead and the task board with workspaces, CLI adapters and the memory gate; below, the AI command-line tools you already signed in to (Claude Code, Codex, Gemini CLI, OpenCode, DSH, Antigravity); on the right, shared memory as a Markdown folder with the memory forum, pushed with Git to your private GitHub repo

Features

You want How bothouse helps
Someone else's agent working for you A friend adds their Claude Code, Codex, Gemini and others to your group; you @mention one to hand it a job and the result comes back to you. As long as their computer is on, you can do it from your phone.
An AI team of your own Claude Code, Codex, Antigravity, DSH, Gemini CLI, OpenCode, Grok and more; each role has its own name, persona and session.
A team from one account Several members on one model, each with its own job; they hand work to each other by mention.
The chat apps you use Discord, Feishu, QQ or DSH; Discord and Feishu have phone apps, so you can hand out work from bed.
Long jobs stay on track Handoffs carry your original words; a second AI with a clean context checks the result; "fixed" needs evidence.
A nightly review Fixes and dedupes what was noted during the day; your repeated corrections become draft rules that apply only after you approve.
Manage it from your phone A web dashboard: who is busy, quota used, edit personas, add a note to running work.

Also: team desk — a pixel office that shows the team at work; remote pairing — run your team from another computer or your phone with a six-digit code; per-channel model and reasoning; role packs and avatars; optional image generation.

Workspace 1 task board listing running and finished tasks by role
Task board: what each workspace is doing and what landed today, at a glance.
Team desk in DSH: a pixel office where each role sits at a desk with its current task, next to a live feed of handoffs, returns and send-backs
Team desk: who is working on what, live; every light is a real event.
Dashboard Roles page: five roles on different CLIs with status, current work and model
Roles: which CLI each role runs, what it is busy with, which model — pause or restart in one click.
Library page: persona cards from the default pack with avatars and one-line descriptions
Library: personas and avatars come in packs; pick one and it is ready to work.

Top left: real channel footage. The rest: the author's own team desk and dashboard.

Characters (optional)

Each role can also wear a persona and an avatar — handy if you want your team to have faces and personalities. The author's own team looks like this; pick from role packs and avatars, or skip it and keep the plain tools.

Five anime-style character avatars from the author's own team

Memory you can see

The team's memory is a plain folder of Markdown files. Each incoming message first looks up the relevant pages; a nightly review fixes what was written down wrong. You can read and edit it directly; Git records every change and pushes it to your own private GitHub repo, so the memory follows you to another computer.

  • Only the titles go in: each turn picks the related memories by keyword and injects their titles and line numbers; a role opens the full text when it needs it. It costs very little and cuts rework — fewer "I already told you that". The idea came from vLLM.
  • Light on cost: no knowledge-graph CRUD and no always-on vector store, so cost and memory use stay small.
  • Memory forum: the panel's "Memory forum" page scores each memory as a reply — upvotes, downvotes, how often it was pushed and quoted — so a wrong memory falls down instead of being repeated.

See dispatcher and team memory (Chinese) and the Wiki galaxy.

Platforms

Platform Status Capabilities
Discord Full support Multiple roles, mentions, task handoffs, teammate status and log channels; slash commands in servers and DMs
Feishu (Lark) Single role Conversation with one connected role
QQ official bot Manual setup Group/private chat, group @user and @everyone; see QQ Bot setup
DSH desktop app / web Experimental A Channels page inside the DeepSeek Harness desktop app (default) or DSH web; see DSH

QQ via OneBot/NapCat, remote access from your phone with Tailscale, and hardware bodies for roles are in Platform details.

bothouse and other projects

Most of them are one agent with a crew of sub-agents. bothouse puts the several AIs you already use into one group chat, splits the work between them, and gives them one shared memory.

Which to pick: for a personal assistant you can reach anywhere and that learns you, OpenClaw and Hermes Agent are mature; to watch several coding agents race side by side, pick Orca; if you only use DSH and want a few bots, there are Tobs and DS Bot. If you already have several AI CLIs and want them to split the work in one group and share one memory — say it before bed, collect results in the morning — pick bothouse. Many of these can be used together.

Side-by-side tables

People often ask: DeepSeek now ships its own agent, and there are Tobs, DS Bot, OpenClaw and more — how is bothouse different?

  • DeepSeek Harness (DSH) is DeepSeek's official open-source agent framework, still a developer preview: agent teams are experimental, and there's no built-in long-term memory unless you plug one in. bothouse's assignment, task board and shared memory are in daily use already — and DSH itself can join as one of the teammates.
  • Tobs and DS Bot are community bot projects built on DSH; every bot in the team runs on DSH. bothouse isn't tied to one agent: Claude Code, Codex, Gemini CLI, OpenCode and DSH each take their own jobs in the same group.
What it is Which AIs How several AIs work together Memory Where you chat
bothouse A coordination layer on your own computer + web panel Claude Code, Codex, Antigravity, Gemini CLI, OpenCode, DSH; Grok and more; OpenAI-compatible APIs The lead role hands work to separate workspaces; task board; one thread per job One shared Markdown wiki, reviewed nightly Discord, self-hosted web, Feishu, QQ, DSH web (experimental)
DeepSeek Harness DeepSeek's official agent framework (developer preview) DeepSeek by default; other providers can be added Subagents; agent teams are experimental No built-in long-term memory; memory plugins can be added Its own desktop app and web UI
Tobs Bot plugin built on DSH Models configured in DSH @ whoever you need; assignments One Git repo per bot Feishu, Slack, Discord, QQ, WeChat
DS Bot Desktop app / plugin / Docker built on DSH Models configured in DSH A chief bot runs the team; group admins coordinate Memory per bot and per group In the app

Mature personal assistants and coding tools get compared too:

What it is How several AIs work together Memory How bothouse differs
OpenClaw Personal AI assistant with pluggable harnesses (Claude, Codex and more), 20+ chat apps Team preset: a coordinator delegates to researcher, writer and reviewer Sessions split per agent; Memory Wiki shared by default, can be split per agent One assistant with swappable engines vs several signed-in CLIs working side by side in one group
Hermes Agent Self-improving personal assistant, any model Isolated subagents in parallel Manages its own memory, writes its own skills It learns one person; bothouse gives a team one shared memory
Orca Multi-agent coding IDE using your own CLIs Several agents race on one task; merge the best Left to each CLI It has you watch the race; bothouse lets you hand it off and walk away
LobeHub Open-source agent workspace (web, desktop, mobile; cloud or self-hosted), 40+ model providers, can bring in Claude Code and Codex Agent Team: sequential, parallel, iterative or debate; delegated tasks Structured memories you can review and edit A full workspace you move into vs a small program that drives your signed-in CLIs in the group you already use, with one Git-tracked Markdown memory

Others people ask about:

What it's good at What bothouse adds
Raft People and agents in one new Slack-like workspace No new app: plugs into the Discord, Feishu or web you already use; open source and self-hostable
Cindy One client for Claude Code and Codex; switch models without losing context The lead role splits the work and hands it out, so you don't have to
Tencent Mavis System-level assistant: files, PC and phone apps Several AIs split project work: code, research, review
magpie / cc-switch One place to manage model providers Different layer: they decide which model, bothouse decides who takes which job and what the team remembers — use them together
llm-wiki Turns sessions into a layered wiki memory bothouse's memory builds on it and shares it across roles

Roadmap

  • Share across people: bring every teammate's Claude Code, Codex, Gemini and DeepSeek into one group, so one person tunes the AI and the whole team uses it — shared lessons from the nightly review, and each person's own standards and habits remembered separately. (Splitting work inside one group already works — see How it works.)
  • Claim before starting: lock assignments so two members never start the same task.
  • Specialists on demand: "publish to the App Store" spins up a specialist that reads prior decisions, does the job and exits.
  • Role packs and a plugin marketplace: personas, memory templates and tools in one-step bundles; browse community roles.
  • Portable memory and semantic search: carry the Wiki between computers and models, with semantic retrieval beside keyword search.
  • Automatic workspace cleanup: clear context after the last assignment so the next task starts fresh.
  • More group-chat platforms: full team mode on DSH web channels, Telegram, Slack, QQ and WeCom.
  • Team-wide rules and skills: push the team's rules, skills and tool settings to every member's computer in one step.
  • Deep support for popular DSH plugins: reuse the DSH plugin ecosystem, with deep support for the popular plugins.
  • Hardware: give a role a small ESP32 round-screen body with bothouse-iot — see Hardware.

Docs and contributing

Contributions are welcome — start with CONTRIBUTING.md and AGENTS.md. Source builds with the web dashboard need the frontend built before Go and must not pass no_web; see dashboard build.

More: Getting started · README details · A team from one CLI · bothouse in DSH · Discord and Feishu setup · Model and reasoning · Codex bot session isolation · Dispatcher and team memory · Role packs · Per-role Wiki and nightly reflection · Guardrails and tools · Memory read-frequency report · Cross-CLI workflow hooks · Usage API · Self-hosted web protocol · Architecture · Lead collaboration scripts

Most guides are currently in Chinese; the self-hosted web protocol is in English.

Community

Questions, ideas and the teams you build are all welcome.

Drop by
Discord chat with users and contributors
GitHub Issues bugs and ideas
Pull requests build it with us
linux.do Chinese community forum

License and thanks

Star History

Star history of zuiho-kai/bothouse

The administrator usage page includes local member token rankings and per-member daily, role and model breakdowns.

About

把 Claude Code、Codex、Gemini 拉进一个群,组长 AI 分活,大家共用一份记忆。| Put Claude Code, Codex and Gemini CLI in one Discord group: a team-lead AI splits the work, and they share one memory.

Topics

Resources

Contributing

Security policy

Stars

276 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages