@chorus-aidlc/chorus 0.7.0 → 0.8.0

package/.next/standalone/public/install-opencode.sh

@@ -0,0 +1,284 @@
+#!/usr/bin/env bash
+# Chorus + OpenCode one-shot plugin installer
+#
+# Usage:
+#   curl -fsSL https://<your-chorus>/install-opencode.sh | bash
+#
+# What this does (idempotent, safe to re-run):
+#   1. Verifies `opencode` CLI is installed.
+#   2. Adds "opencode-chorus" to the `plugin` array in
+#      ~/.config/opencode/opencode.json. Creates the file if missing.
+#      Preserves any existing plugins.
+#   3. Sets file permissions to 600.
+#
+# What this does NOT do:
+#   - Write to ~/.bashrc / ~/.zshrc. You must export CHORUS_URL and
+#     CHORUS_API_KEY yourself before launching opencode (the plugin reads
+#     process.env on startup).
+#   - Invoke jq / node / python. Pure POSIX awk/sed/grep only.
+
+set -euo pipefail
+
+# ---------- cosmetics ----------
+BOLD=$'\033[1m'; DIM=$'\033[2m'; GREEN=$'\033[32m'; YELLOW=$'\033[33m'; RED=$'\033[31m'; RESET=$'\033[0m'
+ok()   { printf "${GREEN}\xe2\x9c\x93${RESET} %s\n" "$*"; }
+warn() { printf "${YELLOW}!${RESET} %s\n" "$*" >&2; }
+die()  { printf "${RED}\xe2\x9c\x97${RESET} %s\n" "$*" >&2; exit 1; }
+hdr()  { printf "\n${BOLD}%s${RESET}\n" "$*"; }
+
+# ---------- config ----------
+PLUGIN_NAME="opencode-chorus"
+CONFIG_DIR="${OPENCODE_CONFIG_DIR:-$HOME/.config/opencode}"
+CONFIG_FILE="$CONFIG_DIR/opencode.json"
+BACKUP_FILE="$CONFIG_FILE.chorus-bak"
+
+# ---------- step 1: check opencode ----------
+hdr "1/3  Checking OpenCode CLI"
+if command -v opencode >/dev/null 2>&1; then
+  ok "Found $(opencode --version 2>/dev/null | head -1)"
+else
+  warn "opencode not found in PATH — install it first: https://opencode.ai/docs/"
+  warn "Proceeding to write the config anyway. OpenCode will pick it up on install."
+fi
+
+# ---------- step 2: ensure config dir ----------
+hdr "2/3  Updating $CONFIG_FILE"
+mkdir -p "$CONFIG_DIR"
+
+# Helper: print the manual instructions and exit 0 (non-fatal).
+print_manual_hint() {
+  warn "Could not automatically update $CONFIG_FILE."
+  warn "Please add \"$PLUGIN_NAME\" to the \"plugin\" array manually:"
+  cat >&2 <<HINT
+
+  {
+    "\$schema": "https://opencode.ai/config.json",
+    "plugin": ["$PLUGIN_NAME"${EXISTING_PLUGIN_HINT:-}]
+    ...
+  }
+
+HINT
+  exit 0
+}
+
+# ---------- Case A: file does not exist ----------
+if [ ! -f "$CONFIG_FILE" ]; then
+  cat > "$CONFIG_FILE" <<JSON
+{
+  "\$schema": "https://opencode.ai/config.json",
+  "plugin": ["$PLUGIN_NAME"]
+}
+JSON
+  chmod 600 "$CONFIG_FILE"
+  ok "Created $CONFIG_FILE with $PLUGIN_NAME"
+else
+  # File exists — back it up once.
+  if [ ! -f "$BACKUP_FILE" ]; then
+    cp "$CONFIG_FILE" "$BACKUP_FILE"
+    chmod 600 "$BACKUP_FILE"
+    ok "Backed up original config to $BACKUP_FILE"
+  fi
+
+  # Reject JSONC (comments). Presence of // or /* strongly suggests the file
+  # is hand-edited JSONC; our line-based awk would mangle it. Bail cleanly.
+  if grep -qE '^[[:space:]]*//|/\*' "$CONFIG_FILE"; then
+    warn "Detected // or /* in $CONFIG_FILE — looks like JSONC with comments."
+    print_manual_hint
+  fi
+
+  # Case C1: plugin array already contains opencode-chorus → no-op.
+  # Scope the check to the "plugin" array itself: a top-level occurrence of
+  # "opencode-chorus" outside that array (e.g. in a "lastInstalled" field)
+  # must not trigger the no-op shortcut.
+  plugin_contains_self() {
+    awk -v plugin="$PLUGIN_NAME" '
+      # Track whether we are currently inside the first "plugin" array.
+      # State machine:
+      #   0 = before the plugin key
+      #   1 = inside the plugin array (between its [ and matching ])
+      BEGIN { state = 0 }
+      state == 0 {
+        # Is the "plugin" key on this line?
+        if (match($0, /"plugin"[[:space:]]*:[[:space:]]*\[/)) {
+          # Consume the rest of the line starting at the [
+          rest = substr($0, RSTART + RLENGTH - 1)
+          state = 1
+          # Fall through to state == 1 handling for this rest.
+          $0 = rest
+        } else {
+          next
+        }
+      }
+      state == 1 {
+        # Look for the closing ] on this line (naive — good enough for
+        # standard JSON because plugin entries are plain strings).
+        close_pos = index($0, "]")
+        if (close_pos > 0) {
+          chunk = substr($0, 1, close_pos - 1)
+        } else {
+          chunk = $0
+        }
+        # Check for the quoted token inside the array chunk only.
+        if (index(chunk, "\"" plugin "\"") > 0) {
+          print "yes"
+          exit 0
+        }
+        if (close_pos > 0) exit 0
+      }
+    ' "$CONFIG_FILE"
+  }
+
+  if [ "$(plugin_contains_self)" = "yes" ]; then
+    ok "$PLUGIN_NAME already present in $CONFIG_FILE — nothing to do"
+  else
+    # Decide: Case B (no plugin key) vs Case C2 (plugin key exists without this plugin).
+    if grep -qE '"plugin"[[:space:]]*:' "$CONFIG_FILE"; then
+      # Case C2: insert into existing plugin array.
+      # Strategy: find the first "plugin" key, locate its array bracket pair,
+      # insert "opencode-chorus" before the closing ].
+      #
+      # Only handle the common cases where the array is on a single line or
+      # a multi-line array that has one entry per line. Otherwise bail to hint.
+      tmp="$(mktemp "${TMPDIR:-/tmp}/chorus-opencode.XXXXXX")"
+      if awk -v plugin="$PLUGIN_NAME" '
+        BEGIN { done = 0 }
+        # Single-line empty array: "plugin": []
+        !done && /"plugin"[[:space:]]*:[[:space:]]*\[[[:space:]]*\]/ {
+          sub(/\[[[:space:]]*\]/, "[\"" plugin "\"]")
+          done = 1
+          print
+          next
+        }
+        # Single-line non-empty array: "plugin": [ "foo", "bar" ]
+        !done && match($0, /"plugin"[[:space:]]*:[[:space:]]*\[[^\]]*\]/) {
+          line = $0
+          pre  = substr(line, 1, RSTART - 1)
+          match_text = substr(line, RSTART, RLENGTH)
+          post = substr(line, RSTART + RLENGTH)
+          # Insert before the closing ]
+          sub(/\][[:space:]]*$/, ", \"" plugin "\"]", match_text)
+          # If the match still ends in ] (no trailing whitespace stripped), fall through
+          print pre match_text post
+          done = 1
+          next
+        }
+        # Multi-line array opener: "plugin": [ (and not on same line closer)
+        !done && /"plugin"[[:space:]]*:[[:space:]]*\[[[:space:]]*$/ {
+          print
+          getline nextline
+          # Empty multi-line array: next line is just ]
+          if (nextline ~ /^[[:space:]]*\][[:space:]]*,?[[:space:]]*$/) {
+            print "    \"" plugin "\""
+            print nextline
+            done = 1
+            next
+          }
+          # Non-empty multi-line: emit entries verbatim until we hit the ]
+          buffer[++bn] = nextline
+          while ((getline nextline) > 0) {
+            if (nextline ~ /^[[:space:]]*\][[:space:]]*,?[[:space:]]*$/) {
+              # Last existing entry may not have trailing comma; add one.
+              last = buffer[bn]
+              if (last !~ /,[[:space:]]*$/) {
+                sub(/[[:space:]]*$/, ",", buffer[bn])
+              }
+              for (i = 1; i <= bn; i++) print buffer[i]
+              # Insert new entry before the closing ]
+              # Determine indentation from first buffered entry.
+              match(buffer[1], /^[[:space:]]*/)
+              indent = substr(buffer[1], 1, RLENGTH)
+              print indent "\"" plugin "\""
+              print nextline
+              done = 1
+              bn = 0
+              break
+            }
+            buffer[++bn] = nextline
+          }
+          next
+        }
+        { print }
+        END {
+          if (!done) exit 2
+        }
+      ' "$CONFIG_FILE" > "$tmp"; then
+        mv "$tmp" "$CONFIG_FILE"
+        chmod 600 "$CONFIG_FILE"
+        ok "Added $PLUGIN_NAME to existing \"plugin\" array"
+      else
+        rm -f "$tmp"
+        warn "The \"plugin\" key exists but I could not safely determine where to insert the new entry."
+        EXISTING_PLUGIN_HINT=", ...your existing entries..."
+        print_manual_hint
+      fi
+    else
+      # Case B: no plugin key in file → inject it.
+      # We look for the first top-level "{" then insert `"plugin": [...]` on the next line.
+      # Safer: look for the first line containing just "{" optionally with whitespace.
+      tmp="$(mktemp "${TMPDIR:-/tmp}/chorus-opencode.XXXXXX")"
+      if awk -v plugin="$PLUGIN_NAME" '
+        BEGIN { inserted = 0 }
+        !inserted && /^[[:space:]]*\{[[:space:]]*$/ {
+          print
+          print "  \"plugin\": [\"" plugin "\"],"
+          inserted = 1
+          next
+        }
+        { print }
+        END { if (!inserted) exit 2 }
+      ' "$CONFIG_FILE" > "$tmp"; then
+        mv "$tmp" "$CONFIG_FILE"
+        chmod 600 "$CONFIG_FILE"
+        ok "Added \"plugin\" field with $PLUGIN_NAME to $CONFIG_FILE"
+      else
+        rm -f "$tmp"
+        warn "Could not find a line with just \"{\" to inject the plugin array."
+        print_manual_hint
+      fi
+    fi
+  fi
+fi
+
+# ---------- step 3: reminders ----------
+hdr "3/3  Final reminders"
+
+# Environment check — read-only warning, don't export.
+missing_env=""
+if [ -z "${CHORUS_URL:-}" ]; then
+  missing_env="$missing_env CHORUS_URL"
+fi
+if [ -z "${CHORUS_API_KEY:-}" ]; then
+  missing_env="$missing_env CHORUS_API_KEY"
+fi
+
+if [ -n "$missing_env" ]; then
+  warn "The following environment variables are not set in this shell:$missing_env"
+  warn "The plugin reads them on OpenCode startup. Please export them in your shell rc:"
+  cat >&2 <<'HINT'
+
+  export CHORUS_URL="https://<your-chorus-instance>"
+  export CHORUS_API_KEY="cho_..."
+
+HINT
+  warn "Then re-source your shell rc, or launch opencode from a shell where they are exported."
+else
+  ok "CHORUS_URL and CHORUS_API_KEY are set in this shell"
+fi
+
+hdr "Done."
+cat <<'NEXT'
+Start OpenCode — Bun will fetch opencode-chorus on first launch:
+
+  opencode
+
+Then in OpenCode, ask the agent:
+
+  check in to chorus
+
+If the plugin fails to load, clear the package cache and retry:
+
+  rm -rf ~/.cache/opencode/packages/opencode-chorus@latest
+
+To roll back this change:
+NEXT
+printf "  mv %s %s\n\n" "$BACKUP_FILE" "$CONFIG_FILE"

package/README.md

@@ -15,7 +15,7 @@
 
 <p align="center"><a href="README.zh.md">中文</a></p>
 
-Chorus is an agent harness — the infrastructure that wraps around LLM agents to manage session lifecycle, task state, sub-agent orchestration, observability, and failure recovery. It lets multiple AI Agents (PM, Developer, Admin) and humans collaborate through the full workflow from requirements to delivery.
+Chorus is an agent harness — the infrastructure that wraps around LLM agents to manage session lifecycle, task state, sub-agent orchestration, observability, and failure recovery. It lets multiple AI Agents (with fine-grained, configurable permissions) and humans collaborate through the full workflow from requirements to delivery.
 
 Inspired by the **[AI-DLC (AI-Driven Development Lifecycle)](https://aws.amazon.com/blogs/devops/ai-driven-development-life-cycle/)** methodology. Core philosophy: **Reversed Conversation** — AI proposes, humans verify.
 
@@ -26,15 +26,20 @@ Inspired by the **[AI-DLC (AI-Driven Development Lifecycle)](https://aws.amazon.
 ```
 Idea ──> Proposal ──> [Document + Task DAG] ──> Execute ──> Verify ──> Done
   ^          ^               ^                     ^          ^         ^
-Human     PM Agent       PM Agent              Dev Agent    Admin     Admin
-creates   analyzes       drafts PRD            codes &      reviews   closes
-          & plans        & tasks               reports      & verifies
+Human     idea:write     proposal:write         task:write   *:admin    *:admin
+creates   + elaborate    + drafts                + reports   + verifies + closes
 ```
 
+The labels under each stage are the **permissions** an actor needs at that stage — granted to a human, an Agent (preset or Custom), or both. There are no fixed roles; any combination of the 5 × 3 permission matrix is possible. See [`docs/PERMISSIONS.md`](docs/PERMISSIONS.md).
+
 ---
 
 ## What's New
 
+**[v0.8.0](https://chorus-ai.dev/blog/chorus-v0.8.0-release/)** — OpenSpec-aware mode (Claude Code): auto-activates when an `openspec/` directory and the `openspec` CLI are both present, adds `/opsx/{explore,propose,apply,archive}` and a post-verify archive-trigger hook.
+
+**[v0.7.0](https://chorus-ai.dev/blog/chorus-v0.7.0-release/)** — Fine-grained agent permissions: 5 resources × 3 actions grid replaces the PM/Developer/Admin three-way choice, with presets + a Custom option for free combination.
+
 **[v0.6.7](https://chorus-ai.dev/blog/chorus-v0.6.7-release/)** — Chorus plugin for Codex CLI (one-command installer), workspace picker when one email belongs to multiple Companies, per-client connect guides.
 
 **[v0.6.6](https://chorus-ai.dev/blog/chorus-v0.6.6-release/)** — npm one-click install (`npx @chorus-aidlc/chorus`), document export (MD/PDF/Word), proposal revoke, faster agent checkin with work status at a glance.
@@ -153,6 +158,7 @@ A Cmd+K command palette for searching across all 6 entity types (Tasks, Ideas, P
 - **Task DAG** — Dependency modeling, cycle detection, and interactive visualization
 - **Kanban** — Real-time task flow with Worker badges and agent presence
 - **Multi-Agent Collaboration** — Claude Code Agent Teams (Swarm Mode) for parallel execution
+- **Fine-Grained Agent Permissions** — 5 resources × 3 actions grid with preset + custom combinations ([details](docs/PERMISSIONS.md))
 - **Chorus Plugin** — Lifecycle hooks automate session create/close, heartbeats, and context injection
 - **Requirements Elaboration** — Structured Q&A rounds before proposal creation
 - **Proposal Approval Flow** — PM drafts, Admin approves, drafts materialize into real entities
@@ -178,7 +184,7 @@ A Cmd+K command palette for searching across all 6 entity types (Tasks, Ideas, P
 │  └───────────────────────────────────────────────────────────┘   │
 │                                                                  │
 │  ┌── API Layer ──────────────────────────────────────────────┐   │
-│  │  /api/mcp  — MCP HTTP Streamable (50+ tools, role-based)  │   │
+│  │  /api/mcp  — MCP Streaming (50+ tools, permission-gated)  │   │
 │  │  /api/*    — REST API (Web UI + SSE push)                 │   │
 │  └───────────────────────────────────────────────────────────┘   │
 │                                                                  │
@@ -191,8 +197,10 @@ A Cmd+K command palette for searching across all 6 entity types (Tasks, Ideas, P
 │  └───────────────────────────────────────────────────────────┘   │
 └──────────────────────────────────────────────────────────────────┘
      ↑              ↑              ↑              ↑
-  PM Agent    Developer Agent  Admin Agent      Human
-   (LLM)         (LLM)          (LLM)        (Browser)
+  Agent w/      Agent w/       Agent w/         Human
+  idea+proposal  task:write    *:admin perms   (Browser)
+   :write perms    perms      (proxy approval)
+   (LLM)          (LLM)         (LLM)
                      │
           ┌──────────▼──────────┐   ┌─────────────────────┐
           │  PostgreSQL + Prisma │   │  Redis (optional)   │
@@ -290,7 +298,7 @@ The interactive installer provisions VPC, Aurora Serverless v2, ElastiCache Serv
 
 ### Connect AI Agents
 
-The fastest path is the in-app setup wizard: open the Web UI, go to **Settings → Setup Guide → Open setup guide**, and follow the step-by-step instructions for your client (Claude Code, Codex, OpenClaw, or other agents). The wizard creates the API key for you, shows the exact commands, and walks through verifying the connection.
+The fastest path is the in-app setup wizard: open the Web UI, go to **Settings → Setup Guide → Open setup guide**, and follow the step-by-step instructions for your client (Claude Code, Codex, OpenCode, OpenClaw, or other agents). The wizard creates the API key for you, shows the exact commands, and walks through verifying the connection.
 
 If you'd rather read the full docs:
 
@@ -298,8 +306,11 @@ If you'd rather read the full docs:
 |--------|-------|
 | Claude Code | [CONNECT_CLAUDE_CODE.md](docs/CONNECT_CLAUDE_CODE.md) |
 | Codex CLI | [CONNECT_CODEX.md](docs/CONNECT_CODEX.md) |
+| OpenCode † | [CONNECT_OPENCODE.md](docs/CONNECT_OPENCODE.md) |
 | Other MCP agents (Cursor, Continue, custom, …) | [CONNECT_OTHER_AGENTS.md](docs/CONNECT_OTHER_AGENTS.md) |
 
+† OpenCode support is provided by the community-maintained [`opencode-chorus`](https://github.com/etnperlong/opencode-chorus) plugin (npm: [`opencode-chorus`](https://www.npmjs.com/package/opencode-chorus)), authored by [@etnperlong](https://github.com/etnperlong). Thanks!
+
 Create API Keys in the Web UI under **Settings → Agents → Create API Key**. Keys start with `cho_` and are shown only once.
 
 ![Create API Key](docs/images/create-key.png)
@@ -310,8 +321,29 @@ Create API Keys in the Web UI under **Settings → Agents → Create API Key**.
 
 | Method | Location | Use Case |
 |--------|----------|----------|
-| **Plugin-embedded** | `public/chorus-plugin/skills/chorus/` | Claude Code + Plugin, automated Sessions |
-| **Standalone** | `public/skill/` (served at `/skill/`) | Any Agent, manual Session management |
+| **Plugin-embedded (Claude Code)** | `public/chorus-plugin/skills/` | Claude Code + Chorus plugin, automated Sessions and lifecycle hooks |
+| **Plugin-embedded (Codex CLI)** | `plugins/chorus/skills/` | Codex CLI + Chorus plugin, ported skills with `$`-prefixed slash commands |
+| **Standalone** | `public/skill/` (served at `/skill/`) | Any other MCP-capable Agent (Cursor, Continue, custom), manual Session management |
+
+### OpenSpec mode (opt-in, plugin 0.8.1+)
+
+PM agents that have the [OpenSpec](https://github.com/Fission-AI/OpenSpec)
+CLI installed can author proposals in a structured `proposal.md` +
+`design.md` + `specs/<capability>/spec.md` layout. Local files are the
+working copy and Chorus `documentDrafts` are the mirror; reviewers see a
+predictable shape (`## ADDED Requirements`, `### Requirement:`,
+`#### Scenario:`) instead of free-form Markdown. A PostToolUse hook on
+`chorus_admin_verify_task` injects an `openspec archive <slug>` reminder
+when the last task of an OpenSpec idea is verified, so finalized specs
+are merged into the long-term spec set right after sign-off. The mode is
+strictly opt-in: when `openspec` is not installed, behavior is unchanged.
+Master switch on Claude Code is `enableOpenSpec` (plugin userConfig,
+default `true`); both clients also honor `CHORUS_OPENSPEC_MODE=off`. No
+new MCP tools or schema changes ship in this mode; the canonical skill
+reuses the existing `chorus_pm_*` draft and document tools, with mirror
+calls routed through the `chorus-api.sh` wrapper to keep multi-thousand-
+line markdown out of LLM context. See
+[OPENSPEC_MODE.md](docs/OPENSPEC_MODE.md) for the full guide.
 
 ---
 
@@ -322,7 +354,9 @@ Create API Keys in the Web UI under **Settings → Agents → Create API Key**.
 | [PRD](docs/PRD_Chorus.md) | Product Requirements Document |
 | [Architecture](docs/ARCHITECTURE.md) | Technical Architecture Document |
 | [MCP Tools](docs/MCP_TOOLS.md) | MCP Tools Reference |
+| [Permissions](docs/PERMISSIONS.md) | Agent permission model (5 × 3 matrix, presets, Custom mode) |
 | [Chorus Plugin](docs/chorus-plugin.md) | Plugin Design & Hook Documentation |
+| [OpenSpec Mode](docs/OPENSPEC_MODE.md) | Opt-in OpenSpec authoring mode for PM agents (Plugin 0.8.1+) |
 | [Search](docs/SEARCH.md) | Global Search Technical Design |
 | [AI-DLC Gap Analysis](docs/AIDLC_GAP_ANALYSIS.md) | AI-DLC Methodology Gap Analysis |
 | [AIG Implementation Plan](docs/CHORUS_AIG_PLAN.md) | Agent transparency roadmap |

package/README.zh.md

@@ -6,7 +6,7 @@
 
 <p align="center"><a href="README.md">English</a></p>
 
-Chorus 是一个 Agent Harness——包裹在 LLM 外面的基础设施层，负责管理会话生命周期、任务状态、子 Agent 编排、可观测性和故障恢复。它让多个 AI Agent（PM、Developer、Admin）和人类在同一平台上协作，完成从需求到交付的全流程。
+Chorus 是一个 Agent Harness——包裹在 LLM 外面的基础设施层，负责管理会话生命周期、任务状态、子 Agent 编排、可观测性和故障恢复。它让多个具备细粒度权限配置的 AI Agent 和人类在同一平台上协作，完成从需求到交付的全流程。
 
 受 **[AI-DLC（AI-Driven Development Lifecycle）](https://aws.amazon.com/blogs/devops/ai-driven-development-life-cycle/)** 方法论启发。核心理念：**Reversed Conversation**——AI 提议，人类验证。
 
@@ -17,15 +17,20 @@ Chorus 是一个 Agent Harness——包裹在 LLM 外面的基础设施层，负
 ```
 Idea ──> Proposal ──> [Document + Task DAG] ──> Execute ──> Verify ──> Done
   ^          ^               ^                     ^          ^         ^
-Human     PM Agent       PM Agent              Dev Agent    Admin     Admin
-creates   analyzes       drafts PRD            codes &      reviews   closes
-          & plans        & tasks               reports      & verifies
+人类      idea:write     proposal:write         task:write   *:admin    *:admin
+提出      + 需求澄清     + 起草 PRD/任务         + 报告进度   + 验收     + 关闭
 ```
 
+每个阶段下方标的是「执行该阶段所需的权限」，可以由人类、Agent（预设或 Custom）或两者持有。没有固定角色，5 × 3 权限矩阵的任意组合都合法，详见 [`docs/PERMISSIONS.md`](docs/PERMISSIONS.md)（英文）。
+
 ---
 
 ## 最近更新
 
+**[v0.8.0](https://chorus-ai.dev/zh/blog/chorus-v0.8.0-release/)** — OpenSpec-aware 模式（仅 Claude Code）：当仓库下同时存在 `openspec/` 目录和 `openspec` CLI 时自动启用，新增 `/opsx/{explore,propose,apply,archive}` 与 task verify 后的 archive-trigger 钩子。
+
+**[v0.7.0](https://chorus-ai.dev/zh/blog/chorus-v0.7.0-release/)** — 细粒度 Agent 权限：5 类资源 × 3 个动作组成的网格，取代 PM / Developer / Admin 三选一。保留原有预设，新增 Custom 选项自由组合。
+
 **[v0.6.7](https://chorus-ai.dev/zh/blog/chorus-v0.6.7-release/)** — Codex CLI 版 Chorus 插件（一条命令装完）、同一邮箱属于多个 Company 时的工作区选择器、每种客户端的接入文档。
 
 **[v0.6.6](https://chorus-ai.dev/zh/blog/chorus-v0.6.6-release/)** — npm 一键安装（`npx @chorus-aidlc/chorus`）、文档导出（MD/PDF/Word）、Proposal 撤回、优化 Agent Checkin 快速获取工作状态。
@@ -144,6 +149,7 @@ Cmd+K 命令面板，支持跨 6 种实体类型搜索。支持范围筛选（
 - **任务 DAG** — 依赖建模、环检测、交互式可视化
 - **Kanban** — 实时任务流转，Worker 徽标与 Agent Presence
 - **Multi-Agent 协作** — Claude Code Agent Teams (Swarm Mode) 并行执行
+- **细粒度 Agent 权限** — 5 类资源 × 3 个动作组成的权限网格，支持预设 + 自定义组合（[详细说明](docs/PERMISSIONS.md) · 英文）
 - **Chorus Plugin** — 生命周期钩子自动管理 Session 创建/关闭、心跳、上下文注入
 - **需求澄清** — Proposal 创建前的结构化问答轮次
 - **Proposal 审批流** — PM 起草，Admin 审批，草稿物化为正式实体
@@ -169,7 +175,7 @@ Cmd+K 命令面板，支持跨 6 种实体类型搜索。支持范围筛选（
 │  └───────────────────────────────────────────────────────────┘   │
 │                                                                  │
 │  ┌── API Layer ──────────────────────────────────────────────┐   │
-│  │  /api/mcp  — MCP HTTP Streamable (50+ tools, role-based)  │   │
+│  │  /api/mcp  — MCP Streaming (50+ tools, permission-gated)  │   │
 │  │  /api/*    — REST API (Web UI + SSE push)                 │   │
 │  └───────────────────────────────────────────────────────────┘   │
 │                                                                  │
@@ -182,8 +188,10 @@ Cmd+K 命令面板，支持跨 6 种实体类型搜索。支持范围筛选（
 │  └───────────────────────────────────────────────────────────┘   │
 └──────────────────────────────────────────────────────────────────┘
      ↑              ↑              ↑              ↑
-  PM Agent    Developer Agent  Admin Agent      Human
-   (LLM)         (LLM)          (LLM)        (Browser)
+  Agent w/      Agent w/       Agent w/         人类
+  idea+proposal  task:write    *:admin perms   （浏览器）
+   :write perms    perms      （代理人类审批）
+   (LLM)          (LLM)         (LLM)
                      │
           ┌──────────▼──────────┐   ┌─────────────────────┐
           │  PostgreSQL + Prisma │   │  Redis（可选）       │
@@ -281,7 +289,7 @@ PGlite 在端口 5433 运行嵌入式 PostgreSQL。数据存储在 `.pglite/`，
 
 ### 连接 AI Agent
 
-最快的方式是用应用内的 setup 向导：打开 Web UI，进入 **Settings → Setup Guide → 打开设置向导**，按照向导给出的分步指引接入自己的客户端（Claude Code、Codex、OpenClaw 或其他 agent）。向导会帮你创建 API Key、展示完整命令，并引导你验证连接。
+最快的方式是用应用内的 setup 向导：打开 Web UI，进入 **Settings → Setup Guide → 打开设置向导**，按照向导给出的分步指引接入自己的客户端（Claude Code、Codex、OpenCode、OpenClaw 或其他 agent）。向导会帮你创建 API Key、展示完整命令，并引导你验证连接。
 
 如果偏好文档：
 
@@ -289,8 +297,11 @@ PGlite 在端口 5433 运行嵌入式 PostgreSQL。数据存储在 `.pglite/`，
 |--------|---------|
 | Claude Code | [CONNECT_CLAUDE_CODE.zh.md](docs/CONNECT_CLAUDE_CODE.zh.md) |
 | Codex CLI | [CONNECT_CODEX.zh.md](docs/CONNECT_CODEX.zh.md) |
+| OpenCode † | [CONNECT_OPENCODE.zh.md](docs/CONNECT_OPENCODE.zh.md) |
 | 其他 MCP agent（Cursor / Continue / 自研等） | [CONNECT_OTHER_AGENTS.zh.md](docs/CONNECT_OTHER_AGENTS.zh.md) |
 
+† OpenCode 的接入由社区维护的 [`opencode-chorus`](https://github.com/etnperlong/opencode-chorus) 插件提供（npm: [`opencode-chorus`](https://www.npmjs.com/package/opencode-chorus)），作者 [@etnperlong](https://github.com/etnperlong)，特此感谢！
+
 在 Web UI 的 **Settings → Agents → Create API Key** 创建 API Key。Key 以 `cho_` 开头，仅在创建时显示一次。
 
 ![Create API Key](docs/images/create-key.png)
@@ -301,8 +312,9 @@ PGlite 在端口 5433 运行嵌入式 PostgreSQL。数据存储在 `.pglite/`，
 
 | 方式 | 位置 | 适用场景 |
 |------|------|---------|
-| **Plugin 内嵌** | `public/chorus-plugin/skills/chorus/` | Claude Code + Plugin，Session 自动化 |
-| **独立分发** | `public/skill/`（`/skill/` 路径静态托管）| 任何 Agent，手动 Session 管理 |
+| **Plugin 内嵌（Claude Code）** | `public/chorus-plugin/skills/` | Claude Code + Chorus 插件，Session 自动化与生命周期 hook |
+| **Plugin 内嵌（Codex CLI）** | `plugins/chorus/skills/` | Codex CLI + Chorus 插件，移植版技能（`$` 前缀斜杠命令）|
+| **独立分发** | `public/skill/`（`/skill/` 路径静态托管）| 其他 MCP 客户端（Cursor / Continue / 自研），手动 Session 管理 |
 
 ---
 
@@ -313,7 +325,9 @@ PGlite 在端口 5433 运行嵌入式 PostgreSQL。数据存储在 `.pglite/`，
 | [PRD](docs/PRD_Chorus.md) | 产品需求文档 |
 | [Architecture](docs/ARCHITECTURE.md) | 技术架构文档 |
 | [MCP Tools](docs/MCP_TOOLS.md) | MCP 工具参考 |
+| [Permissions](docs/PERMISSIONS.md) | Agent 权限模型（5 × 3 矩阵 + 预设 + Custom） |
 | [Chorus Plugin](docs/chorus-plugin.md) | 插件设计与 Hook 说明 |
+| [OpenSpec Mode](docs/OPENSPEC_MODE.md) | OpenSpec 模式（Plugin 0.8.1+，opt-in） |
 | [Search](docs/SEARCH.md) | 全局搜索技术设计 |
 | [AI-DLC Gap Analysis](docs/AIDLC_GAP_ANALYSIS.md) | AI-DLC 方法论差距分析 |
 | [AIG Implementation Plan](docs/CHORUS_AIG_PLAN.md) | Agent 透明度路线图 |

package/chorus.mjs

@@ -12,7 +12,7 @@ import {
 import { createConnection } from "node:net";
 import { homedir } from "node:os";
 import { dirname, join, resolve } from "node:path";
-import { fileURLToPath } from "node:url";
+import { fileURLToPath, pathToFileURL } from "node:url";
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
 
@@ -71,11 +71,13 @@ OPTIONS
   -d, --data-dir <path>    Data directory for PGlite    (default: ~/.chorus-data, env: CHORUS_DATA_DIR)
       --hostname <host>    Bind address                 (default: 0.0.0.0)
       --pglite-port <port> Embedded PGlite port         (default: 5433, env: CHORUS_PGLITE_PORT)
+      --use-pglite[=BOOL]  Use embedded PGlite           (default: true; pass =false for external Postgres)
   -h, --help               Show this help message
   -v, --version            Show version number
 
 ENVIRONMENT VARIABLES
-  DATABASE_URL             External PostgreSQL URL (skips embedded PGlite)
+  CHORUS_USE_PGLITE        Set to "0" to disable embedded PGlite (default: enabled)
+  DATABASE_URL             External PostgreSQL URL (required when --use-pglite=false)
   REDIS_URL                Redis URL for multi-instance pub/sub
   DEFAULT_USER             Auto-create login user email
   DEFAULT_PASSWORD         Auto-create login user password
@@ -83,10 +85,10 @@ ENVIRONMENT VARIABLES
   COOKIE_SECURE            Set to "true" for HTTPS deployments
 
 EXAMPLES
-  chorus                                     # Start with defaults
+  chorus                                     # Embedded PGlite (default)
   chorus --port 3000                         # Custom port
   chorus --data-dir /var/lib/chorus          # Custom data directory
-  DATABASE_URL=postgres://... chorus         # Use external PostgreSQL
+  DATABASE_URL=postgres://... chorus --use-pglite=false   # External PostgreSQL
 `);
   process.exit(0);
 }
@@ -158,14 +160,40 @@ function ensureSecret() {
 let pgliteProcess = null;
 
 async function main() {
-  // 1. Ensure data directory
-  mkdirSync(join(dataDir, "pglite"), { recursive: true });
+  // 1. Determine database mode
+  // --use-pglite means "the database is PGlite-backed" (local or remote).
+  // It controls pg.Pool sizing (max=1 to avoid the @electric-sql/pglite-socket
+  // cross-handler race), independently of whether the PGlite process is
+  // local or remote.
+  //
+  // Whether to start a local embedded PGlite is decided by DATABASE_URL:
+  //   - If DATABASE_URL is set, treat it as a pre-existing DB (PGlite or
+  //     real Postgres) and connect to it.
+  //   - Otherwise, --use-pglite=true (default) starts an embedded PGlite.
+  const usePgliteFlag = getArg("--use-pglite");
+  const envFlag = process.env.CHORUS_USE_PGLITE;
+  const usePglite =
+    usePgliteFlag === "false" || envFlag === "0" || envFlag === "false"
+      ? false
+      : true;
+  const startEmbeddedPglite = usePglite && !process.env.DATABASE_URL;
+
+  if (!usePglite && !process.env.DATABASE_URL) {
+    console.error(
+      "ERROR: --use-pglite=false requires DATABASE_URL to be set."
+    );
+    process.exit(1);
+  }
 
-  // 2. Determine database mode
-  const useExternalDb = !!process.env.DATABASE_URL;
+  // 2. Signal child processes to pin pg.Pool max=1 when using any PGlite backend.
+  if (usePglite) {
+    process.env.CHORUS_USE_PGLITE = "1";
+  }
 
-  if (!useExternalDb) {
-    // Start embedded PGlite
+  // 3. Start embedded PGlite if requested (no DATABASE_URL pointing at an
+  //    external instance).
+  if (startEmbeddedPglite) {
+    mkdirSync(join(dataDir, "pglite"), { recursive: true });
     console.log(`Starting embedded PostgreSQL (PGlite) on port ${PGLITE_PORT}...`);
 
     // @electric-sql/pglite-socket does not expose `./dist/scripts/server.js`
@@ -253,13 +281,26 @@ async function main() {
   console.log("");
   console.log(`  URL:       http://${hostname === "0.0.0.0" ? "localhost" : hostname}:${port}`);
   console.log(`  Data:      ${dataDir}`);
-  console.log(`  Database:  ${useExternalDb ? "external PostgreSQL" : "PGlite (embedded)"}`);
+  const dbLabel = usePglite
+    ? (startEmbeddedPglite
+        ? "PGlite (embedded, pg.Pool max=1)"
+        : "PGlite (external, pg.Pool max=1)")
+    : "external PostgreSQL";
+  console.log(`  Database:  ${dbLabel}`);
   console.log(`  Redis:     ${process.env.REDIS_URL ? "connected" : "disabled (in-memory EventBus)"}`);
   const maskedPassword = process.env.DEFAULT_PASSWORD === "chorus"
     ? "chorus"
     : "****";
   console.log(`  Login:     ${process.env.DEFAULT_USER} / ${maskedPassword}`);
   console.log("");
+  if (usePglite) {
+    console.log("  ⚠ PGlite mode pins pg.Pool to max=1 to avoid a cross-handler");
+    console.log("    race in @electric-sql/pglite-socket. Concurrent DB traffic is");
+    console.log("    serialized — fine for local single-user use, but for multi-user");
+    console.log("    or production deployments use a real PostgreSQL: pass");
+    console.log("    --use-pglite=false and set DATABASE_URL.");
+    console.log("");
+  }
 
   // 7. Ensure static assets are accessible inside standalone directory
   // next build puts .next/static/ and public/ at the project root, but
@@ -279,8 +320,11 @@ async function main() {
   }
 
   // 8. Start Next.js standalone server
+  // Use pathToFileURL — on Windows, dynamic import() rejects bare drive paths
+  // like "C:\…\server.js" with ERR_UNSUPPORTED_ESM_URL_SCHEME. file:// URLs
+  // work on every platform.
   process.chdir(standaloneDir);
-  await import(join(standaloneDir, "server.js"));
+  await import(pathToFileURL(join(standaloneDir, "server.js")).href);
 }
 
 // ---------------------------------------------------------------------------

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chorus-aidlc/chorus",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "description": "The Agent Harness for AI-Human Collaboration — session lifecycle, task state, sub-agent orchestration, observability, and failure recovery",
   "homepage": "https://github.com/Chorus-AIDLC/Chorus",
   "repository": {