Gbt CLI Chat — Communication skill for Claude Code

cli_chat

**One capability bit from GBT V8, packaged standalone.** No. 101 of 341, `integration` domain (Integration).

外部 CLI 助手**对话面板**（把「集成」面板真的接到对话上）：`agents` 只读底表（装没装/版本/**能不能一次性驱动**/一次形态）· `send` **真发一句话**给选定的 CLI 助手（claude `-p` / codebuddy `-p` / codex `exec` / copilot `-p`，形态**现跑 --help 亲验**）· `transcript` 会话账 · `verify`/`where`。**「免费」的确切含义**：走各 CLI **自己的登录态/额度**（订阅额度），不经框架 API key ⇒ **不吃 API 账单**（≠ 无额度上限）。⚠️ 与 freebuff 的**本质差别**：这 4 位**都有**非交互一次性入口（freebuff 是 TUI-only）⇒ 面板**能真聊**。⚠️ `send` = 起外部进程 + 把 prompt 送出本机 ⇒ 挂 `process_execute`+`external_llm`；policy.py 无本位分支（owner-only，AI 无权改）⇒ 门在模块内自闸（auth_gate 唯一校验入口），缺授权如实报缺。未装位/图形位 fail-closed 如实报缺 + 给装法，**不编**。safe=false：send 起进程且内容出本机（不是纯只读面）。type=internal

That description is copied verbatim from the registry. `tests/test_spec.py` pins it, so documentation drift fails the build instead of shipping quietly.

What this package actually is

It is the **contract** for one capability: its name, its parameters, the values it accepts, and whether it can change state that cannot be restored. It is not the implementation — that lives in the runtime this bit was extracted from.

So `run()` goes through a narrow `Backend` protocol, and the default backend is a stub that **says so**:

status="validated"   backend="stub"   data={"executed": false}

Never `status="ok"`. A stub that reports success is worse than no stub, because the caller stops looking for the real thing.

Install

git clone https://github.com/gbtweilai-star/gbt-cli-chat.git
cd gbt-cli-chat
python -m pip install -e ".[dev]"

Use

python -m gbt_cli_chat info                  # capability card
python -m gbt_cli_chat spec --json           # machine-readable contract
python -m gbt