botmux 2.49.0-canary.1 → 2.50.0

package/README.en.md

@@ -62,7 +62,8 @@ Compared to OpenClaw-style approaches built on Agent SDKs:
 ## Prerequisites
 
 - **Node.js** >= 20
-- **AI coding CLI** installed and authenticated (`claude`, `codex`, `cursor-agent`, `gemini`, `opencode`, or `agy` (Antigravity) in PATH)
+- **AI coding CLI / local agent app** installed and authenticated (`claude`, `codex`, `coco`, `cursor-agent`, `gemini`, `opencode`, `hermes`, or `agy` (Antigravity) in PATH)
+  - **CoCo requires `0.120.32+`**: type-ahead (sending a new message while a turn is still running, parked in CoCo's own message queue) relies on 0.120.32+ behavior; earlier versions may drop or serialize input while busy — upgrade before use
 - **tmux** >= 3.x (optional — auto-enabled when installed for persistent CLI sessions)
 - **CJK fonts** (only needed for screenshot rendering of Chinese text / emoji):
   - macOS: ships with PingFang / Hiragino, no action needed
@@ -71,43 +72,46 @@ Compared to OpenClaw-style approaches built on Agent SDKs:
 
 ## 5-Minute Setup
 
-> 💡 **TL;DR**: run `botmux setup` and pick "scan-to-create" to finish Steps 1+2 in one shot (the official `@larksuiteoapi/node-sdk` device flow gives you the AppID/AppSecret). PersonalAgent apps come with event subscriptions and bot capability pre-configured, so only Step 4 (permissions) + Step 5 (optional redirect URL) + Step 6 (publish) require browser clicks; the setup wizard writes a JSON file with a one-line clipboard copy command and prints deep-links to each remaining step.
+> 💡 **TL;DR**: `npm i -g botmux` → `botmux setup` and **scan two QR codes** to get a working bot → `botmux start`. The 1st scan creates the app and saves the AppID/AppSecret (event subscriptions + bot capability pre-configured); the 2nd scan lets botmux's built-in Feishu Web login **import permissions, configure the redirect URL, and create + submit a publish version automatically**. Steps 4 (permissions) / 5 (redirect) / 6 (publish) below are all done automatically by setup and folded as a manual fallback; pass `--no-open-platform-auto` to skip the second auto-config step.
 
-### Step 1: Create a Lark App
+### Step 1: Install botmux
 
-**Recommended**: `botmux setup` → pick "1) Scan-to-create app". Scan with the Lark mobile app and the AppID/AppSecret are persisted automatically; no manual browser navigation. Falls back to manual paste on cancel/timeout/network error.
+```bash
+npm install -g botmux
+```
 
-> ⚠️ **Currently only Feishu (feishu.cn) tenants are supported.** If scan detects a Lark international (larksuite.com) tenant, setup aborts — the daemon runtime (Lark Client/WSClient/event-dispatcher) hasn't been wired up for the `larksuite.com` domain yet, so accepting Lark credentials would land users in a half-working state. A follow-up PR will add full Lark support.
+> Requires **Node.js ≥ 20**, with at least one AI coding CLI installed and authenticated (`claude` / `codex` / `cursor-agent` / `gemini` / `opencode` / `coco` / `agy` on your PATH). Installing **tmux** too is recommended (enables session persistence automatically).
 
-**Manual**: go to the [Lark Open Platform](https://open.larkoffice.com/app) and click "Create Custom App".
+### Step 2: Create the App & Configure (`botmux setup`)
 
-![Create App](docs/setup/create-app.png)
+Run `botmux setup` and follow the interactive menu:
 
-### Step 2: Get Credentials
+1. **New config**: type `1` and press Enter (with an existing config, type `2` to add a bot).
+2. **Create the bot**:
+   - Type `1` → **Scan-to-create (recommended)**: scan with the Lark mobile app and a PersonalAgent app is created with AppID/AppSecret persisted automatically, **with event subscriptions + bot capability pre-configured** — no manual browser navigation. Uses the official `@larksuiteoapi/node-sdk` device flow.
+   - Type `2` → **Manual**: go to the [Lark Open Platform](https://open.larkoffice.com/app), create a "Custom App", copy **App ID / App Secret** from "Credentials & Basic Info", and paste them back.
+3. **Pick the CLI**: choose the CLI to bridge (e.g. type `1` for Claude Code).
+4. **Default working dir**: usually the **parent directory** of your git projects (e.g. `~/projects`); new topics scan **downward** for git repos (up to 3 levels). Avoid `~` (too many folders to traverse).
 
-> The scan-to-create path completes this step automatically; skip to Step 3.
+> ⚠️ **Currently only Feishu (feishu.cn) tenants are supported.** If scan detects a Lark international (larksuite.com) tenant, setup aborts — the daemon runtime (Lark Client/WSClient/event-dispatcher) hasn't been wired up for the `larksuite.com` domain yet. A follow-up PR will add full Lark support.
 
-Open the app details page → "Credentials & Basic Info", and copy the **App ID** and **App Secret**.
+At the end, setup validates credentials with a `tenant_access_token` call (only writing `bots.json` on success), writes the full scope JSON to `~/.botmux/lark-scopes.json`, and prints a one-line clipboard copy command plus deep-links to each remaining step.
 
-![Get Credentials](docs/setup/credentials.png)
+![Create App](docs/setup/create-app.png)
 
-### Step 3: Install & Start botmux
+### Step 3: Start
 
 ```bash
-# Install
-npm install -g botmux
-
-# Interactive setup — pick "1) Scan-to-create app" or "2) Paste AppID/Secret manually".
-# Credentials are validated with a tenant_access_token call before bots.json is written.
-# At the end of setup the wizard writes the full scope JSON to ~/.botmux/lark-scopes.json
-# and prints a one-line clipboard copy command for your platform.
-botmux setup
-
-# Start (if you ever need to verify the event subscription, Lark requires the daemon to be running so it can detect the WebSocket connection)
-# Re-validates credentials before forking workers; missing scopes only WARN, do not block the daemon.
 botmux start
 ```
 
+> `start` re-validates credentials before forking workers; missing scopes only WARN, they don't block the daemon. If you later need to verify the event subscription, Lark requires the daemon to be running so it can detect the WebSocket connection.
+
+<details>
+<summary><b>Manual Open Platform config: permissions / redirect / publish (fallback)</b> —— botmux setup does these automatically (during the 2nd scan); expand only if auto-config failed or you want to verify manually</summary>
+
+<br>
+
 ### Step 4: Add Permissions
 
 Run the copy-to-clipboard command setup printed, then go to "Permissions & Scopes" → "Batch Import/Export" and paste. Submit for review — visibility "only me" auto-approves.
@@ -145,6 +149,8 @@ Go to "Version Management & Release", click "Create Version" and publish. Set av
 
 ![Publish](docs/setup/publish.png)
 
+</details>
+
 ### Step 7: Create a Group and Start Chatting
 
 1. Create a **topic-enabled group** in Lark
@@ -306,9 +312,9 @@ Send these straight into a topic — the daemon intercepts them (no clash with t
 
 | Command | Description |
 |---------|-------------|
-| `/repo` | Show project selector card (interactive dropdown + text list) |
+| `/repo` | While a repo is pending selection, launch in the default workingDir; mid-session, show the project selector card (interactive dropdown + text list) |
 | `/repo <N>` | Switch to Nth project from last scan |
-| `/skip` | Skip the repo selector card, start the session in the default dir |
+| `/repo <path\|name>` | Skip the selector card; pass a path (relative/absolute) or a first-level project name under workingDir |
 | `/cd <path>` | Change working directory and restart the CLI process |
 | `/status` | Show session info (uptime, terminal URL, etc.) |
 | `/restart` | Restart CLI process (keeps the session context) |
@@ -355,8 +361,8 @@ Send these straight into a topic — the daemon intercepts them (no clash with t
 
 | Command | Description |
 |---------|-------------|
-| `@bot /grant @someone` | Pop an authorization card to add the user to the "this chat" or "global" allowlist; also auto-pops (and @s the owner) when an unauthorized user @-mentions the bot |
-| `@bot /revoke @someone` | Revoke the user's this-chat + global access |
+| `@bot /grant @someone` | Pop an authorization card to add the user to the "this chat" or "global" allowlist; you can @ several people/bots at once (one card lists every target, one scope click applies to all); if a granted target is a bot, it's auto-registered into the roster on success (an implicit `/introduce`) for cross-bot collaboration; also auto-pops (and @s the owner) when an unauthorized user @-mentions the bot |
+| `@bot /revoke @someone` | Revoke the user's this-chat + global access; you can @ several people/bots at once |
 
 **🆕 One-shot session group**
 
@@ -369,7 +375,7 @@ Send these straight into a topic — the daemon intercepts them (no clash with t
 | Command | Description |
 |---------|-------------|
 | `@botA @botB /t <prompt>` | With multiple bots, each @-mentioned bot opens its own independent topic from the same message |
-| `@botA @botB /introduce` | Bots register each other's open_id so they can later explicitly @-mention one another across sessions (any @ order, extra text allowed) |
+| `@botA @botB /introduce` | Bots register each other's open_id so they can later explicitly @-mention one another across sessions (any @ order, extra text allowed; roster-only, grants no permission — **anyone in the chat can run it, no authorization needed**) |
 
 **❓ Help**
 
@@ -414,7 +420,7 @@ Configure bots via `~/.botmux/bots.json`. Run `botmux setup` to create it intera
 botmux setup
 ```
 
-When `~/.botmux/bots.json` already exists, `botmux setup` can add a bot, reconfigure from scratch, edit an existing bot, or delete a bot config. The edit/delete flow accepts the process name shown by `botmux status` (e.g. `botmux-1` or a custom `botmux-claude-main`) or the `larkAppId`; empty input keeps the current value, and `-` clears optional fields such as `name`, `backendType`, `workingDir`, and `allowedUsers`. Changing `larkAppId` asks for confirmation because historical session/chat state under the old app ID is not migrated automatically. Deleting a bot only removes one local `bots.json` entry; it does not delete the Lark app, historical messages, or local session data. Run `botmux restart` for changes to take effect.
+When `~/.botmux/bots.json` already exists, `botmux setup` can add a bot, reconfigure from scratch, edit an existing bot, or delete a bot config. The edit/delete flow accepts the process name shown by `botmux status` (e.g. `botmux-1` or a custom `botmux-claude-main`) or the `larkAppId`; empty input keeps the current value, and `-` clears optional fields such as `name`, `model`, `backendType`, `workingDir`, and `allowedUsers`. Changing `larkAppId` asks for confirmation because historical session/chat state under the old app ID is not migrated automatically. Deleting a bot only removes one local `bots.json` entry; it does not delete the Lark app, historical messages, or local session data. Run `botmux restart` for changes to take effect.
 
 **bots.json format:**
 
@@ -425,7 +431,7 @@ When `~/.botmux/bots.json` already exists, `botmux setup` can add a bot, reconfi
     "larkAppSecret": "secret_1",
     "name": "claude-main",
     "cliId": "claude-code",
-    "disableCliBypass": true,
+    "model": "sonnet",
     "workingDir": "~/projects",
     "allowedUsers": ["alice@company.com"],
     "allowedChatGroups": ["oc_xxx_team"]
@@ -434,6 +440,7 @@ When `~/.botmux/bots.json` already exists, `botmux setup` can add a bot, reconfi
     "larkAppId": "cli_xxx_bot2",
     "larkAppSecret": "secret_2",
     "cliId": "codex",
+    "model": "gpt-5-codex",
     "workingDir": "~/work"
   }
 ]
@@ -444,14 +451,15 @@ When `~/.botmux/bots.json` already exists, `botmux setup` can add a bot, reconfi
 | `larkAppId` | Yes | Lark app ID |
 | `larkAppSecret` | Yes | Lark app secret |
 | `name` | No | Process name suffix shown by `botmux status`; e.g. `claude-main` appears as `botmux-claude-main`, defaults to `botmux-<index>` |
-| `cliId` | No | CLI adapter, defaults to `claude-code` (options: `aiden`, `coco`, `codex`, `cursor`, `gemini`, `opencode`, `antigravity`) |
+| `cliId` | No | CLI adapter, defaults to `claude-code` (options: `aiden`, `coco`, `codex`, `codex-app`, `cursor`, `gemini`, `opencode`, `antigravity`, `hermes`) |
+| `model` | No | Model name used when spawning the CLI. Currently honored by: `claude-code`, `codex`, `coco`, `cursor`, `gemini`, `opencode`; other adapters ignore the field. Leave empty to use the CLI default. `botmux setup` proposes per-CLI candidates plus a free-form Other option. |
 | `cliPathOverride` | No | Absolute path to the CLI entry, for wrappers / routers; typical use: `ccr`, `claude-w`, `aiden-x-claude`, etc. |
-| `disableCliBypass` | No | Whether to disable botmux's default CLI bypass / weak-sandbox flag injection. Missing or `false` keeps the legacy behavior: botmux still adds flags such as `--yolo`, `--dangerously-*`, `--force`, or `--permission-mode agentFull`. When `true`, botmux stops adding those flags |
 | `backendType` | No | Session backend: `pty` or `tmux` (auto-detected by default) |
 | `workingDir` | No | Default working directory, supports comma-separated. The new-topic repo-select card scans for git repos **from this directory downward** (recursive, up to 3 levels), no longer climbing to the parent: point it at a repos root (e.g. `~/projects`) to list every repo beneath it, or at a single repo to list just that repo (and its linked worktrees) |
 | `defaultWorkingDir` | No | Single-repo default: new topics with no oncall binding and no peer-session inheritance spawn directly here, skipping the repo-select card. `/cd <path>` still switches mid-session; the next new topic falls back to this default. **Difference from `defaultOncall`:** does NOT write `oncallChats` and does NOT change the `canTalk` / `canOperate` permission model |
 | `allowedUsers` | No | Allowed users (**full emails** like `alice@example.com`, or open_ids `ou_xxx`). Email prefixes can't be resolved and are dropped. Required (at least one entry, as owner) when `allowedChatGroups` is set |
 | `allowedChatGroups` | No | Talk-open chats (`chat_id`, for example `oc_xxx`). Any member talking **inside these chats** can use the bot (decided by the message's chat — new members work immediately, removed members lose access, no restart needed); grants `canTalk` only, sensitive ops still require `allowedUsers`. Equivalent to the owner running `/grant` (no target) in that chat. |
+| `globalGrants` | No | Global talk allowlist (`open_id` list, e.g. `ou_xxx`; humans or bots). Listed entries can talk to the bot in **any** chat; grants `canTalk` only, sensitive ops still require `allowedUsers`. Usually written via the owner's `/grant` card (the "grant talk globally" button); can also be set manually here. |
 | `oncallChats` | No | Oncall bindings (written by `/oncall bind`), e.g. `[{ "chatId": "oc_xxx", "workingDir": "~/projects/foo" }]`; any group member can @ the bot |
 
 **Config priority:** `BOTS_CONFIG` env var > `~/.botmux/bots.json`

package/README.md

@@ -169,7 +169,8 @@ CLI 进入 botmux 会话时自动获得 `~/.botmux/bin` 在 PATH 中，以及一
 ## 前置要求
 
 - **Node.js** >= 20
-- **AI 编程 CLI** 已安装并完成认证（`claude`、`codex`、`cursor-agent`、`gemini`、`opencode` 或 `agy`（Antigravity）在 PATH 中）
+- **AI 编程 CLI / 本地 Agent 应用** 已安装并完成认证（`claude`、`codex`、`coco`、`cursor-agent`、`gemini`、`opencode`、`hermes` 或 `agy`（Antigravity）在 PATH 中）
+  - **CoCo 最低版本 `0.120.32`**：type-ahead（会话忙时即可发新消息，由 CoCo 自己的消息队列接住）依赖 0.120.32+ 的行为；更早版本忙时输入可能丢失或串行，请升级后再用
 - **tmux** >= 3.x（可选，安装后自动启用会话常驻）
 - **CJK 字体**（用于截图渲染中文/emoji）：
   - macOS 自带 PingFang/Hiragino，无需配置
@@ -178,42 +179,46 @@ CLI 进入 botmux 会话时自动获得 `~/.botmux/bin` 在 PATH 中，以及一
 
 ## 5 分钟快速接入
 
-> 💡 **TL;DR**：跑 `botmux setup` 选「扫码建应用」一步完成 Step 1+2（拿 AppID/AppSecret）。PersonalAgent 应用建出来时事件订阅和 bot 能力都已默认配好，只剩 Step 4 权限申请 + Step 5（按需）重定向 URL + Step 6 发版三步要在浏览器手动点；setup 完成后会自动写 JSON 文件 + 打印一键复制命令 + 各步骤的深链。
+> 💡 **TL;DR**：`npm i -g botmux` → `botmux setup`，**扫两次码**就能建好一个可用机器人 → `botmux start`。第 1 次扫码建应用、拿到 AppID/AppSecret（事件订阅 + bot 能力默认已配好）；第 2 次扫码让 botmux 内置的飞书 Web 登录**自动导入权限、配置重定向 URL、创建并提交发布版本**。下面的 Step 4 权限 / Step 5 重定向 / Step 6 发版都已由 setup 默认自动完成、折叠为手动备用；加 `--no-open-platform-auto` 可跳过第二次自动配置、改走手动。
 
-### Step 1: 创建飞书应用
+### Step 1: 安装 botmux
 
-**推荐路径**：`botmux setup` 选「1) 扫码建应用」，飞书扫码完成后自动落盘 AppID/AppSecret，无需手动浏览器创建。底层走 `@larksuiteoapi/node-sdk` 的官方 device flow。
+```bash
+npm install -g botmux
+```
 
-> ⚠️ **目前仅支持飞书 (feishu.cn) 租户**。扫码检测到 Lark 国际版 (larksuite.com) 会中止 setup —— daemon runtime (Lark Client/WSClient/event-dispatcher 等) 需要一并接入 lark 域，会在单独 PR 跟进。
+> 要求 **Node.js ≥ 20**，且本地已装好并登录至少一种 AI 编程 CLI（`claude` / `codex` / `cursor-agent` / `gemini` / `opencode` / `coco` / `agy` 等在 PATH 中）。推荐顺手装 **tmux**（装了自动启用会话常驻）。
 
-**手动路径**：打开 [飞书开放平台](https://open.larkoffice.com/app)，点击「创建企业自建应用」。
+### Step 2: 创建应用并配置（`botmux setup`）
 
-![创建应用](docs/setup/create-app.png)
+跑 `botmux setup`，按交互菜单一步步选：
 
-### Step 2: 获取凭证
+1. **新建配置**：输入 `1` 回车（已有配置时输入 `2` 添加机器人）。
+2. **创建机器人**：
+   - 输入 `1` → **扫码创建（推荐）**：飞书扫码完成后自动建出 PersonalAgent 应用并落盘 AppID/AppSecret，**事件订阅 + bot 能力默认已配好**，无需手动浏览器创建。底层走 `@larksuiteoapi/node-sdk` 官方 device flow。
+   - 输入 `2` → **手动创建**：去 [飞书开放平台](https://open.larkoffice.com/app) 建「企业自建应用」，在「凭证与基础信息」复制 **App ID / App Secret** 回来粘贴。
+3. **选择 CLI**：选本次要接入的 CLI（如接 Claude Code 就选 `1`）。
+4. **默认工作目录**：通常填 git 项目的**父级目录**（如 `~/projects`），新话题会从该目录**向下**查找 git 仓库（最多 3 层）；尽量别填 `~`（要遍历太多文件夹）。
 
-> 扫码路径自动完成此步，可直接跳到 Step 3。
+> ⚠️ **目前仅支持飞书 (feishu.cn) 租户**。扫码检测到 Lark 国际版 (larksuite.com) 会中止 setup —— daemon runtime (Lark Client/WSClient/event-dispatcher 等) 需要一并接入 lark 域，会在单独 PR 跟进。
 
-进入应用详情 →「凭证与基础信息」，复制 **App ID** 和 **App Secret**。
+setup 末尾会用 `tenant_access_token` 校验凭证（通过才落盘 `bots.json`），并把完整权限 JSON 写到 `~/.botmux/lark-scopes.json` + 打印一键复制命令 + 各步骤深链。
 
-![获取凭证](docs/setup/credentials.png)
+![扫码建应用](docs/setup/create-app.png)
 
-### Step 3: 安装 & 启动 botmux
+### Step 3: 启动
 
 ```bash
-# 安装
-npm install -g botmux
-
-# 交互式配置 — 选「1) 扫码建应用」或「2) 手动粘 AppID/Secret」
-# 凭证拿到后自动取一次 tenant_access_token 校验，通过才落盘 bots.json
-# setup 末尾会把完整权限 JSON 写到 ~/.botmux/lark-scopes.json 并打印一键复制命令
-botmux setup
-
-# 启动（如果之后需要确认事件订阅，飞书后台会要求 daemon 已在跑才能识别长连接）
-# start 前再校验一次凭证；权限未配齐不会阻塞 daemon，只 WARN
 botmux start
 ```
 
+> start 前再校验一次凭证；权限未配齐不会阻塞 daemon，只 WARN。如果之后需要确认事件订阅，飞书后台会要求 daemon 已在跑才能识别长连接。
+
+<details>
+<summary><b>手动配置开放平台：权限 / 重定向 / 发版（备用）</b> —— 这三步 botmux setup 默认已自动完成（扫第二次码时），仅在自动配置失败、或想手动核对时展开</summary>
+
+<br>
+
 ### Step 4: 添加权限
 
 setup 完成后，按 terminal 提示的一键复制命令把权限 JSON 复制到剪贴板，进入「权限管理」→「批量导入/导出权限」粘贴 → 提交审批。可用性范围选「仅自己可见」会自动通过：
@@ -251,6 +256,8 @@ http://127.0.0.1:9768/callback
 
 ![发版](docs/setup/publish.png)
 
+</details>
+
 ### Step 7: 建群开聊
 
 1. 飞书中创建一个**话题群**
@@ -300,9 +307,9 @@ botmux autostart enable
 
 | 命令 | 说明 |
 |------|------|
-| `/repo` | 显示项目选择卡片（交互式下拉 + 文本列表） |
+| `/repo` | 仓库待选时直接用默认 workingDir 启动会话；会话进行中则弹出项目选择卡片（交互式下拉 + 文本列表） |
 | `/repo <N>` | 切换到上次扫描的第 N 个项目 |
-| `/skip` | 跳过仓库选择卡片，直接用默认目录开启会话 |
+| `/repo <路径\|项目名>` | 跳过选择卡片，直接指定路径（相对/绝对）或 workingDir 下的一级项目名 |
 | `/cd <路径>` | 切换工作目录并重启 CLI 进程 |
 | `/status` | 查看会话信息（运行时间、终端地址等） |
 | `/restart` | 重启 CLI 进程（保留 session 上下文） |
@@ -349,8 +356,8 @@ botmux autostart enable
 
 | 命令 | 说明 |
 |------|------|
-| `@机器人 /grant @某人` | 弹授权卡片，把对方加进「本群使用」或「全局」白名单；无权限者 @ 机器人时也会自动弹这张卡并 @owner |
-| `@机器人 /revoke @某人` | 撤销对方的本群 + 全局授权 |
+| `@机器人 /grant @某人` | 弹授权卡片，把对方加进「本群使用」或「全局」白名单；可一次 @ 多人/多 bot（一张卡列出全部目标、点一次范围对全部生效）；被授权的若是 bot，授权成功后会自动登记进花名册（等于顺带 `/introduce` 一次）便于跨 bot 协作；无权限者 @ 机器人时也会自动弹这张卡并 @owner |
+| `@机器人 /revoke @某人` | 撤销对方的本群 + 全局授权；可一次 @ 多人/多 bot |
 
 **🆕 一键新建会话群**
 
@@ -363,7 +370,7 @@ botmux autostart enable
 | 命令 | 说明 |
 |------|------|
 | `@botA @botB /t <prompt>` | 多机器人时，让每个被 @ 的机器人在同一条消息上各自独立开新话题 |
-| `@botA @botB /introduce` | 互相登记彼此的 open_id，便于后续跨 bot 显式 @mention 协作（@ 顺序任意，可带额外文本） |
+| `@botA @botB /introduce` | 互相登记彼此的 open_id，便于后续跨 bot 显式 @mention 协作（@ 顺序任意，可带额外文本；只记花名册、不授予任何权限，**群内任何人都可用、无需授权**） |
 
 **❓ 帮助**
 
@@ -518,7 +525,7 @@ dashboard 走单独 pm2 进程 `botmux-dashboard`，跟着 `pnpm daemon:restart`
 botmux setup
 ```
 
-已有 `~/.botmux/bots.json` 时，`botmux setup` 支持添加新机器人、重新配置、编辑现有机器人，以及删除机器人配置。编辑或删除时用 `botmux status` 里的进程名（如 `botmux-1` 或自定义的 `botmux-claude-main`）或 `larkAppId` 选择目标；字段留空表示保留当前值，`name`、`cliPathOverride`、`backendType`、`workingDir`、`allowedUsers` 等可选字段输入 `-` 表示清空。修改 `larkAppId` 会提示确认，因为旧 appId 下的历史会话和群聊状态数据不会自动迁移。删除机器人只移除本机 `bots.json` 中的一项，不删除飞书开放平台应用、历史消息或本地会话数据；修改完成后运行 `botmux restart` 生效。
+已有 `~/.botmux/bots.json` 时，`botmux setup` 支持添加新机器人、重新配置、编辑现有机器人，以及删除机器人配置。编辑或删除时用 `botmux status` 里的进程名（如 `botmux-1` 或自定义的 `botmux-claude-main`）或 `larkAppId` 选择目标；字段留空表示保留当前值，`name`、`model`、`cliPathOverride`、`backendType`、`workingDir`、`allowedUsers` 等可选字段输入 `-` 表示清空。修改 `larkAppId` 会提示确认，因为旧 appId 下的历史会话和群聊状态数据不会自动迁移。删除机器人只移除本机 `bots.json` 中的一项，不删除飞书开放平台应用、历史消息或本地会话数据；修改完成后运行 `botmux restart` 生效。
 
 **bots.json 格式：**
 
@@ -529,7 +536,7 @@ botmux setup
     "larkAppSecret": "secret_1",
     "name": "claude-main",
     "cliId": "claude-code",
-    "disableCliBypass": true,
+    "model": "sonnet",
     "workingDir": "~/projects",
     "allowedUsers": ["alice@company.com"],
     "allowedChatGroups": ["oc_xxx_team"]
@@ -538,6 +545,7 @@ botmux setup
     "larkAppId": "cli_xxx_bot2",
     "larkAppSecret": "secret_2",
     "cliId": "codex",
+    "model": "gpt-5-codex",
     "workingDir": "~/work"
   }
 ]
@@ -548,14 +556,15 @@ botmux setup
 | `larkAppId` | 是 | 飞书应用 App ID |
 | `larkAppSecret` | 是 | 飞书应用 App Secret |
 | `name` | 否 | `botmux status` 中的进程名后缀；例如 `claude-main` 会显示为 `botmux-claude-main`，留空默认 `botmux-<序号>` |
-| `cliId` | 否 | CLI 适配器，默认 `claude-code`（可选：`aiden`、`coco`、`codex`、`cursor`、`gemini`、`opencode`、`antigravity`） |
+| `cliId` | 否 | CLI 适配器，默认 `claude-code`（可选：`aiden`、`coco`、`codex`、`codex-app`、`cursor`、`gemini`、`opencode`、`antigravity`、`hermes`） |
+| `model` | 否 | 启动 CLI 时使用的模型名；留空走 CLI 默认。当前会注入到支持模型参数的适配器：`claude-code` / `codex` / `coco` / `cursor` / `gemini` / `opencode`；其它适配器会忽略该字段 |
 | `cliPathOverride` | 否 | CLI 入口的绝对路径，用于套 wrapper / router；典型场景：ccr、claude-w、aiden-x-claude 等自定义入口 |
-| `disableCliBypass` | 否 | 是否禁用 botmux 默认注入的 CLI bypass / 弱沙箱参数。未配置或 `false` 时保持兼容旧逻辑，botmux 会继续添加 `--yolo`、`--dangerously-*`、`--force`、`--permission-mode agentFull` 等参数；设为 `true` 时不再自动添加这些参数 |
 | `backendType` | 否 | 会话后端：`pty` 或 `tmux`（默认自动检测） |
 | `workingDir` | 否 | 默认工作目录，支持逗号分隔多个目录。新话题的 repo 选择卡片会**从该目录自身向下**递归查找 git 仓库（最多 3 层），不再向上扫父目录：指向仓库集合根目录（如 `~/projects`）即列出其下所有仓库，指向单个仓库则只列该仓库（及其 linked worktrees） |
 | `defaultWorkingDir` | 否 | 单仓库默认目录：新话题在无 oncall 绑定 / 无同群兄弟 session 时直接进入该目录，跳过 repo 选择卡片。`/cd <path>` 仍可临时切换；下一个新话题回到该默认值。**与 `defaultOncall` 的区别**：不写 `oncallChats`、不修改 `canTalk`/`canOperate` 权限模型 |
 | `allowedUsers` | 否 | 允许的用户列表（**完整邮箱**如 `alice@example.com`，或 open_id `ou_xxx`）。邮箱前缀无法解析、会被丢弃。配置了 `allowedChatGroups` 时此项必须至少有一个条目作为 owner |
 | `allowedChatGroups` | 否 | 可对话群列表（飞书 `chat_id`，如 `oc_xxx`）。**在这些群里**任何成员都能与机器人对话（按消息所在群判断，新人进群即生效、退群即失权，无需重启）；仅授对话权（`canTalk`），敏感操作仍由 `allowedUsers` 控制。等价于 owner 在该群发 `/grant`（不带 @）。 |
+| `globalGrants` | 否 | 全局可对话名单（`open_id` 列表，如 `ou_xxx`；人或 bot 均可）。名单内的对象可在**任意群**与机器人对话；仅授对话权（`canTalk`），敏感操作仍由 `allowedUsers` 控制。通常由 owner 在授权卡上点「全局授权对话」写入，也可在此手动配置。 |
 | `oncallChats` | 否 | oncall 绑定（`/oncall bind` 写入），形如 `[{ "chatId": "oc_xxx", "workingDir": "~/projects/foo" }]`，群内任何成员可 @ 提问 |
 
 **配置优先级：** `BOTS_CONFIG` 环境变量 → `~/.botmux/bots.json`

package/dist/adapters/adopt-route.d.ts

@@ -0,0 +1,63 @@
+/**
+ * adopt-route.ts
+ *
+ * 为没有 BOTMUX_* 环境变量的"孤立" Claude 进程（即通过 /adopt 接管的外部 CLI）
+ * 提供 askUserQuestion hook 的路由解析逻辑。
+ *
+ * 通过以下步骤确定目标 Lark 会话：
+ *   1. 收集 hook 进程的祖先 PID 链
+ *   2. 遍历在线 daemon，查询每个 daemon 是否有以某祖先 PID 启动的 adopt 会话
+ *   3. 首个命中即返回路由信息
+ */
+/** 从 daemon 取回的 adopt 会话路由信息 */
+export interface AdoptRoute {
+    sessionId: string;
+    chatId: string;
+    larkAppId: string;
+    rootMessageId: string;
+}
+/**
+ * 沿进程祖先链向上收集 PID（不含 startPid 自己）。
+ *
+ * @param startPid    起始进程 PID（自身不包含在结果中）
+ * @param readParent  注入式父 PID 读取函数（默认使用 /proc 或 ps）
+ * @param maxDepth    最大深度，防止意外无限循环（默认 40）
+ * @returns           祖先 PID 数组，从最近父进程到最远祖先
+ */
+export declare function getAncestorPids(startPid: number, readParent?: (pid: number) => number | null, maxDepth?: number): number[];
+/**
+ * 查询某个 daemon 是否有以指定 PID 启动的活跃 adopt 会话。
+ *
+ * GET http://127.0.0.1:<ipcPort>/api/adopt-session/<pid>
+ *   200 → 解析 AdoptRoute；其它状态码或异常 → null（不抛）。
+ * 超时：2 秒（AbortController）。
+ */
+export declare function queryAdoptSession(ipcPort: number, pid: number): Promise<AdoptRoute | null>;
+/**
+ * 通过祖先 PID 匹配在线 adopt 会话。
+ *
+ * **并发 + 全局 budget 封顶**：候选 = daemon 列表序 × 祖先链序（由近及远）逐个编号；
+ * 全部并发查询（每请求各自带 2s 超时），整体不超过 `budgetMs`。命中按候选 index 取
+ * 最小，保持确定性。
+ *
+ * 为何要全局 budget：runHook 在缺 BOTMUX_* 时同步 await 本函数，而全局 hook 会覆盖
+ * 非 botmux 的 Claude 会话；若某 daemon still-online 但 IPC 不响应，顺序 await 会
+ * `祖先数 × 2s × daemon 数` 线性叠加（可达几十秒），把真·非 botmux 的 ask 卡死。
+ * 并发让总耗时收敛到单请求量级，budget 再封顶，保证快速 passthrough。
+ *
+ * @param deps.startPid      hook 进程自身的 PID
+ * @param deps.listDaemons   列出在线 daemon（ipcPort）
+ * @param deps.queryDaemon   查询某 daemon 是否有该 pid 的活跃 adopt 会话
+ * @param deps.getAncestors  取祖先 PID（默认使用 getAncestorPids）
+ * @param deps.budgetMs      整体耗时上限（默认 1500ms；可注入便于测试）
+ */
+export declare function resolveAdoptRoute(deps: {
+    startPid: number;
+    listDaemons: () => Array<{
+        ipcPort: number;
+    }>;
+    queryDaemon: (ipcPort: number, pid: number) => Promise<AdoptRoute | null>;
+    getAncestors?: (startPid: number) => number[];
+    budgetMs?: number;
+}): Promise<AdoptRoute | null>;
+//# sourceMappingURL=adopt-route.d.ts.map

package/dist/adapters/adopt-route.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"adopt-route.d.ts","sourceRoot":"","sources":["../../src/adapters/adopt-route.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAOH,gCAAgC;AAChC,MAAM,WAAW,UAAU;IACzB,SAAS,EAAE,MAAM,CAAC;IAClB,MAAM,EAAE,MAAM,CAAC;IACf,SAAS,EAAE,MAAM,CAAC;IAClB,aAAa,EAAE,MAAM,CAAC;CACvB;AA8CD;;;;;;;GAOG;AACH,wBAAgB,eAAe,CAC7B,QAAQ,EAAE,MAAM,EAChB,UAAU,CAAC,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,MAAM,GAAG,IAAI,EAC3C,QAAQ,CAAC,EAAE,MAAM,GAChB,MAAM,EAAE,CAiBV;AAID;;;;;;GAMG;AACH,wBAAsB,iBAAiB,CACrC,OAAO,EAAE,MAAM,EACf,GAAG,EAAE,MAAM,GACV,OAAO,CAAC,UAAU,GAAG,IAAI,CAAC,CAgC5B;AAID;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAsB,iBAAiB,CAAC,IAAI,EAAE;IAC5C,QAAQ,EAAE,MAAM,CAAC;IACjB,WAAW,EAAE,MAAM,KAAK,CAAC;QAAE,OAAO,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IAC9C,WAAW,EAAE,CAAC,OAAO,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,KAAK,OAAO,CAAC,UAAU,GAAG,IAAI,CAAC,CAAC;IAC1E,YAAY,CAAC,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,MAAM,EAAE,CAAC;IAC9C,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB,GAAG,OAAO,CAAC,UAAU,GAAG,IAAI,CAAC,CA+C7B"}

package/dist/adapters/adopt-route.js

@@ -0,0 +1,195 @@
+/**
+ * adopt-route.ts
+ *
+ * 为没有 BOTMUX_* 环境变量的"孤立" Claude 进程（即通过 /adopt 接管的外部 CLI）
+ * 提供 askUserQuestion hook 的路由解析逻辑。
+ *
+ * 通过以下步骤确定目标 Lark 会话：
+ *   1. 收集 hook 进程的祖先 PID 链
+ *   2. 遍历在线 daemon，查询每个 daemon 是否有以某祖先 PID 启动的 adopt 会话
+ *   3. 首个命中即返回路由信息
+ */
+import { execFileSync } from 'node:child_process';
+import { readFileSync } from 'node:fs';
+// ── 祖先 PID 收集 ──────────────────────────────────────────────────────────────
+/**
+ * 读取某进程的父 PID。
+ *
+ * 默认实现：
+ *   1. 优先从 /proc/<pid>/stat 读取（Linux），第 4 字段（0-based）是 ppid。
+ *      注意 stat 第 2 字段 comm 可以含括号和空格，所以从最后一个 `)` 之后的子串解析。
+ *   2. 失败时回退到 `ps -o ppid= -p <pid>`（macOS/Linux 通用）。
+ *
+ * 失败/进程不存在 → 返回 null。
+ */
+function defaultReadParent(pid) {
+    // 先尝试 /proc（Linux 最快）
+    try {
+        const stat = readFileSync(`/proc/${pid}/stat`, 'utf-8');
+        // stat 格式: "<pid> (<comm>) <state> <ppid> ..."
+        // comm 字段可能含空格和括号，取最后一个 ')' 之后的部分
+        const lastParen = stat.lastIndexOf(')');
+        if (lastParen === -1)
+            throw new Error('unexpected /proc stat format');
+        const tail = stat.slice(lastParen + 1).trim();
+        // tail: "<state> <ppid> ..."
+        const parts = tail.split(' ');
+        // parts[0] = state, parts[1] = ppid
+        const ppid = parseInt(parts[1], 10);
+        if (Number.isInteger(ppid) && ppid > 0)
+            return ppid;
+    }
+    catch {
+        // /proc 不可用或解析失败，回退到 ps
+    }
+    // 回退到 ps（macOS / 无 /proc 的 Linux）
+    try {
+        const out = execFileSync('ps', ['-o', 'ppid=', '-p', String(pid)], {
+            encoding: 'utf-8',
+        });
+        const ppid = parseInt(out.trim(), 10);
+        if (Number.isInteger(ppid) && ppid > 0)
+            return ppid;
+    }
+    catch {
+        // 进程不存在或 ps 调用失败
+    }
+    return null;
+}
+/**
+ * 沿进程祖先链向上收集 PID（不含 startPid 自己）。
+ *
+ * @param startPid    起始进程 PID（自身不包含在结果中）
+ * @param readParent  注入式父 PID 读取函数（默认使用 /proc 或 ps）
+ * @param maxDepth    最大深度，防止意外无限循环（默认 40）
+ * @returns           祖先 PID 数组，从最近父进程到最远祖先
+ */
+export function getAncestorPids(startPid, readParent, maxDepth) {
+    const reader = readParent ?? defaultReadParent;
+    const depth = maxDepth ?? 40;
+    const ancestors = [];
+    const visited = new Set([startPid]);
+    let current = startPid;
+    for (let i = 0; i < depth; i++) {
+        const parent = reader(current);
+        if (parent === null || parent <= 1)
+            break; // 到 init 或读不到，停止
+        if (visited.has(parent))
+            break; // 防环
+        visited.add(parent);
+        ancestors.push(parent);
+        current = parent;
+    }
+    return ancestors;
+}
+// ── Daemon 查询辅助 ─────────────────────────────────────────────────────────────
+/**
+ * 查询某个 daemon 是否有以指定 PID 启动的活跃 adopt 会话。
+ *
+ * GET http://127.0.0.1:<ipcPort>/api/adopt-session/<pid>
+ *   200 → 解析 AdoptRoute；其它状态码或异常 → null（不抛）。
+ * 超时：2 秒（AbortController）。
+ */
+export async function queryAdoptSession(ipcPort, pid) {
+    const controller = new AbortController();
+    const timer = setTimeout(() => controller.abort(), 2000);
+    try {
+        const res = await fetch(`http://127.0.0.1:${ipcPort}/api/adopt-session/${pid}`, { signal: controller.signal });
+        if (!res.ok)
+            return null;
+        const body = (await res.json());
+        if (!body || typeof body !== 'object')
+            return null;
+        const b = body;
+        if (typeof b.sessionId !== 'string' ||
+            typeof b.chatId !== 'string' ||
+            typeof b.larkAppId !== 'string' ||
+            typeof b.rootMessageId !== 'string') {
+            return null;
+        }
+        return {
+            sessionId: b.sessionId,
+            chatId: b.chatId,
+            larkAppId: b.larkAppId,
+            rootMessageId: b.rootMessageId,
+        };
+    }
+    catch {
+        // 超时、网络错误、JSON 解析失败等 → null
+        return null;
+    }
+    finally {
+        clearTimeout(timer);
+    }
+}
+// ── 主逻辑 ─────────────────────────────────────────────────────────────────────
+/**
+ * 通过祖先 PID 匹配在线 adopt 会话。
+ *
+ * **并发 + 全局 budget 封顶**：候选 = daemon 列表序 × 祖先链序（由近及远）逐个编号；
+ * 全部并发查询（每请求各自带 2s 超时），整体不超过 `budgetMs`。命中按候选 index 取
+ * 最小，保持确定性。
+ *
+ * 为何要全局 budget：runHook 在缺 BOTMUX_* 时同步 await 本函数，而全局 hook 会覆盖
+ * 非 botmux 的 Claude 会话；若某 daemon still-online 但 IPC 不响应，顺序 await 会
+ * `祖先数 × 2s × daemon 数` 线性叠加（可达几十秒），把真·非 botmux 的 ask 卡死。
+ * 并发让总耗时收敛到单请求量级，budget 再封顶，保证快速 passthrough。
+ *
+ * @param deps.startPid      hook 进程自身的 PID
+ * @param deps.listDaemons   列出在线 daemon（ipcPort）
+ * @param deps.queryDaemon   查询某 daemon 是否有该 pid 的活跃 adopt 会话
+ * @param deps.getAncestors  取祖先 PID（默认使用 getAncestorPids）
+ * @param deps.budgetMs      整体耗时上限（默认 1500ms；可注入便于测试）
+ */
+export async function resolveAdoptRoute(deps) {
+    const { startPid, listDaemons, queryDaemon } = deps;
+    const getAncestors = deps.getAncestors ?? ((pid) => getAncestorPids(pid));
+    const budgetMs = deps.budgetMs ?? 1500;
+    const ancestors = getAncestors(startPid);
+    if (ancestors.length === 0)
+        return null;
+    const daemons = listDaemons();
+    if (daemons.length === 0)
+        return null;
+    // 候选编号：daemon 列表序 × 祖先链序（由近及远），index 决定确定性优先级。
+    const candidates = [];
+    let idx = 0;
+    for (const daemon of daemons) {
+        for (const pid of ancestors) {
+            candidates.push({ index: idx++, ipcPort: daemon.ipcPort, pid });
+        }
+    }
+    // 并发发起全部查询，命中按 index 记入 hits；整体被 budget 封顶。
+    const hits = new Map();
+    const queries = candidates.map(async (c) => {
+        const route = await queryDaemon(c.ipcPort, c.pid);
+        if (route)
+            hits.set(c.index, route);
+    });
+    let timer;
+    const budget = new Promise((resolve) => {
+        timer = setTimeout(resolve, budgetMs);
+        timer.unref?.();
+    });
+    try {
+        await Promise.race([Promise.allSettled(queries), budget]);
+    }
+    finally {
+        if (timer)
+            clearTimeout(timer);
+    }
+    // 在「budget 内已 settle 的命中」里按候选 index 升序取最早的一个（确定性）。
+    let best = null;
+    let bestIdx = Infinity;
+    for (const [i, route] of hits) {
+        if (i < bestIdx) {
+            bestIdx = i;
+            best = route;
+        }
+    }
+    if (best && process.env.BOTMUX_HOOK_DEBUG === '1') {
+        process.stderr.write(`[adopt-route] matched candidate#${bestIdx} session=${best.sessionId}\n`);
+    }
+    return best;
+}
+//# sourceMappingURL=adopt-route.js.map

package/dist/adapters/adopt-route.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"adopt-route.js","sourceRoot":"","sources":["../../src/adapters/adopt-route.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAEH,OAAO,EAAE,YAAY,EAAE,MAAM,oBAAoB,CAAC;AAClD,OAAO,EAAE,YAAY,EAAE,MAAM,SAAS,CAAC;AAYvC,8EAA8E;AAE9E;;;;;;;;;GASG;AACH,SAAS,iBAAiB,CAAC,GAAW;IACpC,sBAAsB;IACtB,IAAI,CAAC;QACH,MAAM,IAAI,GAAG,YAAY,CAAC,SAAS,GAAG,OAAO,EAAE,OAAO,CAAC,CAAC;QACxD,+CAA+C;QAC/C,kCAAkC;QAClC,MAAM,SAAS,GAAG,IAAI,CAAC,WAAW,CAAC,GAAG,CAAC,CAAC;QACxC,IAAI,SAAS,KAAK,CAAC,CAAC;YAAE,MAAM,IAAI,KAAK,CAAC,8BAA8B,CAAC,CAAC;QACtE,MAAM,IAAI,GAAG,IAAI,CAAC,KAAK,CAAC,SAAS,GAAG,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;QAC9C,6BAA6B;QAC7B,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC;QAC9B,oCAAoC;QACpC,MAAM,IAAI,GAAG,QAAQ,CAAC,KAAK,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC;QACpC,IAAI,MAAM,CAAC,SAAS,CAAC,IAAI,CAAC,IAAI,IAAI,GAAG,CAAC;YAAE,OAAO,IAAI,CAAC;IACtD,CAAC;IAAC,MAAM,CAAC;QACP,wBAAwB;IAC1B,CAAC;IAED,kCAAkC;IAClC,IAAI,CAAC;QACH,MAAM,GAAG,GAAG,YAAY,CAAC,IAAI,EAAE,CAAC,IAAI,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,CAAC,GAAG,CAAC,CAAC,EAAE;YACjE,QAAQ,EAAE,OAAO;SAClB,CAAC,CAAC;QACH,MAAM,IAAI,GAAG,QAAQ,CAAC,GAAG,CAAC,IAAI,EAAE,EAAE,EAAE,CAAC,CAAC;QACtC,IAAI,MAAM,CAAC,SAAS,CAAC,IAAI,CAAC,IAAI,IAAI,GAAG,CAAC;YAAE,OAAO,IAAI,CAAC;IACtD,CAAC;IAAC,MAAM,CAAC;QACP,iBAAiB;IACnB,CAAC;IAED,OAAO,IAAI,CAAC;AACd,CAAC;AAED;;;;;;;GAOG;AACH,MAAM,UAAU,eAAe,CAC7B,QAAgB,EAChB,UAA2C,EAC3C,QAAiB;IAEjB,MAAM,MAAM,GAAG,UAAU,IAAI,iBAAiB,CAAC;IAC/C,MAAM,KAAK,GAAG,QAAQ,IAAI,EAAE,CAAC;IAC7B,MAAM,SAAS,GAAa,EAAE,CAAC;IAC/B,MAAM,OAAO,GAAG,IAAI,GAAG,CAAS,CAAC,QAAQ,CAAC,CAAC,CAAC;IAE5C,IAAI,OAAO,GAAG,QAAQ,CAAC;IACvB,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,KAAK,EAAE,CAAC,EAAE,EAAE,CAAC;QAC/B,MAAM,MAAM,GAAG,MAAM,CAAC,OAAO,CAAC,CAAC;QAC/B,IAAI,MAAM,KAAK,IAAI,IAAI,MAAM,IAAI,CAAC;YAAE,MAAM,CAAE,iBAAiB;QAC7D,IAAI,OAAO,CAAC,GAAG,CAAC,MAAM,CAAC;YAAE,MAAM,CAAa,KAAK;QACjD,OAAO,CAAC,GAAG,CAAC,MAAM,CAAC,CAAC;QACpB,SAAS,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;QACvB,OAAO,GAAG,MAAM,CAAC;IACnB,CAAC;IAED,OAAO,SAAS,CAAC;AACnB,CAAC;AAED,+EAA+E;AAE/E;;;;;;GAMG;AACH,MAAM,CAAC,KAAK,UAAU,iBAAiB,CACrC,OAAe,EACf,GAAW;IAEX,MAAM,UAAU,GAAG,IAAI,eAAe,EAAE,CAAC;IACzC,MAAM,KAAK,GAAG,UAAU,CAAC,GAAG,EAAE,CAAC,UAAU,CAAC,KAAK,EAAE,EAAE,IAAI,CAAC,CAAC;IACzD,IAAI,CAAC;QACH,MAAM,GAAG,GAAG,MAAM,KAAK,CACrB,oBAAoB,OAAO,sBAAsB,GAAG,EAAE,EACtD,EAAE,MAAM,EAAE,UAAU,CAAC,MAAM,EAAE,CAC9B,CAAC;QACF,IAAI,CAAC,GAAG,CAAC,EAAE;YAAE,OAAO,IAAI,CAAC;QACzB,MAAM,IAAI,GAAG,CAAC,MAAM,GAAG,CAAC,IAAI,EAAE,CAAY,CAAC;QAC3C,IAAI,CAAC,IAAI,IAAI,OAAO,IAAI,KAAK,QAAQ;YAAE,OAAO,IAAI,CAAC;QACnD,MAAM,CAAC,GAAG,IAA+B,CAAC;QAC1C,IACE,OAAO,CAAC,CAAC,SAAS,KAAK,QAAQ;YAC/B,OAAO,CAAC,CAAC,MAAM,KAAK,QAAQ;YAC5B,OAAO,CAAC,CAAC,SAAS,KAAK,QAAQ;YAC/B,OAAO,CAAC,CAAC,aAAa,KAAK,QAAQ,EACnC,CAAC;YACD,OAAO,IAAI,CAAC;QACd,CAAC;QACD,OAAO;YACL,SAAS,EAAE,CAAC,CAAC,SAAS;YACtB,MAAM,EAAE,CAAC,CAAC,MAAM;YAChB,SAAS,EAAE,CAAC,CAAC,SAAS;YACtB,aAAa,EAAE,CAAC,CAAC,aAAa;SAC/B,CAAC;IACJ,CAAC;IAAC,MAAM,CAAC;QACP,4BAA4B;QAC5B,OAAO,IAAI,CAAC;IACd,CAAC;YAAS,CAAC;QACT,YAAY,CAAC,KAAK,CAAC,CAAC;IACtB,CAAC;AACH,CAAC;AAED,+EAA+E;AAE/E;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,CAAC,KAAK,UAAU,iBAAiB,CAAC,IAMvC;IACC,MAAM,EAAE,QAAQ,EAAE,WAAW,EAAE,WAAW,EAAE,GAAG,IAAI,CAAC;IACpD,MAAM,YAAY,GAAG,IAAI,CAAC,YAAY,IAAI,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,eAAe,CAAC,GAAG,CAAC,CAAC,CAAC;IAC1E,MAAM,QAAQ,GAAG,IAAI,CAAC,QAAQ,IAAI,IAAI,CAAC;IACvC,MAAM,SAAS,GAAG,YAAY,CAAC,QAAQ,CAAC,CAAC;IACzC,IAAI,SAAS,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,IAAI,CAAC;IAExC,MAAM,OAAO,GAAG,WAAW,EAAE,CAAC;IAC9B,IAAI,OAAO,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,IAAI,CAAC;IAEtC,+CAA+C;IAC/C,MAAM,UAAU,GAA2D,EAAE,CAAC;IAC9E,IAAI,GAAG,GAAG,CAAC,CAAC;IACZ,KAAK,MAAM,MAAM,IAAI,OAAO,EAAE,CAAC;QAC7B,KAAK,MAAM,GAAG,IAAI,SAAS,EAAE,CAAC;YAC5B,UAAU,CAAC,IAAI,CAAC,EAAE,KAAK,EAAE,GAAG,EAAE,EAAE,OAAO,EAAE,MAAM,CAAC,OAAO,EAAE,GAAG,EAAE,CAAC,CAAC;QAClE,CAAC;IACH,CAAC;IAED,4CAA4C;IAC5C,MAAM,IAAI,GAAG,IAAI,GAAG,EAAsB,CAAC;IAC3C,MAAM,OAAO,GAAG,UAAU,CAAC,GAAG,CAAC,KAAK,EAAE,CAAC,EAAE,EAAE;QACzC,MAAM,KAAK,GAAG,MAAM,WAAW,CAAC,CAAC,CAAC,OAAO,EAAE,CAAC,CAAC,GAAG,CAAC,CAAC;QAClD,IAAI,KAAK;YAAE,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,KAAK,EAAE,KAAK,CAAC,CAAC;IACtC,CAAC,CAAC,CAAC;IAEH,IAAI,KAAgD,CAAC;IACrD,MAAM,MAAM,GAAG,IAAI,OAAO,CAAO,CAAC,OAAO,EAAE,EAAE;QAC3C,KAAK,GAAG,UAAU,CAAC,OAAO,EAAE,QAAQ,CAAC,CAAC;QACtC,KAAK,CAAC,KAAK,EAAE,EAAE,CAAC;IAClB,CAAC,CAAC,CAAC;IACH,IAAI,CAAC;QACH,MAAM,OAAO,CAAC,IAAI,CAAC,CAAC,OAAO,CAAC,UAAU,CAAC,OAAO,CAAC,EAAE,MAAM,CAAC,CAAC,CAAC;IAC5D,CAAC;YAAS,CAAC;QACT,IAAI,KAAK;YAAE,YAAY,CAAC,KAAK,CAAC,CAAC;IACjC,CAAC;IAED,mDAAmD;IACnD,IAAI,IAAI,GAAsB,IAAI,CAAC;IACnC,IAAI,OAAO,GAAG,QAAQ,CAAC;IACvB,KAAK,MAAM,CAAC,CAAC,EAAE,KAAK,CAAC,IAAI,IAAI,EAAE,CAAC;QAC9B,IAAI,CAAC,GAAG,OAAO,EAAE,CAAC;YAAC,OAAO,GAAG,CAAC,CAAC;YAAC,IAAI,GAAG,KAAK,CAAC;QAAC,CAAC;IACjD,CAAC;IACD,IAAI,IAAI,IAAI,OAAO,CAAC,GAAG,CAAC,iBAAiB,KAAK,GAAG,EAAE,CAAC;QAClD,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,mCAAmC,OAAO,YAAY,IAAI,CAAC,SAAS,IAAI,CAAC,CAAC;IACjG,CAAC;IACD,OAAO,IAAI,CAAC;AACd,CAAC"}

package/dist/adapters/backend/tmux-backend.d.ts

@@ -115,13 +115,15 @@ export declare function buildBotmuxEnvAssignments(env: NodeJS.ProcessEnv | undef
  *   $0 = '_' (placeholder), $1 = cwd, $2..N = KEY=VAL... bin args...
  *
  * The `cd` step makes the CLI's cwd survive a wayward `cd` in the user's
- * rcfile. The `exec /usr/bin/env` step injects botmux's per-bot/per-session
- * overrides AFTER rcfile load so they can't be shadowed by leftover exports.
+ * rcfile. The `unset` step removes bare creds the pane inherited from the tmux
+ * server's global env (REDACTED_ENV_UNSET_CLAUSE). The `exec /usr/bin/env` step
+ * injects botmux's per-bot/per-session overrides AFTER rcfile load so they
+ * can't be shadowed by leftover exports.
  *
  * POSIX-syntax (works in bash/zsh/sh); fish/csh/nu users get remapped to
  * bash/zsh/sh by resolveUserShell() so they hit the same SCRIPT path.
  */
-export declare const SHELL_WRAPPER_SCRIPT = "cd -- \"$1\" && shift && exec /usr/bin/env \"$@\"";
+export declare const SHELL_WRAPPER_SCRIPT: string;
 /**
  * Debug variant of the wrapper script — same prelude, but the CLI runs as
  * a *child* (no `exec`) and the wrapper hands off to an interactive shell