deepcoldy/botmux: README-based editorial guide

deepcoldy/botmux describes itself in the README as "Bridge Feishu/Lark to AI coding CLIs , Claude Code, Codex, Gemini, OpenCode… every DM, group or topic spawns its own live-streaming CLI session". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "botmux", the README says: Daemon 监听飞书消息，为每个新会话自动 spawn 一个独立的会话进程，把 AI 编程 CLI / Agent 的输出实时流式回传成飞书卡片，并提供可交互的 Web 终端。它不重造 Agent 能力，而是直接桥接你已经在用的工具（20+ CLI / Agent 适配器，见 支持的 CLI / Agent）。. That establishes the project's stated boundary, not a production test.

The README's "它解决什么" section gives a useful starting point for deciding whether the project fits: CLI 不感知飞书上下文 , 把机器人拉进话题群 / oncall 群，@ 一句就在你本机的代码库里开跑；会话可以用 /relay 原样搬到另一个群，上下文一点不丢。. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Agent 收不到通知、手机控不了 , CLI 跑在开发机上，人在手机上。botmux 把每轮输出推成飞书卡片，随时随地查看 / 追问 / 打断，还能开可写 Web 终端直接操作。. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "5 分钟接入". The source evidence includes: 然后私聊机器人、或 botmux dashboard 拉个群，直接开聊。完整步骤（含 Lark 国际版、--no-open-platform-auto 后手动配置权限 / 发版、排查）见 5 分钟快速接入。. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: npm install -g botmux # 需要 Node >= 22 botmux setup # 一次扫码建应用 → 选 CLI → 选工作目录（自动配权限 + 发版） botmux start # 启动 daemon（botmux autostart enable 设开机自启） When the README contains no runnable command, this article does not invent one. Open its "它解决什么" section and confirm system dependencies, default ports, and first-run initialization before using a public server.