@chorus-aidlc/chorus 0.19.0 → 0.20.0

package/README.ko.md

@@ -38,6 +38,10 @@ Idea ──> Proposal ──> [Document + Task DAG] ──> Execute ──> Veri
 
 ## 최근 업데이트
 
+**[v0.20.0](https://chorus-ai.dev/blog/chorus-v0.20.0-release/)** — 데몬 백엔드를 Codex App Server, Claude Code 양방향 stream-json, Pi 네이티브 RPC로 전환해 프로토콜로 중단과 실행 상태를 처리합니다. 새 `chorus upgrade` 명령은 npm으로 전역 설치한 CLI를 업데이트하며, `--plugins`를 추가하면 설정된 Claude Code, Codex, Kiro, Pi 연동도 갱신합니다.
+
+**[v0.19.1](https://chorus-ai.dev/blog/chorus-v0.19.1-release/)** — 가벼운 Research로 Idea 구체화와 Proposal 설계 단계에서 핵심 사실을 확인할 수 있습니다. 인라인 근거 인용으로 주장과 출처를 연결하고, 개발 시작 전에는 Tracker에서 추가 조사를 요청할 수 있습니다.
+
 **[v0.19.0](https://chorus-ai.dev/blog/chorus-v0.19.0-release/)** — Cloudflare를 참고해 리뷰 범위를 명확히 하고, 문제의 근거를 온전히 남기며, 고정 ID로 재검토까지 추적합니다. 태스크 리뷰는 인수 기준 외의 코드 품질도 기본으로 검사합니다.
 
 **[v0.18.0](https://chorus-ai.dev/blog/chorus-v0.18.0-release/)** — OpenSpec을 보완하는 가볍고 Git 친화적인 로컬 Spec 관리 방식으로 `spec-lite`를 내장했습니다. live session anchor를 통해 데몬 에이전트의 응답이 작업을 시작한 에이전트의 기존 Idea 세션으로 돌아갑니다.
@@ -46,16 +50,6 @@ Idea ──> Proposal ──> [Document + Task DAG] ──> Execute ──> Veri
 
 **[v0.17.0–0.17.1](https://github.com/Chorus-AIDLC/Chorus/releases/tag/v0.17.1)** — 하나의 CLI로 여러 코딩 에이전트에 Chorus를 설치하고 업데이트할 수 있습니다. 이제 Tracker, Graph, Idea 상세 화면에서 데몬 활동도 실시간으로 확인할 수 있습니다.
 
-**[v0.16.4](https://chorus-ai.dev/blog/chorus-v0.16.4-release/)** — DeepSeek Harness(dsh)가 여섯 번째 연결 방식으로 추가됩니다: `@chorus-aidlc/chorus-dsh` 번들이 Chorus의 스킬·페르소나·MCP 설정을 임의의 dsh 프로파일에 추가합니다. 현재는 대화식 사용만, 데몬 웨이크는 추후 지원.
-
-**[v0.16.1](https://chorus-ai.dev/blog/chorus-v0.16.1-release/)** — 이제 하나의 `chorus daemon`이 서로 독립적인 여러 에이전트를 동시에 서비스합니다. 각 에이전트는 `agents[]` 배열로 자신의 키·작업 디렉터리·백엔드·권한을 가집니다. 에이전트끼리 @멘션으로 작업을 넘길 수 있고, 각 웨이크는 해당 에이전트 자신의 프로젝트 디렉터리에 도착합니다.
-
-**[v0.16.0](https://chorus-ai.dev/blog/chorus-v0.16.0-release/)** — 에이전트를 문서 사이트([doc.chorus-ai.dev](https://doc.chorus-ai.dev))로 안내하는 `docs` 스킬을 추가해, 기억에 의존하지 않고 현재 문서를 읽고 답하도록 했습니다.
-
-**[v0.15.0](https://chorus-ai.dev/blog/chorus-v0.15.0-release/)** — 프로젝트별 Agent 작업 디렉터리: 각 사용자가 프로젝트의 Agent마다 호스트와 cwd를 지정하고, 데몬이 허용한 루트만 탐색할 수 있습니다. 배정, 웨이크, 재개, 후속 턴에서 같은 실행 위치를 사용하며 진행 중인 세션은 이동하지 않습니다. Codex는 재개 가능한 백엔드 thread ID를 별도로 저장하고, 더 이상 필요하지 않은 Chorus session 관리 단계를 제거했습니다.
-
-**[v0.14.1](https://chorus-ai.dev/blog/chorus-v0.14.1-release/)** — Amazon Kiro CLI가 네 번째 연결 방식이 되었습니다(Kiro CLI v2): `chorus agents add` 명령 한 줄로 설치하는 Kiro 플러그인과 `--agent kiro` 데몬 백엔드, 여기에 몇 가지 데몬 수정.
-
 > 전체 변경 이력: [CHANGELOG.md](CHANGELOG.md)
 
 ---
@@ -65,7 +59,7 @@ Idea ──> Proposal ──> [Document + Task DAG] ──> Execute ──> Veri
 두 개의 명령이면 됩니다. 데이터베이스도, Docker도, 설정 파일도 필요 없습니다.
 
 ```bash
-npm install -g @chorus-aidlc/chorus@0.19.0
+npm install -g @chorus-aidlc/chorus@0.20.0
 chorus
 ```
 

package/README.md

@@ -38,6 +38,10 @@ The labels under each stage are the **permissions** an actor needs there — gra
 
 ## What's New
 
+**[v0.20.0](https://chorus-ai.dev/blog/chorus-v0.20.0-release/)** — Daemon backends now use Codex App Server, bidirectional Claude Code stream-json, and native Pi RPC for protocol-based interruption and execution tracking. New `chorus upgrade` updates npm-global CLI installations; `--plugins` also refreshes configured Claude Code, Codex, Kiro, and Pi integrations.
+
+**[v0.19.1](https://chorus-ai.dev/blog/chorus-v0.19.1-release/)** — Lightweight Research checks factual gaps during Idea and Proposal preparation. Inline evidence citations put sources next to claims, and Tracker can request more research before development starts.
+
 **[v0.19.0](https://chorus-ai.dev/blog/chorus-v0.19.0-release/)** — Cloudflare-inspired reviewer rules: clearer scope, complete blocker evidence, and stable finding IDs across rounds. Task reviews now check code quality beyond acceptance criteria.
 
 **[v0.18.0](https://chorus-ai.dev/blog/chorus-v0.18.0-release/)** — Built-in `spec-lite` adds a lightweight, Git-native local spec workflow alongside OpenSpec. Live session anchors let daemon agents return replies to the initiating agent's existing Idea session.
@@ -46,16 +50,6 @@ The labels under each stage are the **permissions** an actor needs there — gra
 
 **[v0.17.0–0.17.1](https://github.com/Chorus-AIDLC/Chorus/releases/tag/v0.17.1)** — One CLI now installs and refreshes Chorus across your coding agents. Live daemon activity is visible directly on Ideas in Tracker, Graph, and detail views.
 
-**[v0.16.4](https://chorus-ai.dev/blog/chorus-v0.16.4-release/)** — DeepSeek Harness (dsh) is the sixth way to connect: the `@chorus-aidlc/chorus-dsh` bundle drops Chorus's skills, persona, and MCP config into any dsh profile. Interactive for now; daemon wake comes later.
-
-**[v0.16.1](https://chorus-ai.dev/blog/chorus-v0.16.1-release/)** — One `chorus daemon` now serves many independent agents at once — each with its own key, working directories, backend, and permissions via an `agents[]` array — and agents can hand work to each other by @-mention, with each wake landing in that agent's own project directory.
-
-**[v0.16.0](https://chorus-ai.dev/blog/chorus-v0.16.0-release/)** — A `docs` skill that points agents at the live docs site ([doc.chorus-ai.dev](https://doc.chorus-ai.dev)), so they answer from the current docs instead of reciting from memory.
-
-**[v0.15.0](https://chorus-ai.dev/blog/chorus-v0.15.0-release/)** — Project-level Agent working directories: each user can bind every Agent in a project to a host and cwd, browse only daemon-approved roots, and use the same target across assignment, wake, resume, and later turns without moving active sessions. Codex now persists its resumable backend thread ID separately and drops obsolete Chorus session-management steps.
-
-**[v0.14.1](https://chorus-ai.dev/blog/chorus-v0.14.1-release/)** — Amazon Kiro CLI is the fourth way to connect (Kiro CLI v2): a one-command Kiro plugin via `chorus agents add` and a `--agent kiro` daemon backend, plus daemon fixes.
-
 > Full changelog: [CHANGELOG.md](CHANGELOG.md)
 
 ---
@@ -65,7 +59,7 @@ The labels under each stage are the **permissions** an actor needs there — gra
 Two commands. No database, no Docker, no config files.
 
 ```bash
-npm install -g @chorus-aidlc/chorus@0.19.0
+npm install -g @chorus-aidlc/chorus@0.20.0
 chorus
 ```
 
@@ -75,6 +69,21 @@ Chorus starts with an embedded PostgreSQL (PGlite), runs migrations, and opens a
 
 To turn your local machine into an agent runtime that picks up assigned tasks, run `chorus daemon` → **[Daemon operations](https://doc.chorus-ai.dev/guides/daemon-operations/)** · **[Remote control](https://doc.chorus-ai.dev/guides/remote-control/)**.
 
+### Upgrade the CLI and plugins
+
+```bash
+chorus upgrade             # CLI only; `chorus update` is an alias
+chorus upgrade --plugins   # Also refresh configured agents' Chorus plugins
+```
+
+Self-upgrade supports the active **npm global installation** on Linux, macOS and Windows. It checks npm's prefix, resolves the latest stable release, avoids downgrades and verifies the installed version. Source checkouts, links, npx and other package-manager installations must use their own update workflow. CLI discovery, installation or verification failure stops plugin work.
+
+`--plugins` reads `~/.chorus/daemon.json`, including legacy single-agent records. Explicit Claude Code, Codex, Kiro and Pi types are processed even with wake disabled. Each record's home, config directory and PATH are respected; shared destinations update once. Only Chorus and required integration packages are refreshed, with existing credentials and unrelated settings preserved. Host CLIs must already be installed. Kiro templates come from the record's configured Chorus instance (its served version, which may lag npm); conflicting instance URLs for one destination are reported. Pi probes for targeted updates of Chorus and `pi-mcp-adapter`; older hosts without that capability report incomplete work, including partial installs, without updating unrelated extensions. Pinned versions, ranges and non-latest tags are preserved and reported incomplete; remove those constraints to allow latest updates.
+
+The command is noninteractive and reports each target. Exit **0** means all requested work completed (missing/empty configuration is a successful no-op); exit **1** means failure or incomplete work, including offline/unknown/untyped records, missing hosts or unsupported targeted updates. Later targets still run after a plugin failure; completed changes are not rolled back. Start new agent sessions and restart the daemon when convenient to activate updates—the command does not restart processes or interrupt sessions.
+
+npm installation has no automatic deadline or forced kill; it shows sanitized progress until npm exits. Queries remain time-limited. Failures include sanitized causes and exit status; permission failures suggest a user-owned Node installation such as nvm. Existing config backups use one `.chorus-upgrade.bak` per file, replaced on the next upgrade.
+
 ---
 
 ## See It in Action

package/README.zh.md

@@ -29,6 +29,10 @@ Idea ──> Proposal ──> [Document + Task DAG] ──> Execute ──> Veri
 
 ## 最近更新
 
+**[v0.20.0](https://chorus-ai.dev/zh/blog/chorus-v0.20.0-release/)**：daemon 后端改用 Codex App Server、Claude Code 双向 stream-json 和 Pi 原生 RPC，通过协议处理中断与执行状态。新增 `chorus upgrade`，支持 npm 全局安装的 CLI 自升级；加上 `--plugins` 可刷新已配置的 Claude Code、Codex、Kiro 和 Pi 集成。
+
+**[v0.19.1](https://chorus-ai.dev/zh/blog/chorus-v0.19.1-release/)**：新增轻量 Research，在 Idea 澄清和 Proposal 设计时查证关键事实；行内证据引用让结论直接关联来源。开发开始前，也可从 Tracker 发起补充调查。
+
 **[v0.19.0](https://chorus-ai.dev/zh/blog/chorus-v0.19.0-release/)**：借鉴 Cloudflare，明确 reviewer 职责、保留完整证据，用稳定 ID 逐轮追踪问题。任务审查默认检查验收标准之外的代码质量。
 
 **[v0.18.0](https://chorus-ai.dev/zh/blog/chorus-v0.18.0-release/)** — 内置 `spec-lite`，作为 OpenSpec 之外更轻量、可直接进 Git 的本地 Spec 管理方案。live session anchor 让 daemon Agent 的回复回到发起者已有的 Idea 会话。
@@ -37,16 +41,6 @@ Idea ──> Proposal ──> [Document + Task DAG] ──> Execute ──> Veri
 
 **[v0.17.0–0.17.1](https://github.com/Chorus-AIDLC/Chorus/releases/tag/v0.17.1)** — 一个 CLI 即可为各类编程 Agent 安装和更新 Chorus。现在还能在 Tracker、Graph 和 Idea 详情中直接看到 daemon 的实时活动。
 
-**[v0.16.4](https://chorus-ai.dev/zh/blog/chorus-v0.16.4-release/)** — DeepSeek Harness（dsh）成为第六种接入方式：`@chorus-aidlc/chorus-dsh` bundle 把 Chorus 的 skill、persona 和 MCP 配置装进任意 dsh profile。目前仅交互式使用，daemon 唤醒稍后支持。
-
-**[v0.16.1](https://chorus-ai.dev/zh/blog/chorus-v0.16.1-release/)** — 一个 `chorus daemon` 现在可以同时服务多个互相独立的 agent，每个都有自己的密钥、工作目录、后端和权限（通过 `agents[]` 配置）；agent 之间还能通过 @ 把活递给对方，每次唤醒都落在该 agent 自己的项目目录里。
-
-**[v0.16.0](https://chorus-ai.dev/zh/blog/chorus-v0.16.0-release/)** — 新增 `docs` skill，引导 Agent 查阅文档站点（[doc.chorus-ai.dev](https://doc.chorus-ai.dev)），基于当前文档作答，而不是凭记忆复述。
-
-**[v0.15.0](https://chorus-ai.dev/zh/blog/chorus-v0.15.0-release/)** — 项目级 Agent 工作目录：每位用户可以为项目中的每个 Agent 绑定主机和 cwd，只浏览 daemon 允许的目录，并让任务分配、唤醒、恢复和后续对话使用同一个执行位置，且不迁移进行中的会话。Codex 现在会单独保存可恢复的后端 thread ID，并移除不再需要的 Chorus session 管理步骤。
-
-**[v0.14.1](https://chorus-ai.dev/zh/blog/chorus-v0.14.1-release/)** — Amazon Kiro CLI 成为第四种接入方式（Kiro CLI v2）：通过 `chorus agents add` 一条命令安装的 Kiro 插件，以及 `--agent kiro` 的 daemon 后端，另有若干 daemon 修复。
-
 > 完整更新日志：[CHANGELOG.md](CHANGELOG.md)
 
 ---
@@ -56,7 +50,7 @@ Idea ──> Proposal ──> [Document + Task DAG] ──> Execute ──> Veri
 两条命令即可，无需数据库、无需 Docker、无需配置文件。
 
 ```bash
-npm install -g @chorus-aidlc/chorus@0.19.0
+npm install -g @chorus-aidlc/chorus@0.20.0
 chorus
 ```
 
@@ -66,6 +60,21 @@ Chorus 会自动启动内嵌 PostgreSQL (PGlite)、执行数据库迁移，然
 
 想把本地机器变成领取任务的 agent 运行时，运行 `chorus daemon` → **[Daemon 运维](https://doc.chorus-ai.dev/zh/guides/daemon-operations/)** · **[远程控制](https://doc.chorus-ai.dev/zh/guides/remote-control/)**。
 
+### 升级 CLI 和插件
+
+```bash
+chorus upgrade             # 仅升级 CLI；chorus update 为同义命令
+chorus upgrade --plugins   # 同时刷新已配置 Agent 的 Chorus 插件
+```
+
+自升级支持 Linux、macOS 和 Windows 上当前使用的 **npm 全局安装**：检查 npm prefix、查询最新稳定版本、避免降级，并在安装后验证版本。源码目录、链接、npx 和其他包管理器安装请使用各自的更新方式。CLI 检查、安装或版本验证失败后，不会继续更新插件。
+
+`--plugins` 读取 `~/.chorus/daemon.json`，兼容旧版单 Agent 配置。明确指定 Claude Code、Codex、Kiro、Pi 类型的记录都会处理，不受唤醒开关影响；按每条记录的 home、配置目录和 PATH 定位宿主，共享目标只更新一次。仅刷新 Chorus 及必需的集成依赖，保留已有凭证和无关设置，不安装宿主 CLI。Kiro 模板来自记录配置的 Chorus 实例（以该实例提供的版本为准，可能落后于 npm），共享目录对应不同实例时报告冲突。Pi 会探测是否支持定向更新 Chorus 和 `pi-mcp-adapter`；旧宿主不支持时报告未完成，部分安装也不会误报全部刷新，更不会更新其他扩展。固定版本、版本范围及非 latest 标签会保留并报告未完成；需移除这些约束后才能更新到最新。
+
+命令非交互执行并逐项汇总。退出码 **0** 表示请求全部完成（配置不存在或为空也算成功）；**1** 表示失败或未全部完成，包括 offline、未知或缺少类型的记录、宿主缺失及不支持定向更新。单个插件失败不影响后续目标，已完成的变更不回滚。更新后请开启新的 Agent 会话，并在方便时重启 daemon；命令本身不会重启进程或中断现有会话。
+
+npm 安装过程不设置自动超时或强制终止，会持续显示脱敏进度直到退出；查询仍保留超时。失败会显示脱敏原因和退出状态，权限问题会提示使用 nvm 等用户级 Node 安装。配置备份使用固定的 `.chorus-upgrade.bak` 文件，下次升级时替换，避免堆积。
+
 ---
 
 ## 界面预览

package/chorus.mjs

@@ -24,7 +24,7 @@ const __dirname = dirname(fileURLToPath(import.meta.url));
 // client commands that connect OUT to a remote Chorus server. Their modules are
 // lazy-imported so the server-launch path pays no startup cost.
 
-const SUBCOMMANDS = new Set(["daemon", "login", "mcp", "agents"]);
+const SUBCOMMANDS = new Set(["daemon", "login", "mcp", "agents", "upgrade", "update"]);
 
 // Client-subcommand arg parsing + help text live in cli/client-args.mjs so they
 // are pure and unit-testable (this entry module runs side effects at import).
@@ -54,6 +54,10 @@ function pkgVersion() {
 }
 
 async function runSubcommand(name, rest) {
+  if (name === "upgrade" || name === "update") {
+    const { runUpgrade } = await import("./cli/upgrade.mjs");
+    return runUpgrade(rest);
+  }
   // `agents` and `mcp` own their arg parsing + help (they handle `--help`
   // themselves), so they are dispatched before the shared client-flag/help
   // block below. (`chorus init` was renamed to `chorus agents add` — the bare
@@ -171,6 +175,8 @@ Chorus v${pkg.version} — AI Agent & Human collaboration platform
 
 USAGE
   chorus [options]                 Start the Chorus server (default)
+  chorus upgrade [--plugins]      Upgrade npm-global CLI; optionally refresh configured plugins
+  chorus update [--plugins]       Alias for upgrade (see 'chorus upgrade --help')
   chorus agents [list|add|remove]  Manage this machine's configured agents:
                                    list (default), add (detect + install plugin + seed
                                    creds; formerly 'chorus init'), remove <name|uuid>

package/cli/agent-cli-config.mjs

@@ -10,7 +10,7 @@ const PROTECTED = {
     short: "prcwv",
   },
   codex: {
-    long: "json experimental-json output-schema output-last-message color sandbox ask-for-approval full-auto approve-for-me not-so-yolo yolo dangerously-bypass-approvals-and-sandbox dangerously-bypass-hook-trust cd add-dir skip-git-repo-check ephemeral last all session resume fork profile remote remote-auth-token-env thread-source ignore-user-config ignore-rules",
+    long: "listen code-mode-host code-mode-host-url json experimental-json output-schema output-last-message color sandbox ask-for-approval full-auto approve-for-me not-so-yolo yolo dangerously-bypass-approvals-and-sandbox dangerously-bypass-hook-trust cd add-dir skip-git-repo-check ephemeral last all session resume fork profile remote remote-auth-token-env thread-source ignore-user-config ignore-rules",
     short: "soaCp",
   },
   kiro: {
@@ -180,7 +180,7 @@ export function validateAgentCliConfig(config = {}, type, label = "agent") {
     if (backend === "codex") {
       const c = codexConfigAt(args, i);
       if (c) {
-        if (!c.valid || /^(mcp_servers|sandbox[^.]*|approval_policy|approvals_reviewer|cwd|permissions|developer_instructions|model_instructions_file|experimental_instructions_file|base_instructions)(\.|$)/.test(c.key))
+        if (!c.valid || /^(listen|code_mode_host[^.]*|mcp_servers|sandbox[^.]*|approval_policy|approvals_reviewer|cwd|permissions|developer_instructions|model_instructions_file|experimental_instructions_file|base_instructions)(\.|$)/.test(c.key))
           invalid(label, `args[${i}]`, "has an invalid or managed Codex config key");
       }
     }
@@ -190,6 +190,32 @@ export function validateAgentCliConfig(config = {}, type, label = "agent") {
   return { args: [...args], env: { ...env } };
 }
 
+// Daemon-only translation. Foreground retains its literal argument planner.
+// App Server accepts global -c overrides, but not exec's model switch.
+export function codexAppServerArgs(args, label = "agent") {
+  const translated = [];
+  for (let i = 0; i < args.length;) {
+    const config = codexConfigAt(args, i);
+    if (config) {
+      translated.push(...args.slice(i, i + config.size));
+      i += config.size;
+      continue;
+    }
+    const option = optionAt("codex", args, i);
+    if (option?.flag === "--model" && !option.missing) {
+      const token = args[i];
+      const value = option.size === 2 ? args[i + 1]
+        : token.startsWith("--model=") ? token.slice(8)
+        : token.slice(2).replace(/^=/, "");
+      translated.push("-c", `model=${JSON.stringify(value)}`);
+      i += option.size;
+      continue;
+    }
+    invalid(label, `args[${i}]`, "is unsupported by Codex App Server; use model or permitted -c/--config settings, or explicit foreground passthrough");
+  }
+  return translated;
+}
+
 // Windows child environments are case-insensitive, unlike an ordinary JS object
 // (including injected test envs). Match Node's sorted-key selection if an inherited
 // object contains duplicates; overlayAgentEnv removes collisions for overrides.