Spawn Claude Code and Codex inside Feishu chat threads
Why wrap an SDK when you can pipe a real CLI into Feishu? Each chat thread gets its own persistent terminal session.

What it does
A daemon listens to Feishu (Lark) messages and launches independent CLI processes for each conversation thread. It supports eight AI coding agents—including Claude Code, Codex, Gemini, and OpenCode—rendering their terminal output as real-time streaming cards inside chat. Each session runs in its own tmux pane, complete with an interactive web terminal and mobile-friendly controls.
The interesting bit
Instead of reimplementing agent capabilities via SDK, the project literally spawns the CLI binary and pipes the PTY output back to Feishu cards. This means memory, tool use, plan mode, and / commands come for free, and every upstream CLI improvement arrives without a single line of adapter code. It also supports multi-bot orchestration: one “conductor” bot can split a task across topics, dispatch a coder and a reviewer in parallel, and track progress on a shared Feishu task board.
Key highlights
- Real-time Feishu cards rendered from headless xterm screenshots, with fold/unfold and scroll controls
- Interactive web terminal (read-only or writable) that syncs bidirectionally with local tmux sessions
- Daemon restarts don’t kill CLI sessions; workers re-attach to existing tmux panes automatically
- Multi-bot collaboration with @mention routing and parallel topic dispatch for coder/reviewer workflows
- Natural-language scheduling (
每日17:50) and built-in CLI tools (botmux send,botmux history) injected into each session’s PATH
Caveats
- Permission boundaries between “own” and external bots are strict: operate-level commands require explicit
allowedUsersgrants - Sub-bots must already be present in the target group with the correct Feishu permissions before orchestration works
- Primary documentation is in Chinese; the English README exists but the linked deep docs are Chinese-centric
Verdict
Teams already living in Feishu/Lark and running AI coding agents locally should look here; if you don’t use Feishu or prefer cloud-hosted chat UIs, this is not your bridge.
Frequently asked
- What is deepcoldy/botmux?
- Why wrap an SDK when you can pipe a real CLI into Feishu? Each chat thread gets its own persistent terminal session.
- Is botmux open source?
- Yes — deepcoldy/botmux is open source, released under the MIT license.
- What language is botmux written in?
- deepcoldy/botmux is primarily written in TypeScript.
- How popular is botmux?
- deepcoldy/botmux has 1.2k stars on GitHub and is currently holding steady.
- Where can I find botmux?
- deepcoldy/botmux is on GitHub at https://github.com/deepcoldy/botmux.