Maintainer of this skill?
by zuiho-kai
把电脑上的 Claude Code、Codex、Gemini、DeepSeek 拉进一个群，组成共享记忆、自己分活的 AI 小团队；一个人调好的 AI，全队都能用。| Bring your local AI CLIs into one group chat as a team with shared memory — and share one tuned setup across your whole team.
# Add to your Claude Code skills
git clone https://github.com/zuiho-kai/bothouseGuides for using ai agents skills like bothouse.
See how bothouse compares with popular alternatives.
bothouse is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by zuiho-kai. 把电脑上的 Claude Code、Codex、Gemini、DeepSeek 拉进一个群，组成共享记忆、自己分活的 AI 小团队；一个人调好的 AI，全队都能用。| Bring your local AI CLIs into one group chat as a team with shared memory — and share one tuned setup across your whole team. It has 162 GitHub stars.
bothouse's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/zuiho-kai/bothouse" and add it to your Claude Code skills directory (see the Installation section above).
bothouse is primarily written in Go. It is open-source under zuiho-kai on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh bothouse against similar tools.
No comments yet. Be the first to share your thoughts!
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
English ｜ 中文
bothouse: put Claude Code, Codex, Gemini CLI and DeepSeek on your computer into one group chat — an AI team that shares one memory and divides up its own work.
What's next: team mode — one person tunes the AI, the whole team uses it; hardware — give a role a small ESP32 body (bothouse-iot).
Video · What's next · Install · Features · Screenshots · Memory · Compare · Community · Docs
Watch bothouse in 3 minutes: one message goes in; the crew splits the work, takes it on and hands it back. Click the cover to play.
New installs default to Only when addressed: the role you @ answers, nothing extra to install. Smart routing can be turned on in the wizard or later on the panel's Gate page; it needs a judge model that returns logprobs, and the wizard offers a one-click preset for the Qwen3.5-4B we run ourselves (local, mlx-lm on Apple silicon; not downloaded automatically). See routing choices.
Using Claude Code, Codex and DeepSeek together used to mean switching between terminals and copying messages across. Close a window and the context is gone; step away and the work stops.
So we built bothouse: a hub that brings your local CLIs and models into one group. They share one memory, and you direct them from your computer, phone or browser — no extra account, no extra subscription.
Once it works for one person, we grow it in two directions.
Bring every teammate's Claude Code, Codex, Gemini and DeepSeek into one team group, and the team shares one set of AI know-how.
bothouse-iot connects small ESP32 round-screen boards. Each board is a role: talk to it, the role answers, and the dial face changes with it. See Hardware below.
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, the background service and the DSH channel are in Getting started.
| You want | How bothouse helps |
|---|---|
| An AI team of your own | Bring the Claude Code, Codex, Gemini CLI or OpenCode you already signed in to; every role gets its own name, persona and session. |
| A team from one account | Only one Codex or DeepSeek account? Create several members anyway, each with its own name, persona, job and session; they assign and hand back work by mentioning each other. |
| Find it in the chat apps you use | @ it in Discord, Feishu, QQ, the self-hosted web chat or DSH web; Discord and Feishu already have phone apps, so you can hand out work from bed. |
| Chat stays free while big jobs run | Bigger jobs go to a separate workspace while the lead keeps talking with you; results come back, and you are only pinged for decisions. |
| Everyone remembers the same thing | All roles read and write one shared memory, so whoever picks up the job already knows the background. |
| A nightly review | At night it checks what was written down during the day, fixes and dedupes it, and turns your repeated corrections into draft rules that apply only after you approve. |
| Long jobs stay on track | Every handoff carries your original words; a second AI with a clean context checks the result; “fixed” needs evidence. |
| Manage it from your phone | A built-in web dashboard shows who is busy and how much quota is used, lets you edit personas, open a project and add a note to work that is already running. |
| Draw a picture when you ask for one | Optional and off by default: point [image_gen] at an OpenAI-compatible image service and the dashboard's 生图 page draws one picture into a local file. It never posts it for you — bothouse send --image is a separate, deliberate step. |
Model and reasoning selections are scoped to the current channel/session key.
Use /model and /reasoning in that channel, or let the agent use
cc-connect model list --json followed by model set <exact-id> --effort <level>.
CLI changes are queued until the next turn; the conversation is preserved.
Selections survive restarts and /new, while other channels retain their own
selections or project/directory defaults. CLI support and pinned model arguments
still determine which settings a backend can apply.
Every role has its own avatar and persona. They come in packs — pick one and it is ready to work; to make your own, see role packs (Chinese).
Top row: real channel footage. Bottom row: the author's own dashboard.
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. See dispatcher and team memory (Chinese).