botmux 2.25.1 → 2.27.0

package/README.en.md

@@ -71,78 +71,71 @@ 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.
+
 ### Step 1: Create a Lark App
 
-Go to the [Lark Open Platform](https://open.larkoffice.com/app) and click "Create Custom App".
+**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.
+
+> ⚠️ **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.
+
+**Manual**: go to the [Lark Open Platform](https://open.larkoffice.com/app) and click "Create Custom App".
 
 ![Create App](docs/setup/create-app.png)
 
 ### Step 2: Get Credentials
 
+> The scan-to-create path completes this step automatically; skip to Step 3.
+
 Open the app details page → "Credentials & Basic Info", and copy the **App ID** and **App Secret**.
 
 ![Get Credentials](docs/setup/credentials.png)
 
-### Step 3: Add Permissions
-
-Go to "Permissions & Scopes" → "Batch Import/Export", and paste the following JSON to import all permissions at once:
-
-![Permissions](docs/setup/permissions.png)
-
-<details>
-<summary>Click to expand batch import JSON</summary>
-
-```json
-{
-  "scopes": {
-    "tenant": [
-      "contact:user.base:readonly",
-      "contact:user.id:readonly",
-      "im:chat:read",
-      "im:chat.members:bot_access",
-      "im:chat.members:read",
-      "im:message",
-      "im:message:readonly",
-      "im:message:send_as_bot",
-      "im:message:update",
-      "im:message.group_at_msg",
-      "im:message.group_at_msg:readonly",
-      "im:message.group_msg",
-      "im:message.p2p_msg:readonly",
-      "im:message.reactions:write_only",
-      "im:resource"
-    ]
-  }
-}
-```
-</details>
-
-### Step 4: Install & Start botmux
+### Step 3: Install & Start botmux
 
 ```bash
 # Install
 npm install -g botmux
 
-# Interactive setup — enter the App ID and App Secret from Step 2
+# 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 (must be running before configuring WebSocket subscription — Lark checks for an active connection)
+# 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
 ```
 
-### Step 5: Configure Event Subscription
+### Step 4: Add Permissions
 
-Back in the Lark Open Platform, go to "Events & Callbacks":
+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.
 
-1. **Subscription mode**: Click the edit icon, select "Receive events via persistent connection" (WebSocket) — requires botmux to be running so Lark can detect the connection
+![Permissions](docs/setup/permissions.png)
 
-![WebSocket subscription](docs/setup/event-websocket.png)
+The full JSON lives at `~/.botmux/lark-scopes.json` (also tracked in-repo at [src/setup/lark-scopes.json](src/setup/lark-scopes.json), kept in sync with the internal wiki, covers ~290 tenant + user scopes).
 
-2. **Add event**: Click "Add Event", search and add `im.message.receive_v1` (Receive messages v2.0)
+```bash
+# macOS
+cat ~/.botmux/lark-scopes.json | pbcopy
+# Linux X
+cat ~/.botmux/lark-scopes.json | xclip -selection clipboard
+# Wayland
+cat ~/.botmux/lark-scopes.json | wl-copy
+```
 
-![Add event](docs/setup/event-receive-msg.png)
+> Scan-created PersonalAgent apps have `im.message.receive_v1` + `card.action.trigger` subscribed and the bot capability enabled out of the box, per botmux maintainer testing. Lark hasn't documented this as stable behavior, so **if the bot receives no messages at all after setup**, see "Step 8: Troubleshoot — bot not receiving messages" below for a manual fallback.
 
-3. **Enable callback**: Switch to the "Callback Configuration" tab, turn on "Card action callback" (`card.action.trigger`)
+### Step 5: Add Redirect URL (optional)
+
+If you plan to use `/login` inside Lark to let botmux act on your behalf for docs / calendar / wiki / sheets, add a redirect URL under "Security Settings" → "Redirect URL":
+
+```
+http://127.0.0.1:9768/callback
+```
+
+Skip this step if you only need bot messaging.
 
 ### Step 6: Publish the App
 
@@ -158,7 +151,16 @@ Go to "Version Management & Release", click "Create Version" and publish. Set av
 
 ![Add bot to group](docs/setup/add-bot-to-group.png)
 
-### Step 8: Enable Boot-time Autostart (recommended)
+### Step 8: Troubleshoot — bot not receiving messages (fallback)
+
+PersonalAgent apps come with event subscriptions and bot capability pre-configured; in normal cases you don't touch this. If the bot **receives no messages at all** after setup (not even DMs), verify these two settings:
+
+- **Event subscription**: Open Platform → your app → Events & Callbacks → should be subscribed to `im.message.receive_v1` + `card.action.trigger`. If missing, add them manually. Subscription mode must be "Receive via persistent connection" (WebSocket), and the botmux daemon must be running.
+- **Bot capability**: Open Platform → your app → Features → Bot should be enabled (it is by default). Adjust name/avatar if needed.
+
+After verifying, restart: `botmux restart`.
+
+### Step 9: Enable Boot-time Autostart (recommended)
 
 Once the bot is sending and receiving messages cleanly, run:
 

package/README.md

@@ -173,78 +173,70 @@ 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 文件 + 打印一键复制命令 + 各步骤的深链。
+
 ### Step 1: 创建飞书应用
 
-打开 [飞书开放平台](https://open.larkoffice.com/app)，点击「创建企业自建应用」。
+**推荐路径**：`botmux setup` 选「1) 扫码建应用」，飞书扫码完成后自动落盘 AppID/AppSecret，无需手动浏览器创建。底层走 `@larksuiteoapi/node-sdk` 的官方 device flow。
+
+> ⚠️ **目前仅支持飞书 (feishu.cn) 租户**。扫码检测到 Lark 国际版 (larksuite.com) 会中止 setup —— daemon runtime (Lark Client/WSClient/event-dispatcher 等) 需要一并接入 lark 域，会在单独 PR 跟进。
+
+**手动路径**：打开 [飞书开放平台](https://open.larkoffice.com/app)，点击「创建企业自建应用」。
 
 ![创建应用](docs/setup/create-app.png)
 
 ### Step 2: 获取凭证
 
+> 扫码路径自动完成此步，可直接跳到 Step 3。
+
 进入应用详情 →「凭证与基础信息」，复制 **App ID** 和 **App Secret**。
 
 ![获取凭证](docs/setup/credentials.png)
 
-### Step 3: 添加权限
-
-进入「权限管理」→「批量导入/导出权限」，粘贴以下 JSON 一次性导入所有权限：
-
-![权限管理](docs/setup/permissions.png)
-
-<details>
-<summary>点击展开批量导入 JSON</summary>
-
-```json
-{
-  "scopes": {
-    "tenant": [
-      "contact:user.base:readonly",
-      "contact:user.id:readonly",
-      "im:chat:read",
-      "im:chat.members:bot_access",
-      "im:chat.members:read",
-      "im:message",
-      "im:message:readonly",
-      "im:message:send_as_bot",
-      "im:message:update",
-      "im:message.group_at_msg",
-      "im:message.group_at_msg:readonly",
-      "im:message.group_msg",
-      "im:message.p2p_msg:readonly",
-      "im:message.reactions:write_only",
-      "im:resource"
-    ]
-  }
-}
-```
-</details>
-
-### Step 4: 安装 & 启动 botmux
+### Step 3: 安装 & 启动 botmux
 
 ```bash
 # 安装
 npm install -g botmux
 
-# 交互式配置 — 输入 Step 2 的 App ID 和 App Secret
+# 交互式配置 — 选「1) 扫码建应用」或「2) 手动粘 AppID/Secret」
+# 凭证拿到后自动取一次 tenant_access_token 校验，通过才落盘 bots.json
+# setup 末尾会把完整权限 JSON 写到 ~/.botmux/lark-scopes.json 并打印一键复制命令
 botmux setup
 
-# 启动（飞书后台配置长连接订阅前需要先启动，否则无法检测到连接）
+# 启动（如果之后需要确认事件订阅，飞书后台会要求 daemon 已在跑才能识别长连接）
+# start 前再校验一次凭证；权限未配齐不会阻塞 daemon，只 WARN
 botmux start
 ```
 
-### Step 5: 配置事件订阅
+### Step 4: 添加权限
 
-回到飞书开放平台，进入「事件与回调」：
+setup 完成后，按 terminal 提示的一键复制命令把权限 JSON 复制到剪贴板，进入「权限管理」→「批量导入/导出权限」粘贴 → 提交审批。可用性范围选「仅自己可见」会自动通过：
 
-1. **订阅方式**：点击编辑图标，选择「使用长连接接收事件」（需要 botmux 已启动，飞书会检测长连接是否建立）
+![权限管理](docs/setup/permissions.png)
 
-![配置长连接](docs/setup/event-websocket.png)
+完整 JSON 已经写到 `~/.botmux/lark-scopes.json`，源仓库版本在 [src/setup/lark-scopes.json](src/setup/lark-scopes.json)（与本仓库内部 wiki 文档同步，覆盖 tenant + user 双套域 ≈ 290 项）。
 
-2. **添加事件**：点击「添加事件」，搜索添加 `im.message.receive_v1`（接收消息 v2.0）
+```bash
+# macOS
+cat ~/.botmux/lark-scopes.json | pbcopy
+# Linux X
+cat ~/.botmux/lark-scopes.json | xclip -selection clipboard
+# Wayland
+cat ~/.botmux/lark-scopes.json | wl-copy
+```
 
-![添加事件](docs/setup/event-receive-msg.png)
+> 扫码建出来的 PersonalAgent 应用，botmux 维护者实测默认已订阅 `im.message.receive_v1` + `card.action.trigger` 并开通 bot 能力，所以主线流程不再要求手动配。但飞书没在公开文档里承诺这是稳定行为，**如果配好后机器人完全收不到消息**，参见下方「Step 8: 机器人收不到消息时的自查」。
 
-3. **启用回调**：切换到「回调配置」tab，开启「卡片回传交互」（`card.action.trigger`）
+### Step 5: 添加重定向 URL（按需）
+
+如果之后要在飞书里 `/login` 让 botmux 以你的身份调云文档/日历/Wiki 等 API，进入「安全设置」→「重定向 URL」填入：
+
+```
+http://127.0.0.1:9768/callback
+```
+
+只用 bot 收发消息的话这一步可以跳过。
 
 ### Step 6: 发版
 
@@ -260,7 +252,16 @@ botmux start
 
 ![添加机器人到群](docs/setup/add-bot-to-group.png)
 
-### Step 8: 开机自启（推荐）
+### Step 8: 机器人收不到消息时的自查（fallback）
+
+PersonalAgent 默认配好事件订阅 + bot 能力，正常情况下不用动。如果按上面步骤走完 bot **完全收不到任何消息**（连私聊都不回），分别确认这两项：
+
+- **事件订阅**：开放平台 → 你的应用 → 事件与回调 → 应当订阅 `im.message.receive_v1` + `card.action.trigger`（默认已订阅，如缺失就手动添加）。订阅方式必须是「使用长连接接收事件」(WebSocket)，且 botmux daemon 已经在跑。
+- **机器人能力**：开放平台 → 你的应用 → 应用功能 → 机器人 应当已开通（默认开通），名字/头像可以改。
+
+确认后重启 daemon：`botmux restart`。
+
+### Step 9: 开机自启（推荐）
 
 确认机器人能正常收发消息之后，跑一次：
 

package/dist/adapters/backend/session-backend-selector.d.ts

@@ -0,0 +1,11 @@
+import type { SessionBackend } from './types.js';
+export interface SelectedSessionBackend {
+    backend: SessionBackend;
+    isTmuxMode: boolean;
+    isPipeMode: boolean;
+}
+export declare function selectSessionBackend(opts: {
+    sessionId: string;
+    useTmux: boolean;
+}): SelectedSessionBackend;
+//# sourceMappingURL=session-backend-selector.d.ts.map

package/dist/adapters/backend/session-backend-selector.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"session-backend-selector.d.ts","sourceRoot":"","sources":["../../../src/adapters/backend/session-backend-selector.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,YAAY,CAAC;AAEjD,MAAM,WAAW,sBAAsB;IACrC,OAAO,EAAE,cAAc,CAAC;IACxB,UAAU,EAAE,OAAO,CAAC;IACpB,UAAU,EAAE,OAAO,CAAC;CACrB;AAED,wBAAgB,oBAAoB,CAAC,IAAI,EAAE;IAAE,SAAS,EAAE,MAAM,CAAC;IAAC,OAAO,EAAE,OAAO,CAAA;CAAE,GAAG,sBAAsB,CAuB1G"}

package/dist/adapters/backend/session-backend-selector.js

@@ -0,0 +1,26 @@
+import { PtyBackend } from './pty-backend.js';
+import { TmuxBackend } from './tmux-backend.js';
+import { TmuxPipeBackend } from './tmux-pipe-backend.js';
+export function selectSessionBackend(opts) {
+    if (!opts.useTmux) {
+        return {
+            backend: new PtyBackend(),
+            isTmuxMode: false,
+            isPipeMode: false,
+        };
+    }
+    const sessionName = TmuxBackend.sessionName(opts.sessionId);
+    if (TmuxBackend.hasSession(sessionName)) {
+        return {
+            backend: new TmuxPipeBackend(sessionName, { ownsSession: true, isReattach: true }),
+            isTmuxMode: true,
+            isPipeMode: true,
+        };
+    }
+    return {
+        backend: new TmuxPipeBackend(sessionName, { createSession: true, ownsSession: true }),
+        isTmuxMode: true,
+        isPipeMode: true,
+    };
+}
+//# sourceMappingURL=session-backend-selector.js.map

package/dist/adapters/backend/session-backend-selector.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"session-backend-selector.js","sourceRoot":"","sources":["../../../src/adapters/backend/session-backend-selector.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,MAAM,kBAAkB,CAAC;AAC9C,OAAO,EAAE,WAAW,EAAE,MAAM,mBAAmB,CAAC;AAChD,OAAO,EAAE,eAAe,EAAE,MAAM,wBAAwB,CAAC;AASzD,MAAM,UAAU,oBAAoB,CAAC,IAA6C;IAChF,IAAI,CAAC,IAAI,CAAC,OAAO,EAAE,CAAC;QAClB,OAAO;YACL,OAAO,EAAE,IAAI,UAAU,EAAE;YACzB,UAAU,EAAE,KAAK;YACjB,UAAU,EAAE,KAAK;SAClB,CAAC;IACJ,CAAC;IAED,MAAM,WAAW,GAAG,WAAW,CAAC,WAAW,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC;IAC5D,IAAI,WAAW,CAAC,UAAU,CAAC,WAAW,CAAC,EAAE,CAAC;QACxC,OAAO;YACL,OAAO,EAAE,IAAI,eAAe,CAAC,WAAW,EAAE,EAAE,WAAW,EAAE,IAAI,EAAE,UAAU,EAAE,IAAI,EAAE,CAAC;YAClF,UAAU,EAAE,IAAI;YAChB,UAAU,EAAE,IAAI;SACjB,CAAC;IACJ,CAAC;IAED,OAAO;QACL,OAAO,EAAE,IAAI,eAAe,CAAC,WAAW,EAAE,EAAE,aAAa,EAAE,IAAI,EAAE,WAAW,EAAE,IAAI,EAAE,CAAC;QACrF,UAAU,EAAE,IAAI;QAChB,UAAU,EAAE,IAAI;KACjB,CAAC;AACJ,CAAC"}

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

@@ -4,22 +4,42 @@ import type { SessionBackend, SpawnOpts } from './types.js';
  *  to xterm.js (which treats bare LF as "down one row, keep column"). */
 export declare function normaliseCaptureLineEndings(s: string): string;
 export declare class TmuxPipeBackend implements SessionBackend {
-    /** Real tmux pane address (e.g. "0:2.0"). */
+    /** Real tmux pane address (e.g. "0:2.0") or botmux session name (bmx-*). */
     private readonly paneTarget;
     private readonly fifoPath;
     private readStream;
     private readonly dataCbs;
     private readonly exitCbs;
+    private lifecycleTimer;
     private cols;
     private rows;
     private exited;
     /** Set after pipe-pane subscription is active so kill() knows to cancel it. */
     private pipeAttached;
-    constructor(paneTarget: string);
-    /** spawn() in this backend doesn't actually spawn a process; it sets up
-     *  the pipe-pane subscription + fifo reader. The bin/args params are
-     *  ignored (the CLI is already running in the user's pane). */
-    spawn(_bin: string, _args: string[], opts: SpawnOpts): void;
+    private readonly createSession;
+    private readonly ownsSession;
+    private readonly _isReattach;
+    /** Claude Code session JSONL path — set by worker for claude-code sessions so
+     *  the claude-code adapter can verify paste+Enter submissions via file growth. */
+    claudeJsonlPath?: string;
+    /** PID of the spawned Claude Code child — used by the claude-code adapter to
+     *  follow Claude's authoritative session id via ~/.claude/sessions/<pid>.json. */
+    cliPid?: number;
+    /** Working directory the CLI was spawned in — cross-checked against the pid
+     *  file's cwd field so a recycled PID can't mislead the resolver. */
+    cliCwd?: string;
+    /** Whether this backend re-attached to an existing bmx-* tmux session
+     *  (rather than creating a new detached one). Mirrors TmuxBackend.isReattach
+     *  so the worker can branch on reattach behaviour without a private-cast. */
+    get isReattach(): boolean;
+    constructor(paneTarget: string, opts?: {
+        createSession?: boolean;
+        ownsSession?: boolean;
+        isReattach?: boolean;
+    });
+    /** spawn() sets up the pipe-pane subscription + fifo reader. In managed
+     *  mode it first creates a detached bmx-* tmux session that runs the CLI. */
+    spawn(bin: string, args: string[], opts: SpawnOpts): void;
     write(data: string): void;
     sendText(text: string): void;
     sendSpecialKeys(...keys: string[]): void;
@@ -34,20 +54,40 @@ export declare class TmuxPipeBackend implements SessionBackend {
     destroySession(): void;
     getChildPid(): number | null;
     getAttachInfo(): null;
-    /** Snapshot the current screen of the adopted pane WITH ANSI escapes,
-     *  including history (-S - = start of scrollback). New web-terminal
-     *  connections receive this string so xterm.js renders the existing
-     *  session state instead of a blank screen.
+    private startLifecycleWatcher;
+    private stopLifecycleWatcher;
+    private handlePaneExit;
+    private createDetachedSession;
+    private applySessionOptions;
+    /** Snapshot the full pane history WITH ANSI escapes (`-S - -E -`).
+     *
+     *  Used by web reattach so a brand-new web client sees the whole prior
+     *  conversation. For the screenshot / screen_update fast path use
+     *  `captureViewport()` instead — that one only returns the visible pane
+     *  and is safe to seed a transient xterm-headless with.
      *
      *  IMPORTANT: tmux capture-pane separates rows with bare `\n`, no `\r`.
      *  xterm.js (and any VT100-compliant emulator) treats a bare LF as
      *  "move down one row, keep column" — every captured line lands further
-     *  to the right than the previous one, producing the staircase artefact
-     *  observed in early pipe-mode dogfooding. Normalising every `\n` to
-     *  `\r\n` makes the snapshot render correctly. The live pipe-pane stream
-     *  itself doesn't need this fix — applications write proper `\r\n` (and
-     *  Claude Code uses cursor-positioning instead of bare LF anyway). */
+     *  to the right than the previous one. Normalising every `\n` to `\r\n`
+     *  makes the snapshot render correctly. The live pipe-pane stream itself
+     *  doesn't need this fix — applications write proper `\r\n`. */
     captureCurrentScreen(): string;
+    /** Snapshot ONLY the currently visible pane (no scrollback). Equivalent to
+     *  `tmux capture-pane` with no `-S`/`-E` flags, which defaults to the
+     *  viewport. This is the right input for a transient xterm-headless seed:
+     *  the snapshot row count matches the transient terminal's row count, so
+     *  no normal-buffer scroll happens and the rendered screenshot lines up
+     *  with what the user is seeing in the web terminal right now. */
+    captureViewport(): string;
+    private captureWithBounds;
+    /** Current real tmux pane dimensions. Drives transient-renderer sizing so
+     *  the screenshot canvas matches whatever the web client resized the pane
+     *  to. Returns null if tmux can't be queried (pane gone, server gone). */
+    getPaneSize(): {
+        cols: number;
+        rows: number;
+    } | null;
     /** Cheap probe: is the adopted pane currently in the alternate screen
      *  buffer? Used by captureCurrentScreen to decide whether the snapshot
      *  needs an alt-buffer-enter prefix for correct rendering. */

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

@@ -1 +1 @@
-{"version":3,"file":"tmux-pipe-backend.d.ts","sourceRoot":"","sources":["../../../src/adapters/backend/tmux-pipe-backend.ts"],"names":[],"mappings":"AA8BA,OAAO,KAAK,EAAE,cAAc,EAAE,SAAS,EAAE,MAAM,YAAY,CAAC;AAQ5D;;yEAEyE;AACzE,wBAAgB,2BAA2B,CAAC,CAAC,EAAE,MAAM,GAAG,MAAM,CAE7D;AAED,qBAAa,eAAgB,YAAW,cAAc;IACpD,6CAA6C;IAC7C,OAAO,CAAC,QAAQ,CAAC,UAAU,CAAS;IACpC,OAAO,CAAC,QAAQ,CAAC,QAAQ,CAAS;IAClC,OAAO,CAAC,UAAU,CAA8B;IAChD,OAAO,CAAC,QAAQ,CAAC,OAAO,CAAkC;IAC1D,OAAO,CAAC,QAAQ,CAAC,OAAO,CAAmE;IAC3F,OAAO,CAAC,IAAI,CAAO;IACnB,OAAO,CAAC,IAAI,CAAM;IAClB,OAAO,CAAC,MAAM,CAAS;IACvB,+EAA+E;IAC/E,OAAO,CAAC,YAAY,CAAS;gBAEjB,UAAU,EAAE,MAAM;IAQ9B;;mEAE+D;IAC/D,KAAK,CAAC,IAAI,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,EAAE,EAAE,IAAI,EAAE,SAAS,GAAG,IAAI;IAoD3D,KAAK,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI;IAKzB,QAAQ,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI;IAU5B,eAAe,CAAC,GAAG,IAAI,EAAE,MAAM,EAAE,GAAG,IAAI;IAUxC,SAAS,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI;IAgB7B,OAAO,CAAC,oBAAoB;IAuB5B,aAAa,IAAI,IAAI;IASrB,mBAAmB,CAAC,QAAQ,EAAE,MAAM,GAAG,IAAI;IAS3C,MAAM,CAAC,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,GAAG,IAAI;IAQxC,MAAM,CAAC,EAAE,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,GAAG,IAAI;IAIxC,MAAM,CAAC,EAAE,EAAE,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI,EAAE,MAAM,EAAE,MAAM,GAAG,IAAI,KAAK,IAAI,GAAG,IAAI;IAItE,IAAI,IAAI,IAAI;IAmBZ,cAAc,IAAI,IAAI;IAKtB,WAAW,IAAI,MAAM,GAAG,IAAI;IAkB5B,aAAa;IAMb;;;;;;;;;;;;0EAYsE;IACtE,oBAAoB,IAAI,MAAM;IAyB9B;;kEAE8D;IAC9D,OAAO,CAAC,iBAAiB;IAazB;iFAC6E;IAC7E,WAAW,IAAI,OAAO;IActB,OAAO,CAAC,QAAQ;CAKjB"}
+{"version":3,"file":"tmux-pipe-backend.d.ts","sourceRoot":"","sources":["../../../src/adapters/backend/tmux-pipe-backend.ts"],"names":[],"mappings":"AA8BA,OAAO,KAAK,EAAE,cAAc,EAAE,SAAS,EAAE,MAAM,YAAY,CAAC;AAS5D;;yEAEyE;AACzE,wBAAgB,2BAA2B,CAAC,CAAC,EAAE,MAAM,GAAG,MAAM,CAE7D;AAED,qBAAa,eAAgB,YAAW,cAAc;IACpD,4EAA4E;IAC5E,OAAO,CAAC,QAAQ,CAAC,UAAU,CAAS;IACpC,OAAO,CAAC,QAAQ,CAAC,QAAQ,CAAS;IAClC,OAAO,CAAC,UAAU,CAA8B;IAChD,OAAO,CAAC,QAAQ,CAAC,OAAO,CAAkC;IAC1D,OAAO,CAAC,QAAQ,CAAC,OAAO,CAAmE;IAC3F,OAAO,CAAC,cAAc,CAA+B;IACrD,OAAO,CAAC,IAAI,CAAO;IACnB,OAAO,CAAC,IAAI,CAAM;IAClB,OAAO,CAAC,MAAM,CAAS;IACvB,+EAA+E;IAC/E,OAAO,CAAC,YAAY,CAAS;IAC7B,OAAO,CAAC,QAAQ,CAAC,aAAa,CAAU;IACxC,OAAO,CAAC,QAAQ,CAAC,WAAW,CAAU;IACtC,OAAO,CAAC,QAAQ,CAAC,WAAW,CAAU;IAEtC;sFACkF;IAClF,eAAe,CAAC,EAAE,MAAM,CAAC;IACzB;sFACkF;IAClF,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB;yEACqE;IACrE,MAAM,CAAC,EAAE,MAAM,CAAC;IAEhB;;iFAE6E;IAC7E,IAAI,UAAU,IAAI,OAAO,CAExB;gBAEW,UAAU,EAAE,MAAM,EAAE,IAAI,CAAC,EAAE;QAAE,aAAa,CAAC,EAAE,OAAO,CAAC;QAAC,WAAW,CAAC,EAAE,OAAO,CAAC;QAAC,UAAU,CAAC,EAAE,OAAO,CAAA;KAAE;IAW/G;iFAC6E;IAC7E,KAAK,CAAC,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,EAAE,IAAI,EAAE,SAAS,GAAG,IAAI;IA8DzD,KAAK,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI;IAKzB,QAAQ,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI;IAU5B,eAAe,CAAC,GAAG,IAAI,EAAE,MAAM,EAAE,GAAG,IAAI;IAUxC,SAAS,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI;IAgB7B,OAAO,CAAC,oBAAoB;IAuB5B,aAAa,IAAI,IAAI;IASrB,mBAAmB,CAAC,QAAQ,EAAE,MAAM,GAAG,IAAI;IAS3C,MAAM,CAAC,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,GAAG,IAAI;IAYxC,MAAM,CAAC,EAAE,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,GAAG,IAAI;IAIxC,MAAM,CAAC,EAAE,EAAE,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI,EAAE,MAAM,EAAE,MAAM,GAAG,IAAI,KAAK,IAAI,GAAG,IAAI;IAItE,IAAI,IAAI,IAAI;IAmBZ,cAAc,IAAI,IAAI;IAOtB,WAAW,IAAI,MAAM,GAAG,IAAI;IAkB5B,aAAa;IAMb,OAAO,CAAC,qBAAqB;IAgB7B,OAAO,CAAC,oBAAoB;IAO5B,OAAO,CAAC,cAAc;IAYtB,OAAO,CAAC,qBAAqB;IAuB7B,OAAO,CAAC,mBAAmB;IAY3B;;;;;;;;;;;;oEAYgE;IAChE,oBAAoB,IAAI,MAAM;IAI9B;;;;;sEAKkE;IAClE,eAAe,IAAI,MAAM;IAKzB,OAAO,CAAC,iBAAiB;IAyBzB;;8EAE0E;IAC1E,WAAW,IAAI;QAAE,IAAI,EAAE,MAAM,CAAC;QAAC,IAAI,EAAE,MAAM,CAAA;KAAE,GAAG,IAAI;IAiBpD;;kEAE8D;IAC9D,OAAO,CAAC,iBAAiB;IAazB;iFAC6E;IAC7E,WAAW,IAAI,OAAO;IActB,OAAO,CAAC,QAAQ;CAKjB"}