npm - @chorus-aidlc/chorus - Versions diffs - 0.14.0 → 0.14.2 - Mend

@chorus-aidlc/chorus 0.14.0 → 0.14.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (592) hide show

package/README.ko.md CHANGED Viewed

@@ -1,5 +1,5 @@
 <p align="center">
-  <img src="docs/images/chorus-slug.png" alt="Chorus" width="240" />
+  <img src="packages/landing/public/images/chorus-slug.png" alt="Chorus" width="240" />
 </p>
 <p align="center"><strong>AI-인간 협업을 위한 Agent Harness</strong></p>
@@ -36,6 +36,8 @@ Idea ──> Proposal ──> [Document + Task DAG] ──> Execute ──> Veri
 ## 최근 업데이트
+**[v0.14.1](https://chorus-ai.dev/blog/chorus-v0.14.1-release/)** — Amazon Kiro CLI가 네 번째 연결 방식이 되었습니다(Kiro CLI v2): 명령 한 줄로 설치하는 `install-kiro.sh` 플러그인과 `--agent kiro` 데몬 백엔드, 여기에 몇 가지 데몬 수정.
 **[v0.14.0](https://chorus-ai.dev/blog/chorus-v0.14.0-release/)** — 앱 전체 다크 모드(라이트 / 다크 / 시스템). 참고 자료를 어떤 아이디어·제안·작업에도 첨부할 수 있고, 인라인으로도 MCP를 통해서도 읽을 수 있습니다. 한국어와 일본어 추가(한국어는 커뮤니티 기여). 그룹화를 위한 **테마** 아이디어, 그리고 데몬의 개발 시작 / Yolo 버튼, 대화식 아이디어 입력, 크래시 복구, `chorus daemon install`.
 **[v0.13.0](https://chorus-ai.dev/blog/chorus-v0.13.0-release/)** — 프로젝트별 리소스 마인드맵: 새로운 Graph 뷰가 각 프로젝트의 아이디어·제안·문서·작업을 프로젝트 자체 구조에서 생성한 하나의 접을 수 있는 트리로 엮습니다. 모든 카드에 현재 상태가 표시되며(아이디어는 아이디어 트래커가 사용하는 파생 파이프라인 상태를 보여줍니다), 제목 검색은 모든 일치 항목까지의 경로를 자동으로 펼쳐 하이라이트/디밍하고 이전/다음 탐색을 제공합니다. 동일한 줌/팬 캔버스가 데스크톱과 모바일 모두에서 렌더링됩니다(핀치 + 더블탭).
@@ -178,7 +180,7 @@ CHORUS_DAEMON_CWDS="~/work/repo-a:~/work/repo-b" chorus daemon   # 또는 환경
 ### 원격 에이전트 웨이크 — 디렉터리로 디스패치하고 실행을 지켜보기
-![Remote Agent Wake](docs/images/agent-daemon-wake.gif)
+![Remote Agent Wake](packages/landing/public/images/agent-daemon-wake.gif)
 아이디어를 원격 에이전트의 특정 디렉터리에 배정한 다음 대화를 열면, 로컬 Claude Code가 작업을 이어받아 실시간으로 실행하는 모습을 볼 수 있습니다 — 터미널도, 수동 재개도 필요 없습니다.
@@ -190,7 +192,7 @@ Chorus는 프로젝트 전체를 마인드맵으로 자동 정리합니다 —
 ### 제안 — AI 에이전트가 실시간으로 계획을 생성
-![Proposal Presence](docs/images/proposal-presence.gif)
+![Proposal Presence](packages/landing/public/images/proposal-presence.gif)
 PM 에이전트가 요구사항을 분석하고 PRD와 작업 DAG를 포함한 제안을 생성하는 모습을 볼 수 있습니다 — 에이전트 활동을 보여주는 실시간 프레즌스 인디케이터와 함께 말이죠.
@@ -202,37 +204,37 @@ PM 에이전트가 요구사항을 분석하고 PRD와 작업 DAG를 포함한
 ### 칸반 — 실시간 작업 흐름
-![Kanban Presence](docs/images/kanban-presence.gif)
+![Kanban Presence](packages/landing/public/images/kanban-presence.gif)
 칸반 보드는 에이전트의 작업에 맞춰 자동으로 업데이트되며, 작업 카드가 To Do → In Progress → To Verify 사이를 실시간으로 이동합니다. 에이전트 프레즌스 인디케이터가 어떤 리소스가 작업 중인지 하이라이트합니다.
 ### 칸반 & 작업 DAG
-![Kanban & Task DAG](docs/images/kanan-dag.png)
+![Kanban & Task DAG](packages/landing/public/images/kanban-dag.png)
 작업 상태를 추적하는 칸반 보드와, 실행 순서 및 병렬 경로를 보여주는 의존성 DAG를 나란히 표시합니다.
 ### 아이디어 & 요구사항 구체화
-![Idea & Elaboration](docs/images/idea-elaborate.png)
+![Idea & Elaboration](packages/landing/public/images/idea-elaborate.png)
 PM 에이전트는 제안을 만들기 전에 구조화된 Q&A 라운드를 통해 요구사항을 명확히 합니다. 패널에는 아이디어 상세 정보와 함께, 답변 및 카테고리 태그가 달린 완료된 구체화 라운드가 나란히 표시됩니다.
 ### 제안 검토
-![Proposal Review](docs/images/proposal.png)
+![Proposal Review](packages/landing/public/images/proposal.png)
 PM 에이전트가 생성한 제안에는 문서 초안과 작업 DAG 초안이 담깁니다. 관리자는 이 패널에서 검토하여 승인하거나 거부합니다.
 ### 수락 기준 — 이중 경로 검증
-![Acceptance Criteria](docs/images/task-ac.png)
+![Acceptance Criteria](packages/landing/public/images/task-ac.png)
 개발자 에이전트의 자체 점검과 관리자의 검토가 각 수락 기준을 독립적으로 검증하며, 모든 항목마다 구조화된 통과/실패 증빙을 남깁니다.
 ### 유니버설 검색 — Cmd+K 커맨드 팔레트
-![Universal Search](docs/images/universal-search.png)
+![Universal Search](packages/landing/public/images/universal-search.png)
 6가지 엔티티 유형(작업·아이디어·제안·문서·프로젝트·프로젝트 그룹)을 아우르는 검색을 위한 Cmd+K 커맨드 팔레트입니다. 범위 필터링(Global / Group / Project), 엔티티 유형별 필터 탭, 키보드 내비게이션을 지원합니다. Web UI와 AI 에이전트(`chorus_search` MCP 도구를 통해)는 동일한 검색 백엔드를 공유합니다.
@@ -384,7 +386,7 @@ PGlite는 포트 5433에서 내장 PostgreSQL을 실행합니다. 데이터는 `
 ### AI 에이전트 연결하기
-가장 빠른 방법은 앱 내 설정 마법사입니다: Web UI를 열고 **Settings → Setup Guide → Open setup guide**로 이동한 뒤, 사용하는 클라이언트(Claude Code, Codex, OpenCode, OpenClaw, 또는 그 밖의 에이전트)에 맞는 단계별 안내를 따르세요. 마법사가 API 키를 만들어 주고, 정확한 명령을 보여주며, 연결 확인까지 안내합니다.
+가장 빠른 방법은 앱 내 설정 마법사입니다: Web UI를 열고 **Settings → Setup Guide → Open setup guide**로 이동한 뒤, 사용하는 클라이언트(Claude Code, Codex, Kiro, OpenCode, OpenClaw, 또는 그 밖의 에이전트)에 맞는 단계별 안내를 따르세요. 마법사가 API 키를 만들어 주고, 정확한 명령을 보여주며, 연결 확인까지 안내합니다.
 전체 문서를 읽고 싶다면:
@@ -392,6 +394,7 @@ PGlite는 포트 5433에서 내장 PostgreSQL을 실행합니다. 데이터는 `
 |--------|-------|
 | Claude Code | [CONNECT_CLAUDE_CODE.md](docs/CONNECT_CLAUDE_CODE.md) |
 | Codex CLI | [CONNECT_CODEX.md](docs/CONNECT_CODEX.md) |
+| Kiro CLI | [CONNECT_KIRO.md](docs/CONNECT_KIRO.md) |
 | OpenCode † | [CONNECT_OPENCODE.md](docs/CONNECT_OPENCODE.md) |
 | 그 밖의 MCP 에이전트(Cursor, Continue, 커스텀 등) | [CONNECT_OTHER_AGENTS.md](docs/CONNECT_OTHER_AGENTS.md) |
@@ -399,7 +402,7 @@ PGlite는 포트 5433에서 내장 PostgreSQL을 실행합니다. 데이터는 `
 API 키는 Web UI의 **Settings → Agents → Create API Key**에서 만듭니다. 키는 `cho_`로 시작하며 한 번만 표시됩니다.
-![Create API Key](docs/images/create-key.png)
+![Create API Key](packages/landing/public/images/create-key.png)
 ---

package/README.md CHANGED Viewed

@@ -1,5 +1,5 @@
 <p align="center">
-  <img src="docs/images/chorus-slug.png" alt="Chorus" width="240" />
+  <img src="packages/landing/public/images/chorus-slug.png" alt="Chorus" width="240" />
 </p>
 <p align="center"><strong>The Agent Harness for AI-Human Collaboration</strong></p>
@@ -36,6 +36,8 @@ The labels under each stage are the **permissions** an actor needs at that stage
 ## What's New
+**[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 `install-kiro.sh` plugin and a `--agent kiro` daemon backend, plus daemon fixes.
 **[v0.14.0](https://chorus-ai.dev/blog/chorus-v0.14.0-release/)** — Dark mode across the app (light / dark / system). Reference artifacts: attach docs, repos, issues, and articles to any idea, proposal, or task, readable inline and over MCP. Korean and Japanese locales (Korean contributed by the community). **Theme** ideas for grouping, plus daemon Start Development / Yolo buttons, conversational idea entry, crash-resume, and `chorus daemon install`.
 **[v0.13.0](https://chorus-ai.dev/blog/chorus-v0.13.0-release/)** — Per-project resource mind-map: a new Graph view wires each project's Ideas, Proposals, Documents, and Tasks into one collapsible tree, generated from the project's own structure. Every card carries its current status (ideas show the derived pipeline status the idea tracker uses), a title search auto-expands the path to every match with highlight/dim and prev/next navigation, and the same zoom/pan canvas renders on desktop and mobile (pinch + double-tap).
@@ -178,7 +180,7 @@ On startup the daemon banner prints the **exact `daemon.json` path it read** (an
 ### Remote Agent Wake — Dispatch to a Directory, Watch It Run
-![Remote Agent Wake](docs/images/agent-daemon-wake.gif)
+![Remote Agent Wake](packages/landing/public/images/agent-daemon-wake.gif)
 Assign an idea to a specific directory on a remote agent, then open the conversation and watch the local Claude Code pick up the work and run in real time — no terminal, no manual resume.
@@ -190,7 +192,7 @@ Chorus auto-organizes the entire project into a mind-map — Ideas, Proposals, D
 ### Proposal — AI Agent Generates Plans in Real Time
-![Proposal Presence](docs/images/proposal-presence.gif)
+![Proposal Presence](packages/landing/public/images/proposal-presence.gif)
 Watch a PM Agent analyze requirements and generate a proposal with PRD and task DAG — with real-time presence indicators showing agent activity.
@@ -202,37 +204,37 @@ The left panel is a pixel workspace where pixel characters represent each Agent'
 ### Kanban — Real-time Task Flow
-![Kanban Presence](docs/images/kanban-presence.gif)
+![Kanban Presence](packages/landing/public/images/kanban-presence.gif)
 The Kanban board updates automatically as Agents work, with task cards flowing between To Do → In Progress → To Verify in real time. Agent presence indicators highlight which resources are being worked on.
 ### Kanban & Task DAG
-![Kanban & Task DAG](docs/images/kanan-dag.png)
+![Kanban & Task DAG](packages/landing/public/images/kanban-dag.png)
 Kanban board for task status tracking alongside a dependency DAG showing execution order and parallel paths.
 ### Idea & Requirements Elaboration
-![Idea & Elaboration](docs/images/idea-elaborate.png)
+![Idea & Elaboration](packages/landing/public/images/idea-elaborate.png)
 PM Agents clarify requirements through structured Q&A rounds before creating Proposals. The panel shows idea details alongside completed elaboration rounds with answers and category tags.
 ### Proposal Review
-![Proposal Review](docs/images/proposal.png)
+![Proposal Review](packages/landing/public/images/proposal.png)
 Proposals generated by the PM Agent contain document drafts and task DAG drafts. Admins review and approve or reject on this panel.
 ### Acceptance Criteria — Dual-Path Verification
-![Acceptance Criteria](docs/images/task-ac.png)
+![Acceptance Criteria](packages/landing/public/images/task-ac.png)
 Dev Agent self-checks and Admin reviews each acceptance criterion independently, with structured pass/fail evidence for every item.
 ### Universal Search — Cmd+K Command Palette
-![Universal Search](docs/images/universal-search.png)
+![Universal Search](packages/landing/public/images/universal-search.png)
 A Cmd+K command palette for searching across all 6 entity types (Tasks, Ideas, Proposals, Documents, Projects, Project Groups). Supports scope filtering (Global / Group / Project), filter tabs per entity type, and keyboard navigation. Both the Web UI and AI agents (via `chorus_search` MCP tool) share the same search backend.
@@ -384,7 +386,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, OpenCode, 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, Kiro, 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:
@@ -392,6 +394,7 @@ 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) |
+| Kiro CLI | [CONNECT_KIRO.md](docs/CONNECT_KIRO.md) |
 | OpenCode † | [CONNECT_OPENCODE.md](docs/CONNECT_OPENCODE.md) |
 | Other MCP agents (Cursor, Continue, custom, …) | [CONNECT_OTHER_AGENTS.md](docs/CONNECT_OTHER_AGENTS.md) |
@@ -399,7 +402,7 @@ If you'd rather read the full docs:
 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)
+![Create API Key](packages/landing/public/images/create-key.png)
 ---

package/README.zh.md CHANGED Viewed

@@ -1,5 +1,5 @@
 <p align="center">
-  <img src="docs/images/chorus-slug.png" alt="Chorus" width="240" />
+  <img src="packages/landing/public/images/chorus-slug.png" alt="Chorus" width="240" />
 </p>
 <p align="center"><strong>面向 AI 与人类协作的 Agent Harness</strong></p>
@@ -27,6 +27,8 @@ Idea ──> Proposal ──> [Document + Task DAG] ──> Execute ──> Veri
 ## 最近更新
+**[v0.14.1](https://chorus-ai.dev/zh/blog/chorus-v0.14.1-release/)** — Amazon Kiro CLI 成为第四种接入方式（Kiro CLI v2）：一条命令的 `install-kiro.sh` 插件，以及 `--agent kiro` 的 daemon 后端，另有若干 daemon 修复。
 **[v0.14.0](https://chorus-ai.dev/zh/blog/chorus-v0.14.0-release/)** — 全应用深色模式（浅色 / 深色 / 跟随系统）。参考资料可挂到任意想法、提案或任务上，行内可读，也能通过 MCP 读写。新增韩语和日语（韩语由社区贡献）。用于归类的**主题**想法，以及 daemon 的「开始开发」/「Yolo」按钮、对话式建想法、崩溃恢复与 `chorus daemon install`。
 **[v0.13.0](https://chorus-ai.dev/zh/blog/chorus-v0.13.0-release/)** — 项目资源思维导图：新增 Graph 视图，把每个项目的想法、提案、文档、任务连成一棵可折叠的树，从项目自身结构自动生成。每张卡片都标着当前状态（想法用想法列表那套派生状态），标题搜索会自动展开命中节点的上游并高亮/调暗、配上下切换定位，同一张可缩放可拖动的图在桌面与手机上通用（捏合 + 双击缩放）。
@@ -169,7 +171,7 @@ daemon 启动时的横幅会打印它**实际读取的 `daemon.json` 路径**（
 ### 远程唤醒 Agent——派活到指定目录，实时看它跑
-![远程唤醒 Agent](docs/images/agent-daemon-wake.gif)
+![远程唤醒 Agent](packages/landing/public/images/agent-daemon-wake.gif)
 把一条想法派给远程 Agent 的某个目录，打开对话窗口，就能实时看到本地的 Claude Code 接活、开跑，全程不用碰终端，也不用手动 resume。
@@ -181,7 +183,7 @@ Chorus 自动把整个项目整理成一张思维导图——想法、提案、
 ### Proposal——AI Agent 实时生成计划
-![Proposal Presence](docs/images/proposal-presence.gif)
+![Proposal Presence](packages/landing/public/images/proposal-presence.gif)
 PM Agent 分析需求并实时生成包含 PRD 和任务 DAG 的提案，Presence 指示器实时显示 Agent 活动状态。
@@ -193,37 +195,37 @@ PM Agent 分析需求并实时生成包含 PRD 和任务 DAG 的提案，Presenc
 ### Kanban——任务状态实时流转
-![Kanban Presence](docs/images/kanban-presence.gif)
+![Kanban Presence](packages/landing/public/images/kanban-presence.gif)
 Kanban 看板随 Agent 工作进度自动更新，任务卡片在 To Do → In Progress → To Verify 之间实时流转。Presence 指示器高亮显示正在被操作的资源。
 ### 看板 & 任务 DAG
-![Kanban & Task DAG](docs/images/kanan-dag.png)
+![Kanban & Task DAG](packages/landing/public/images/kanban-dag.png)
 看板追踪任务状态，DAG 展示依赖关系和并行路径，一目了然。
 ### Idea & 需求细化
-![Idea & Elaboration](docs/images/idea-elaborate.png)
+![Idea & Elaboration](packages/landing/public/images/idea-elaborate.png)
 PM Agent 在创建 Proposal 前，通过结构化问答轮次澄清需求。面板展示 Idea 详情及已完成的细化轮次。
 ### 提案审阅
-![Proposal Review](docs/images/proposal.png)
+![Proposal Review](packages/landing/public/images/proposal.png)
 PM Agent 生成的 Proposal 包含文档草稿和任务 DAG 草稿，Admin 在此面板审阅并决定批准或驳回。
 ### 验收标准——双路验证
-![Acceptance Criteria](docs/images/task-ac.png)
+![Acceptance Criteria](packages/landing/public/images/task-ac.png)
 Dev Agent 自检 + Admin 独立审核，每条验收标准都有结构化的通过/失败证据。
 ### Universal Search——Cmd+K 全局搜索
-![Universal Search](docs/images/universal-search.png)
+![Universal Search](packages/landing/public/images/universal-search.png)
 Cmd+K 命令面板，支持跨 6 种实体类型搜索。支持范围筛选（全局/项目组/单项目）、按类型切换 Tab、键盘导航。Web UI 和 AI Agent（通过 `chorus_search` MCP 工具）共享同一搜索后端。
@@ -375,7 +377,7 @@ PGlite 在端口 5433 运行嵌入式 PostgreSQL。数据存储在 `.pglite/`，
 ### 连接 AI Agent
-最快的方式是用应用内的 setup 向导：打开 Web UI，进入 **Settings → Setup Guide → 打开设置向导**，按照向导给出的分步指引接入自己的客户端（Claude Code、Codex、OpenCode、OpenClaw 或其他 agent）。向导会帮你创建 API Key、展示完整命令，并引导你验证连接。
+最快的方式是用应用内的 setup 向导：打开 Web UI，进入 **Settings → Setup Guide → 打开设置向导**，按照向导给出的分步指引接入自己的客户端（Claude Code、Codex、Kiro、OpenCode、OpenClaw 或其他 agent）。向导会帮你创建 API Key、展示完整命令，并引导你验证连接。
 如果偏好文档：
@@ -383,6 +385,7 @@ 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) |
+| Kiro CLI | [CONNECT_KIRO.md](docs/CONNECT_KIRO.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) |
@@ -390,7 +393,7 @@ PGlite 在端口 5433 运行嵌入式 PostgreSQL。数据存储在 `.pglite/`，
 在 Web UI 的 **Settings → Agents → Create API Key** 创建 API Key。Key 以 `cho_` 开头，仅在创建时显示一次。
-![Create API Key](docs/images/create-key.png)
+![Create API Key](packages/landing/public/images/create-key.png)
 ---

package/chorus.mjs CHANGED Viewed

@@ -181,6 +181,10 @@ DAEMON / LOGIN (client mode)
   --sigint-timeout <ms>    Grace window after SIGINT before a forceful kill    (env: CHORUS_DAEMON_SIGINT_TIMEOUT)
                            when an interrupt is received (default: 10000).
                            Also configurable via ~/.chorus/daemon.json sigintTimeoutMs.
+  -y, --yes                Non-interactive 'chorus daemon install': skip all install
+                           prompts (credentials are still resolved, persisted, and
+                           validated; install aborts if none resolve). A non-TTY
+                           install behaves as if --yes were passed.
   Credential resolution order: flags > CHORUS_URL/CHORUS_API_KEY env >
   ~/.chorus/daemon.json (from 'chorus login') > Claude Code plugin config.

package/cli/client-args.mjs CHANGED Viewed

@@ -13,10 +13,11 @@
  */
 export const DAEMON_ACTIONS = new Set(["stop", "status", "restart", "logs", "install", "uninstall"]);
-/** Known agent backends. Only `claude-code` is implemented; the rest reserve
- * the extension point (see daemon-agent-selection). Exported for the resolver
- * the --agent task wires in; parsing here does not validate the value. */
-export const KNOWN_AGENTS = new Set(["claude-code"]);
+/** Known agent backends, kept in sync with the authoritative list in
+ * daemon-agent.mjs (`claude-code`, `codex`, `kiro` — all implemented). This copy
+ * is informational only: parsing here does not validate the value (the resolver
+ * in daemon-agent.mjs is the single source of truth for validation). */
+export const KNOWN_AGENTS = new Set(["claude-code", "codex", "kiro"]);
 /**
  * Parse the client-subcommand flags out of an arg list. Recognizes the
@@ -38,7 +39,7 @@ export const KNOWN_AGENTS = new Set(["claude-code"]);
  * @returns {{
  *   url?: string, apiKey?: string, yolo?: boolean, sigintTimeout?: string,
  *   agent?: string, chorusOnly?: boolean, verbose?: boolean, detach?: boolean,
- *   cwd?: string[], force?: boolean, help?: boolean,
+ *   cwd?: string[], force?: boolean, yes?: boolean, help?: boolean,
  * }}
  */
 export function parseClientFlags(argv) {
@@ -63,6 +64,7 @@ export function parseClientFlags(argv) {
     else if (a === "--verbose") out.verbose = true;
     else if (a === "-d" || a === "--detach") out.detach = true;
     else if (a === "--force") out.force = true;
+    else if (a === "--yes" || a === "-y") out.yes = true;
     else if (a === "--help" || a === "-h") out.help = true;
   }
   return out;
@@ -117,7 +119,7 @@ OPTIONS
   --url <url>              Remote Chorus server URL            (env: CHORUS_URL)
   --api-key <cho_...>      Agent API key                       (env: CHORUS_API_KEY)
   --agent <type>           Local agent backend to wake         (env: CHORUS_AGENT)
-                           (claude-code | codex; default: claude-code)
+                           (claude-code | codex | kiro; default: claude-code)
   --yolo                   Full autonomy for the woken agent   (env: CHORUS_YOLO=1)
                            (--dangerously-skip-permissions: Bash, file writes, any
                            command). This is the DEFAULT permission mode.
@@ -130,6 +132,10 @@ OPTIONS
                            local paths at once. Default: the directory it was launched
                            from. (Also configurable as "cwds":[…] in ~/.chorus/daemon.json.)
   -d, --detach             Run detached in the background (pidfile + logfile)
+  -y, --yes                Non-interactive install: skip all 'chorus daemon
+                           install' prompts (credentials still resolved, persisted,
+                           and validated; install aborts if none resolve). A non-TTY
+                           install behaves as if --yes were passed.
   --verbose                More detailed per-wake logging
   --sigint-timeout <ms>    Grace window after SIGINT before a forceful kill
                            (env: CHORUS_DAEMON_SIGINT_TIMEOUT; default 10000)
@@ -147,8 +153,13 @@ SERVICE (install)
   starts at login, restarts on failure, and 'systemctl --user stop' shuts it
   down gracefully. Do NOT hand-write a Type=forking unit around 'chorus daemon
   -d' — the daemon self-daemonizes, which systemd cannot track and which loops
-  on restart. The install captures the --cwd / --agent / --chorus-only flags you
-  pass. On macOS/Windows install prints a correct template you install manually.
+  on restart. Before writing the unit, install resolves + persists + validates
+  your credentials into ~/.chorus/daemon.json (so the clean boot environment can
+  authenticate) and configures the served working directories there too (prompting
+  interactively for one or more when none are set — pass -y/--yes or run non-TTY to
+  skip prompts). The unit captures --agent / --chorus-only but NOT --cwd (cwds live
+  in daemon.json). On macOS/Windows install prints a correct template you install
+  manually.
 EXAMPLES
   chorus daemon                        # Foreground, default yolo (TTY confirms once)

package/cli/codex-session-map.mjs CHANGED Viewed

@@ -5,60 +5,18 @@
 // keyed by the Chorus session anchor (direct idea uuid, or the entity uuid for an
 // ad-hoc session) and `codex exec resume <thread_id>` on the next wake.
 //
-// The store is a single JSON object `{ "<anchor>": "<thread_id>" }` at
-// ~/.chorus/codex-sessions.json (same dir family as daemon.json). The anchor is a
-// globally-unique Chorus uuid, so one flat file is safe across the daemon's
-// multiple path-connections.
-//
-// CONTRACT: this is best-effort and MUST NEVER throw into the wake path. Any
-// read/parse/write/rename failure degrades to "no mapping → next wake starts
-// fresh" with a visible log (no-silent-errors). IO is injectable for tests.
+// Thin wrapper over the generic `createSessionMap` factory (shared with the Kiro
+// backend); the store is ~/.chorus/codex-sessions.json. The public API
+// (getThreadId / setThreadId / codexSessionMapPath) and its injectable-IO deps are
+// unchanged — see session-map.mjs for the best-effort / never-throw contract.
-import { mkdirSync, readFileSync, renameSync, writeFileSync } from "node:fs";
-import { homedir } from "node:os";
-import { dirname, join } from "node:path";
+import { createSessionMap } from "./session-map.mjs";
-const NOOP_LOGGER = { info() {}, warn() {}, error() {} };
+const map = createSessionMap({ filename: "codex-sessions.json", logPrefix: "codex-session-map" });
 /** Absolute path to the Codex session-id map, alongside ~/.chorus/daemon.json. */
 export function codexSessionMapPath() {
-  return join(homedir(), ".chorus", "codex-sessions.json");
-}
-/** A non-empty trimmed string, or null. */
-function nonEmpty(value) {
-  return typeof value === "string" && value.trim().length > 0 ? value : null;
-}
-/**
- * Read the whole map as a plain object. Missing / unreadable / malformed file →
- * `{}` (never throws). A non-object JSON value (array / scalar) is also treated
- * as empty.
- * @param {string} path
- * @param {(p: string) => string} read
- * @param {{warn(m:string):void}} logger
- * @returns {Record<string, unknown>}
- */
-function readMap(path, read, logger) {
-  let raw;
-  try {
-    raw = read(path);
-  } catch (err) {
-    // ENOENT is the normal "no map yet" case — silent. Other read errors warn.
-    if (!(err && err.code === "ENOENT")) {
-      logger.warn(`[Chorus] codex-session-map: read failed (${err}) — treating as empty`);
-    }
-    return {};
-  }
-  try {
-    const parsed = JSON.parse(raw);
-    if (parsed && typeof parsed === "object" && !Array.isArray(parsed)) return parsed;
-    logger.warn("[Chorus] codex-session-map: file is not a JSON object — treating as empty");
-    return {};
-  } catch (err) {
-    logger.warn(`[Chorus] codex-session-map: corrupt JSON (${err}) — treating as empty`);
-    return {};
-  }
+  return map.mapPath();
 }
 /**
@@ -69,13 +27,7 @@ function readMap(path, read, logger) {
  * @returns {string | null}
  */
 export function getThreadId(anchor, deps = {}) {
-  const a = nonEmpty(anchor);
-  if (!a) return null;
-  const path = deps.path ?? codexSessionMapPath();
-  const read = deps.read ?? ((p) => readFileSync(p, "utf8"));
-  const logger = deps.logger ?? NOOP_LOGGER;
-  const map = readMap(path, read, logger);
-  return nonEmpty(map[a]);
+  return map.get(anchor, deps);
 }
 /**
@@ -91,27 +43,5 @@ export function getThreadId(anchor, deps = {}) {
  * @returns {void}
  */
 export function setThreadId(anchor, threadId, deps = {}) {
-  const a = nonEmpty(anchor);
-  const t = nonEmpty(threadId);
-  if (!a || !t) return; // nothing meaningful to persist
-  const path = deps.path ?? codexSessionMapPath();
-  const read = deps.read ?? ((p) => readFileSync(p, "utf8"));
-  const write = deps.write ?? writeFileSync;
-  const mkdir = deps.mkdir ?? mkdirSync;
-  const rename = deps.rename ?? renameSync;
-  const logger = deps.logger ?? NOOP_LOGGER;
-  try {
-    const map = readMap(path, read, logger);
-    map[a] = t;
-    mkdir(dirname(path), { recursive: true });
-    // Atomic write: temp file (0600) in the same dir, then rename over target,
-    // so a crash mid-write never truncates the live map.
-    const tmp = `${path}.tmp`;
-    write(tmp, JSON.stringify(map, null, 2) + "\n", { mode: 0o600 });
-    rename(tmp, path);
-  } catch (err) {
-    // Best-effort: a failed persist just means the next wake starts fresh.
-    logger.warn(`[Chorus] codex-session-map: failed to persist ${a}→${t} (${err}) — wake will start fresh next time`);
-  }
+  map.set(anchor, threadId, deps);
 }

package/cli/daemon-agent.mjs CHANGED Viewed

@@ -1,12 +1,14 @@
 // cli/daemon-agent.mjs
 // Pure resolution + validation of the daemon's `--agent <type>` selection.
-// `claude-code` (the default) and `codex` are both implemented backends
-// (add-daemon-codex-backend cashed in the reserved `codex` slot). Resolving an
-// unknown value is a hard error (no silent fallback). Zero dependencies.
+// `claude-code` (the default), `codex`, and `kiro` are all implemented backends
+// (add-daemon-codex-backend cashed in the reserved `codex` slot;
+// add-daemon-kiro-backend adds `kiro`). Resolving an unknown value is a hard
+// error (no silent fallback). Zero dependencies.
-/** The agent backends the daemon recognizes. Both are implemented (claude-code
- * via ClaudeSpawner, codex via CodexSpawner — see spawner-select.mjs). */
-export const KNOWN_AGENTS = ["claude-code", "codex"];
+/** The agent backends the daemon recognizes. All are implemented (claude-code
+ * via ClaudeSpawner, codex via CodexSpawner, kiro via KiroSpawner — see
+ * spawner-select.mjs). */
+export const KNOWN_AGENTS = ["claude-code", "codex", "kiro"];
 /** The default agent backend when neither --agent nor CHORUS_AGENT is set. */
 export const DEFAULT_AGENT = "claude-code";
@@ -21,6 +23,7 @@ export const DEFAULT_AGENT = "claude-code";
  */
 export function backendCli(agentType) {
   if (agentType === "codex") return { name: "codex", envVar: "CHORUS_CODEX_PATH" };
+  if (agentType === "kiro") return { name: "kiro-cli", envVar: "CHORUS_KIRO_PATH" };
   return { name: "claude", envVar: "CHORUS_CLAUDE_PATH" };
 }
@@ -33,7 +36,9 @@ export function backendCli(agentType) {
  * @returns {string}
  */
 export function backendClientType(agentType) {
-  return agentType === "codex" ? "codex" : "claude_code";
+  if (agentType === "codex") return "codex";
+  if (agentType === "kiro") return "kiro";
+  return "claude_code";
 }
 /**

package/cli/daemon-config.mjs CHANGED Viewed

@@ -107,7 +107,7 @@ export function resolveSigintTimeoutMs(flags = {}, deps = {}) {
 // The Waker/SseListener treat an `undefined` entry as "use process.cwd()".
 /** Expand a leading `~` to the home dir and resolve to an absolute path. */
-function normalizeCwd(value, home) {
+export function normalizeCwd(value, home) {
   if (typeof value !== "string") return undefined;
   const trimmed = value.trim();
   if (!trimmed) return undefined;
@@ -125,7 +125,7 @@ function normalizeCwd(value, home) {
  * @param {Array<unknown>} list @param {string} home
  * @returns {string[]}
  */
-function cleanCwdList(list, home) {
+export function cleanCwdList(list, home) {
   const seen = new Set();
   const out = [];
   for (const raw of Array.isArray(list) ? list : []) {