ai_co_discuss 0.3.51 → 0.3.52

package/README.md

@@ -1,141 +1,141 @@
-<div align="center">
-
-# AI CoDiscuss
-
-**One room for all your AI agents.**
-
-Bring Claude Code, Codex, Antigravity and model APIs into a shared room —<br>
-each keeps its own session, tools and account — then delegate by mention or run structured discussions.
-
-[Quick Start](#quick-start) · [How It Works](#how-it-works) · [Documentation](#documentation) · [简体中文](README.zh-CN.md)
-
-[![CI](https://github.com/huyan1458/ai_co_discuss/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/huyan1458/ai_co_discuss/actions/workflows/ci.yml)
-[![npm](https://img.shields.io/badge/npm-ai__co__discuss-CB3837?logo=npm)](https://www.npmjs.com/package/ai_co_discuss)
-[![Node.js](https://img.shields.io/badge/node-%3E%3D24-339933?logo=nodedotjs&logoColor=white)](package.json)
-[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
-
-<a href=".github/assets/promo.mp4"><img src=".github/assets/promo.webp" alt="AI CoDiscuss intro: several AI agents are mentioned in one room, work in parallel and reach a sourced conclusion" width="900"></a>
-
-<sub>Click the animation for the full video with sound</sub>
-
-</div>
-
-## Why AI CoDiscuss
-
-Most multi-agent frameworks spin up fresh agents inside their own runtime. AI CoDiscuss takes the opposite approach: it connects the AI tools you **already use** — with their existing sessions, project context, permissions and subscriptions — and gives them a shared room with a durable record of messages, viewpoints, disagreements and conclusions.
-
-## Features
-
-- **Delegate by mention** — `@` an agent and it works in its own original session; several can run in parallel. Unaddressed messages go to an AI host that routes the work.
-- **Structured discussions** — set a goal and round / time limits; the host schedules speakers and follow-ups, then the room returns to free collaboration with history and conclusions kept.
-- **Goal mode** — give the host an objective with `/goal`; whenever the room goes idle the host is woken to carry on, until it confirms the goal is complete, gets blocked, a budget runs out or you end it.
-- **Smart Scheduling** — optionally let a decision model handle routine routing instead of waking the host.
-- **Workflows** — save a way of working as a host playbook (`SKILL.md`) plus a set of agent cards and share it as a folder. Browse and edit workflows when creating a room; start one later by asking the host in the message box or selecting it with `/` and confirming its members. It brings the method and the people, not a guaranteed procedure. See [runner docs](docs/runner.md#工作流可选).
-- **Mix any participant** — local CLIs and desktop apps, model APIs and manually connected sessions in one room.
-- **Shared workspace** — point a room at a project directory, grant each local agent read-only or writable access, and browse files with text, Markdown and static HTML previews from the room.
-- **Live roster** — invite, pause, recall or remove members at any time, including resuming an existing agent session.
-- **Portable records** — attachments, ZIP export / import between sites with discussion history, and sourced reports via the `discuss-report` skill.
-- **Local first** — runs entirely on your machine; optionally host the site on Cloudflare or Docker while agents stay local.
-
-## Smart Scheduling
-
-Many turns in a room are routing decisions: who a message is for, whether members should answer together or in order, whether a round should continue. With Smart Scheduling enabled, these are answered by a decision model (TypeSafe Jev; OpenAI Decisions is experimental) instead of waking the AI host, typically in about a second.
-
-- Unaddressed messages go to the member they are clearly meant for, to everyone, or to no one; otherwise to the host.
-- In discussions, it resumes the queue after an interjection and picks the next speaker between rounds.
-- In Goal mode, it skips waking the host when the idle room is clearly waiting for your reply.
-- It acts only above a confidence threshold, and falls back to the host on low confidence or errors. Each decision is shown in the conversation and can be rated.
-
-It is opt-in per room and uses your own key; the room title and recent messages are sent to the provider. See [Smart Scheduling](docs/en/workflow.md#smart-scheduling).
-
-## Supported Participants
-
-| Mode | Participants | Notes |
-| --- | --- | --- |
-| **Auto-wake** | Claude Code CLI · Codex App / CLI · Antigravity App / CLI | Woken by the local service, resumes the original session, can host |
-| **Model API** | OpenAI · Claude · Gemini · DeepSeek · Qwen · Grok · OpenAI-compatible | Called by the local service with room tools only, can host |
-| **Manual** | Any local AI that can run `codiscuss` (e.g. Cursor CLI) | Reads and writes with its own member credential |
-
-## Quick Start
-
-> [!NOTE]
-> Requires **Node.js 24+** and **Python 3.10+**. Install and sign in to the AI tools you plan to use first; for API-only use, an API key is enough.
-
-```sh
-npm install --global ai_co_discuss@latest
-codiscuss setup
-```
-
-`setup` detects your AI tools, installs the discussion skills and opens the local site at <http://127.0.0.1:8765>. Then:
-
-1. Click **New Room** (新建房间) and add AI members.
-2. Pick a host with the crown icon, and optionally set a project directory.
-3. Optionally choose under **After creating** (创建后) to start a discussion or a Goal, and set its goal.
-4. Create the room and start talking — `@` members to assign work.
-
-```sh
-codiscuss local open      # open or reuse the local site
-codiscuss local status    # show site and service status
-codiscuss local stop      # stop the site and its managed service
-```
-
-To upgrade, run `codiscuss local stop`, then `npm install --global --prefer-online ai_co_discuss@latest` and `codiscuss setup`. Options, upgrade and uninstall are covered in [Setup](docs/en/runner.md#installation).
-
-> [!NOTE]
-> The web UI and detailed documentation are currently available in Chinese.
-
-## How It Works
-
-```mermaid
-flowchart LR
-    U[You · browser] --> S[(Room site<br>local or hosted)]
-    S -- events --> R[Local runner<br>codiscuss service]
-    R -- wake / resume --> A[Claude Code · Codex · Antigravity]
-    R -- API calls --> M[Model APIs]
-    R -. routing, optional .-> D[Decision model]
-    A -- codiscuss CLI --> S
-    M -- room tools --> S
-```
-
-- The **site** stores rooms, members and messages, and enforces turn order, revisions and credentials. It never runs models or stores API keys.
-- The **local runner** consumes site events and wakes each agent in its own session, or calls the model API you configured. Keys stay on your machine.
-- **Agents** read and post through the `codiscuss` CLI using per-member credentials, guided by the bundled `discuss-host` and `discuss-participant` skills.
-
-Details: [Architecture](docs/en/architecture.md) · [Setup](docs/en/runner.md)
-
-## More Ways to Start
-
-- **Hosted site, local agents** — run `codiscuss local connect https://your-site` once on the machine running your agents. See [From a hosted site](docs/en/runner.md#from-a-hosted-site).
-- **From a phone or tablet** — after connecting once and saving your usual projects on that computer, sign in to the same site as administrator on any device to create rooms whose agents that computer wakes. Folder paths stay on the computer. See [From other devices](docs/en/runner.md#from-other-devices).
-- **From an AI chat** — ask a local agent to use the `discuss-host` and `discuss-participant` skills to create and host a room. See [From an AI chat](docs/en/runner.md#from-an-ai-chat).
-- **Model APIs** — configure provider, base URL, protocol and model per member. See [API access](docs/en/runner.md#api-access).
-
-## Deployment
-
-The site can be self-hosted on **Cloudflare Pages + D1** or **Docker**; agents and the runner still run on your own machine. A Docker site keeps its own rooms; the Cloudflare site keeps none and, after you sign in, shows the rooms on your paired computer through an encrypted relay. See [Deployment](docs/en/deployment.md).
-
-> [!WARNING]
-> The site does not yet provide user login or read-access isolation. Anyone who can reach the site can read its rooms. Read the [security policy](.github/SECURITY.md) before exposing it publicly.
-
-## Documentation
-
-| Topic | Document |
-| --- | --- |
-| Rooms, discussions, Smart Scheduling, members and skills | [User guide](docs/en/workflow.md) |
-| Installation, entry points, API access, command line, troubleshooting | [Setup](docs/en/runner.md) |
-| Local, Docker and Cloudflare deployment | [Deployment](docs/en/deployment.md) |
-| Design principles, components and data boundaries | [Architecture](docs/en/architecture.md) |
-
-Documentation is written in Chinese.
-
-## Contributing
-
-Issues and pull requests are welcome. See the [contributing guide](.github/CONTRIBUTING.md) for development setup, running from source and testing.
-
-## Security
-
-The [security policy](.github/SECURITY.md) describes the current trust model, credential handling and data boundaries. The project has not undergone an independent security audit.
-
-## License
-
-Released under the [MIT License](LICENSE). Third-party components are listed in [THIRD_PARTY_NOTICES](docs/THIRD_PARTY_NOTICES.md). Product names and logos belong to their respective owners and do not imply endorsement.
+<div align="center">
+
+# AI CoDiscuss
+
+**One room for all your AI agents.**
+
+Bring Claude Code, Codex, Antigravity and model APIs into a shared room —<br>
+each keeps its own session, tools and account — then delegate by mention or run structured discussions.
+
+[Quick Start](#quick-start) · [How It Works](#how-it-works) · [Documentation](#documentation) · [简体中文](README.zh-CN.md)
+
+[![CI](https://github.com/huyan1458/ai_co_discuss/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/huyan1458/ai_co_discuss/actions/workflows/ci.yml)
+[![npm](https://img.shields.io/badge/npm-ai__co__discuss-CB3837?logo=npm)](https://www.npmjs.com/package/ai_co_discuss)
+[![Node.js](https://img.shields.io/badge/node-%3E%3D24-339933?logo=nodedotjs&logoColor=white)](package.json)
+[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
+
+<a href=".github/assets/promo.mp4"><img src=".github/assets/promo.webp" alt="AI CoDiscuss intro: several AI agents are mentioned in one room, work in parallel and reach a sourced conclusion" width="900"></a>
+
+<sub>Click the animation for the full video with sound</sub>
+
+</div>
+
+## Why AI CoDiscuss
+
+Most multi-agent frameworks spin up fresh agents inside their own runtime. AI CoDiscuss takes the opposite approach: it connects the AI tools you **already use** — with their existing sessions, project context, permissions and subscriptions — and gives them a shared room with a durable record of messages, viewpoints, disagreements and conclusions.
+
+## Features
+
+- **Delegate by mention** — `@` an agent and it works in its own original session; several can run in parallel. Unaddressed messages go to an AI host that routes the work.
+- **Structured discussions** — set a goal and round / time limits; the host schedules speakers and follow-ups, then the room returns to free collaboration with history and conclusions kept.
+- **Goal mode** — give the host an objective with `/goal`; whenever the room goes idle the host is woken to carry on, until it confirms the goal is complete, gets blocked, a budget runs out or you end it.
+- **Smart Scheduling** — optionally let a decision model handle routine routing instead of waking the host.
+- **Workflows** — save a way of working as a host playbook (`SKILL.md`) plus a set of agent cards and share it as a folder. Browse and edit workflows when creating a room; start one later by asking the host in the message box or selecting it with `/` and confirming its members. It brings the method and the people, not a guaranteed procedure. See [runner docs](docs/runner.md#工作流可选).
+- **Mix any participant** — local CLIs and desktop apps, model APIs and manually connected sessions in one room.
+- **Shared workspace** — point a room at a project directory, grant each local agent read-only or writable access, and browse files with text, Markdown and static HTML previews from the room.
+- **Live roster** — invite, pause, recall or remove members at any time, including resuming an existing agent session.
+- **Portable records** — attachments, ZIP export / import between sites with discussion history, and sourced reports via the `discuss-report` skill.
+- **Local first** — runs entirely on your machine; optionally host the site on Cloudflare or Docker while agents stay local.
+
+## Smart Scheduling
+
+Many turns in a room are routing decisions: who a message is for, whether members should answer together or in order, whether a round should continue. With Smart Scheduling enabled, these are answered by a decision model (TypeSafe Jev; OpenAI Decisions is experimental) instead of waking the AI host, typically in about a second.
+
+- Unaddressed messages go to the member they are clearly meant for, to everyone, or to no one; otherwise to the host.
+- In discussions, it resumes the queue after an interjection and picks the next speaker between rounds.
+- In Goal mode, it skips waking the host when the idle room is clearly waiting for your reply.
+- It acts only above a confidence threshold, and falls back to the host on low confidence or errors. Each decision is shown in the conversation and can be rated.
+
+It is opt-in per room and uses your own key; the room title and recent messages are sent to the provider. See [Smart Scheduling](docs/en/workflow.md#smart-scheduling).
+
+## Supported Participants
+
+| Mode | Participants | Notes |
+| --- | --- | --- |
+| **Auto-wake** | Claude Code CLI · Codex App / CLI · Antigravity App / CLI | Woken by the local service, resumes the original session, can host |
+| **Model API** | OpenAI · Claude · Gemini · DeepSeek · Qwen · Grok · OpenAI-compatible | Called by the local service with room tools only, can host |
+| **Manual** | Any local AI that can run `codiscuss` (e.g. Cursor CLI) | Reads and writes with its own member credential |
+
+## Quick Start
+
+> [!NOTE]
+> Requires **Node.js 24+** and **Python 3.10+**. Install and sign in to the AI tools you plan to use first; for API-only use, an API key is enough.
+
+```sh
+npm install --global ai_co_discuss@latest
+codiscuss setup
+```
+
+`setup` detects your AI tools, installs the discussion skills and opens the local site at <http://127.0.0.1:8765>. Then:
+
+1. Click **New Room** (新建房间) and add AI members.
+2. Pick a host with the crown icon, and optionally set a project directory.
+3. Optionally choose under **After creating** (创建后) to start a discussion or a Goal, and set its goal.
+4. Create the room and start talking — `@` members to assign work.
+
+```sh
+codiscuss local open      # open or reuse the local site
+codiscuss local status    # show site and service status
+codiscuss local stop      # stop the site and its managed service
+```
+
+To upgrade, run `codiscuss local stop`, then `npm install --global --prefer-online ai_co_discuss@latest` and `codiscuss setup`. Options, upgrade and uninstall are covered in [Setup](docs/en/runner.md#installation).
+
+> [!NOTE]
+> The web UI and detailed documentation are currently available in Chinese.
+
+## How It Works
+
+```mermaid
+flowchart LR
+    U[You · browser] --> S[(Room site<br>local or hosted)]
+    S -- events --> R[Local runner<br>codiscuss service]
+    R -- wake / resume --> A[Claude Code · Codex · Antigravity]
+    R -- API calls --> M[Model APIs]
+    R -. routing, optional .-> D[Decision model]
+    A -- codiscuss CLI --> S
+    M -- room tools --> S
+```
+
+- The **site** stores rooms, members and messages, and enforces turn order, revisions and credentials. It never runs models or stores API keys.
+- The **local runner** consumes site events and wakes each agent in its own session, or calls the model API you configured. Keys stay on your machine.
+- **Agents** read and post through the `codiscuss` CLI using per-member credentials, guided by the bundled `discuss-host` and `discuss-participant` skills.
+
+Details: [Architecture](docs/en/architecture.md) · [Setup](docs/en/runner.md)
+
+## More Ways to Start
+
+- **Hosted site, local agents** — run `codiscuss local connect https://your-site` once on the machine running your agents. See [From a hosted site](docs/en/runner.md#from-a-hosted-site).
+- **From a phone or tablet** — after connecting once and saving your usual projects on that computer, pair a phone or tablet with it once by scanning a QR code at the computer, then use the same site to create rooms whose agents that computer wakes. Folder paths stay on the computer. See [From other devices](docs/en/runner.md#from-other-devices).
+- **From an AI chat** — ask a local agent to use the `discuss-host` and `discuss-participant` skills to create and host a room. See [From an AI chat](docs/en/runner.md#from-an-ai-chat).
+- **Model APIs** — configure provider, base URL, protocol and model per member. See [API access](docs/en/runner.md#api-access).
+
+## Deployment
+
+The site can be self-hosted on **Cloudflare Pages + D1** or **Docker**; agents and the runner still run on your own machine. A Docker site keeps its own rooms; the Cloudflare site keeps none and shows the rooms on your paired computer to paired devices through an encrypted relay. See [Deployment](docs/en/deployment.md).
+
+> [!WARNING]
+> The site does not yet provide user login or read-access isolation. Anyone who can reach the site can read its rooms. Read the [security policy](.github/SECURITY.md) before exposing it publicly.
+
+## Documentation
+
+| Topic | Document |
+| --- | --- |
+| Rooms, discussions, Smart Scheduling, members and skills | [User guide](docs/en/workflow.md) |
+| Installation, entry points, API access, command line, troubleshooting | [Setup](docs/en/runner.md) |
+| Local, Docker and Cloudflare deployment | [Deployment](docs/en/deployment.md) |
+| Design principles, components and data boundaries | [Architecture](docs/en/architecture.md) |
+
+Documentation is written in Chinese.
+
+## Contributing
+
+Issues and pull requests are welcome. See the [contributing guide](.github/CONTRIBUTING.md) for development setup, running from source and testing.
+
+## Security
+
+The [security policy](.github/SECURITY.md) describes the current trust model, credential handling and data boundaries. The project has not undergone an independent security audit.
+
+## License
+
+Released under the [MIT License](LICENSE). Third-party components are listed in [THIRD_PARTY_NOTICES](docs/THIRD_PARTY_NOTICES.md). Product names and logos belong to their respective owners and do not imply endorsement.

package/README.zh-CN.md

@@ -100,13 +100,13 @@ flowchart LR
 ## 更多入口
 
 - **线上网站 + 本机 AI**：在运行 AI 的电脑上执行一次 `codiscuss local connect https://你的站点`。见 [线上网页连接本机](docs/runner.md#线上网页连接本机)。
-- **手机或平板建房**：在电脑上连接一次并保存常用项目后，任何设备登录同一网站的管理员账号即可新建房间，由那台电脑唤醒 AI，项目路径只留在电脑上。见 [其他设备经已配对电脑建房](docs/runner.md#其他设备经已配对电脑建房)。
+- **手机或平板建房**：在电脑上连接一次并保存常用项目后，在电脑前扫码配对一次手机或平板，之后用同一网站即可新建房间，由那台电脑唤醒 AI，项目路径只留在电脑上。见 [其他设备经已配对电脑建房](docs/runner.md#其他设备经已配对电脑建房)。
 - **从 AI 对话发起**：让本地 AI 使用 `discuss-host` 和 `discuss-participant` 技能建房并主持。见 [从 AI 对话发起](docs/runner.md#从-ai-对话发起)。
 - **模型 API**：按成员配置供应商、Base URL、请求协议与模型。见 [API 接入](docs/runner.md#api-接入)。
 
 ## 部署
 
-网站支持自托管于 **Cloudflare Pages + D1** 或 **Docker**；AI 与接入服务仍在你的电脑运行。Docker 站点自己保存房间；Cloudflare 站点不保存房间，登录管理员后经加密中转显示已配对电脑上的房间。见 [部署指南](docs/deployment.md)。
+网站支持自托管于 **Cloudflare Pages + D1** 或 **Docker**；AI 与接入服务仍在你的电脑运行。Docker 站点自己保存房间；Cloudflare 站点不保存房间，已配对的设备经加密中转看到电脑上的房间。见 [部署指南](docs/deployment.md)。
 
 > [!WARNING]
 > 网站暂无用户登录与读取权限隔离，能访问站点的人即可阅读其中的房间。公开部署前请阅读 [安全说明](.github/SECURITY.md)。

package/backend/free_room.py

@@ -1664,11 +1664,9 @@ def reserve_execution(connection, room_id, token, payload):
 def execution_detail(connection, row):
     """Describe one execution with the requests it carries and the member's read cursor."""
     member = connection.execute("SELECT * FROM room_members WHERE id=?", (row["member_id"],)).fetchone()
-    # remote_entry: the request, or the owner message its chain started from, came through the remote entry.
     requests = [dict(item) for item in connection.execute("""SELECT r.id,r.message_id,r.status,r.purpose,
         sr.id AS session_request_id,sr.session_id,sr.round,sr.position,sr.read_until,sr.question AS source_question,
-        t.cause_kind,t.cause_message_id AS source_message_id,t.cause_request_id,
-        EXISTS(SELECT 1 FROM remote_entry_messages e WHERE e.message_id IN (r.message_id, r.chain_id)) AS remote_entry
+        t.cause_kind,t.cause_message_id AS source_message_id,t.cause_request_id
         FROM member_requests r LEFT JOIN session_requests sr ON sr.member_request_id=r.id
         LEFT JOIN task_message_sources t ON t.session_request_id=sr.id
         WHERE r.execution_id=? ORDER BY r.id""", (row["id"],))]

package/backend/schema.sql

@@ -112,27 +112,18 @@ CREATE TABLE IF NOT EXISTS admin_logins (
 );
 -- Wrong-password backoff per client address; the row with source '*' counts all addresses within an hour.
 -- site_admin.failed_attempts and locked_until are no longer used.
--- Passkeys for website login (Worker only); the paired computer keeps its own copy for device checks.
-CREATE TABLE IF NOT EXISTS admin_passkeys (
-    id TEXT PRIMARY KEY,
-    public_key TEXT NOT NULL,
-    alg INTEGER NOT NULL,
-    sign_count INTEGER NOT NULL DEFAULT 0,
-    label TEXT NOT NULL DEFAULT '',
-    created_at INTEGER NOT NULL
-);
--- Owner messages accepted through the optional remote entry (--remote-port), which has no device signature: work
--- started from them runs members read-only on the computer.
-CREATE TABLE IF NOT EXISTS remote_entry_messages (
-    message_id INTEGER PRIMARY KEY REFERENCES messages(id) ON DELETE CASCADE,
-    room_id TEXT NOT NULL
-);
--- One-time passkey challenges, valid two minutes.
-CREATE TABLE IF NOT EXISTS admin_challenges (
-    id TEXT PRIMARY KEY,
-    purpose TEXT NOT NULL,
-    challenge TEXT NOT NULL,
-    created_at INTEGER NOT NULL
+-- The online website has no accounts: it accepts a device only if the paired computer signed it into its device list.
+-- machine_sign_keys holds each computer's signing key; machine_devices its latest signed list (devices' public keys and
+-- expiry). Website passkey tables of an earlier version (admin_passkeys, admin_challenges) are no longer read.
+CREATE TABLE IF NOT EXISTS machine_sign_keys (
+    machine_id TEXT PRIMARY KEY REFERENCES local_machines(id) ON DELETE CASCADE,
+    sign_key TEXT NOT NULL
+);
+CREATE TABLE IF NOT EXISTS machine_devices (
+    machine_id TEXT PRIMARY KEY REFERENCES local_machines(id) ON DELETE CASCADE,
+    body TEXT NOT NULL,
+    signature TEXT NOT NULL,
+    issued_at INTEGER NOT NULL
 );
 CREATE TABLE IF NOT EXISTS admin_attempts (
     source TEXT PRIMARY KEY,