diff --git a/README.en.md b/README.en.md index 7d37187..332642c 100644 --- a/README.en.md +++ b/README.en.md @@ -82,13 +82,7 @@ After the model calls the file-return tool, the plugin hands the specified file ## AI Office Connector -The **AI Office** page lets the local Harness connect outward to a public Office. The machine needs no public IP, forwarded port, or WebSocket server. The Device Token is written only to the Harness credential provider; the ordinary config file contains only the device ID, Office origin, workspace aliases, and instruction-preset aliases. Office selects aliases and never receives local absolute paths. - -The current protocol is `office-harness.v1`. The connector authenticates and advertises capabilities with `POST /api/harness/connector/heartbeat`, then opens the downstream event plane with `GET /api/harness/connector/stream` over SSE. The settings page derives every fixed hook from the Office Base URL and reconnects with backoff after a disconnect. - -A `job.available` event makes the local connector fetch the payload, validate Workspace/Preset aliases, claim a 90-second lease, and renew it every 30 seconds. It creates an isolated Harness Session, reports safe status/tool/text progress, and writes a terminal result exactly once. Tool approvals and follow-up questions surface in Office; approve, reject, and text answers return over SSE to the original Session. Heartbeats and leases recover from dropped connections. - -A successful heartbeat response must be JSON: `{"ok":true,"protocolVersion":"office-harness.v1"}`. This makes a successful connection test proof of a compatible Office Connector instead of any URL that happens to return 200. +[Read the AI Office Connector guide](docs/AI-Office-Connector.en.md) ## Installation diff --git a/README.md b/README.md index f253e13..9e056eb 100644 --- a/README.md +++ b/README.md @@ -85,13 +85,7 @@ Connect IM bots to DeepSeek Harness by scanning a QR code, using an App Manifest ## AI Office Connector -「AI Office」页让本机 Harness 主动连接公网 Office，本机无需公网 IP、端口转发或 WebSocket 服务。Device Token 只写入 Harness 凭据存储；普通配置文件仅保存设备 ID、Office Origin、工作区 alias 和 Instruction Preset alias。Office 只能选择 alias，不会收到本机绝对路径。 - -当前协议版本为 `office-harness.v1`。连接器使用 `POST /api/harness/connector/heartbeat` 完成鉴权和能力握手，再以 `GET /api/harness/connector/stream` 建立 SSE 下行；设置页会从 Office Base URL 自动展示全部固定 Hook，并在断线后按退避策略自动重连。 - -Office 的 `job.available` 会触发本机拉取任务、校验 Workspace/Preset alias、领取 90 秒租约并每 30 秒续租。连接器创建独立 Harness Session，把状态、工具名和增量文字安全回传 Office，终态只允许写入一次。Harness 发起的工具审批或补充问题会进入 Office 人工面板；批准、拒绝或文字答案再经 SSE 回到原 Session，断线时由租约与 Heartbeat 恢复。 - -Heartbeat 成功响应必须是 JSON：`{"ok":true,"protocolVersion":"office-harness.v1"}`。这使「连接测试通过」代表命中了兼容的 Office Connector，而不只是某个碰巧返回 200 的网址。 +[查看 AI Office Connector 说明](docs/AI-Office-Connector.md) ## 安装 diff --git a/docs/images/Context_enhancement.png b/docs/images/Context_enhancement.png index 91d722f..bffb06e 100644 Binary files a/docs/images/Context_enhancement.png and b/docs/images/Context_enhancement.png differ diff --git a/docs/images/Context_enhancement_en.png b/docs/images/Context_enhancement_en.png index 21219cd..97d32db 100644 Binary files a/docs/images/Context_enhancement_en.png and b/docs/images/Context_enhancement_en.png differ