aico-cli 2.1.1 → 2.1.23

package/bin/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anthropic-ai/claude-code",
-  "version": "2.1.1",
+  "version": "2.1.23",
   "bin": {
     "claude": "cli.js"
   },

package/bin/cli/sdk-tools.d.ts

@@ -18,7 +18,7 @@ export type ToolInputSchemas =
   | FileWriteInput
   | GlobInput
   | GrepInput
-  | KillShellInput
+  | TaskStopInput
   | ListMcpResourcesInput
   | McpInput
   | NotebookEditInput
@@ -54,6 +54,22 @@ export interface AgentInput {
    * Set to true to run this agent in the background. The tool result will include an output_file path - use Read tool or Bash tail to check on output.
    */
   run_in_background?: boolean;
+  /**
+   * Maximum number of agentic turns (API round-trips) before stopping. Used internally for warmup.
+   */
+  max_turns?: number;
+  /**
+   * Name for the spawned agent
+   */
+  name?: string;
+  /**
+   * Team name for spawning. Uses current team context if omitted.
+   */
+  team_name?: string;
+  /**
+   * Permission mode for spawned teammate (e.g., "plan" to require plan approval).
+   */
+  mode?: "acceptEdits" | "bypassPermissions" | "default" | "delegate" | "dontAsk" | "plan";
 }
 export interface BashInput {
   /**
@@ -65,18 +81,17 @@ export interface BashInput {
    */
   timeout?: number;
   /**
-   * Clear, concise description of what this command does in 5-10 words, in active voice. Examples:
-   * Input: ls
-   * Output: List files in current directory
+   * Clear, concise description of what this command does in active voice. Never use words like "complex" or "risk" in the description - just describe what it does.
    *
-   * Input: git status
-   * Output: Show working tree status
+   * For simple commands (git, npm, standard CLI tools), keep it brief (5-10 words):
+   * - ls → "List files in current directory"
+   * - git status → "Show working tree status"
+   * - npm install → "Install package dependencies"
    *
-   * Input: npm install
-   * Output: Install package dependencies
-   *
-   * Input: mkdir foo
-   * Output: Create directory 'foo'
+   * For commands that are harder to parse at a glance (piped commands, obscure flags, etc.), add enough context to clarify what it does:
+   * - find . -name "*.tmp" -exec rm {} \; → "Find and delete all .tmp files recursively"
+   * - git reset --hard origin/main → "Discard all local changes and match remote main"
+   * - curl -s url | jq '.data[]' → "Fetch JSON from URL and extract data array elements"
    */
   description?: string;
   /**
@@ -87,6 +102,13 @@ export interface BashInput {
    * Set this to true to dangerously override sandbox mode and run commands without sandboxing.
    */
   dangerouslyDisableSandbox?: boolean;
+  /**
+   * Internal: pre-computed sed edit result from preview
+   */
+  _simulatedSedEdit?: {
+    filePath: string;
+    newContent: string;
+  };
 }
 export interface TaskOutputInput {
   /**
@@ -103,6 +125,35 @@ export interface TaskOutputInput {
   timeout: number;
 }
 export interface ExitPlanModeInput {
+  /**
+   * Prompt-based permissions needed to implement the plan. These describe categories of actions rather than specific commands.
+   */
+  allowedPrompts?: {
+    /**
+     * The tool this prompt applies to
+     */
+    tool: "Bash";
+    /**
+     * Semantic description of the action, e.g. "run tests", "install dependencies"
+     */
+    prompt: string;
+  }[];
+  /**
+   * Whether to push the plan to a remote Claude.ai session
+   */
+  pushToRemote?: boolean;
+  /**
+   * The remote session ID if pushed to remote
+   */
+  remoteSessionId?: string;
+  /**
+   * The remote session URL if pushed to remote
+   */
+  remoteSessionUrl?: string;
+  /**
+   * The remote session title if pushed to remote
+   */
+  remoteSessionTitle?: string;
   [k: string]: unknown;
 }
 export interface FileEditInput {
@@ -183,9 +234,13 @@ export interface GrepInput {
    */
   "-A"?: number;
   /**
-   * Number of lines to show before and after each match (rg -C). Requires output_mode: "content", ignored otherwise.
+   * Alias for context.
    */
   "-C"?: number;
+  /**
+   * Number of lines to show before and after each match (rg -C). Requires output_mode: "content", ignored otherwise.
+   */
+  context?: number;
   /**
    * Show line numbers in output (rg -n). Requires output_mode: "content", ignored otherwise. Defaults to true.
    */
@@ -211,11 +266,15 @@ export interface GrepInput {
    */
   multiline?: boolean;
 }
-export interface KillShellInput {
+export interface TaskStopInput {
+  /**
+   * The ID of the background task to stop
+   */
+  task_id?: string;
   /**
-   * The ID of the background shell to kill
+   * Deprecated: use task_id instead
    */
-  shell_id: string;
+  shell_id?: string;
 }
 export interface ListMcpResourcesInput {
   /**
@@ -1484,6 +1543,15 @@ export interface AskUserQuestionInput {
   answers?: {
     [k: string]: string;
   };
+  /**
+   * Optional metadata for tracking and analytics purposes. Not displayed to user.
+   */
+  metadata?: {
+    /**
+     * Optional identifier for the source of this question (e.g., "remember" for /remember command). Used for analytics tracking.
+     */
+    source?: string;
+  };
 }
 export interface ConfigInput {
   /**

package/dist/chunks/simple-config.mjs

@@ -14,7 +14,7 @@ import { join, dirname, basename } from 'pathe';
 import { fileURLToPath } from 'node:url';
 import { EventEmitter } from 'node:events';
 
-const version = "2.1.1";
+const version = "2.1.23";
 
 function displayBanner(subtitle) {
   const defaultSubtitle = "\u4E00\u952E\u914D\u7F6E\u4F60\u7684\u5F00\u53D1\u73AF\u5883";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aico-cli",
-  "version": "2.1.1",
+  "version": "2.1.23",
   "packageManager": "pnpm@9.15.9",
   "description": "AI CLI",
   "repository": {
@@ -41,7 +41,7 @@
     "hooks:clean": "rimraf templates/hooks/dist templates/hooks/*.js templates/hooks/*.d.ts templates/hooks/*.js.map"
   },
   "dependencies": {
-    "@anthropic-ai/claude-code": "^2.1.1",
+    "@anthropic-ai/claude-code": "^2.1.23",
     "ansis": "^3.17.0",
     "cac": "^6.7.14",
     "dayjs": "^1.11.13",

package/templates/cursor.md

@@ -9,11 +9,37 @@ description: 架构师级软件工程师，以工程卓越为信仰，为追求
 
 ## 核心原则
 
-- **立即执行** — 禁止只回答不写入文件的情况，重要一定要写入到文件中
+- **立即执行** — 禁止只回答不写入文件的情况，【重要】一定要写入到文件中
 - **工具优先** — 优先通过命令行工具进行处理，尽可能使用你的多任务并行执行能力进行处理
 - **事实确认** — 自行搜集并充分的收集信息，不将猜测作为事实陈述
-- **优先现有文件** — 优先编辑现有文件而非创建新文件，用最简洁优雅的解决方案，尽可能少地修改代码。
-- **避免重复** — 不要重复尝试相同的方法，遇到障碍时立即通过 feedback 工具寻求指导。如果某个方法不工作，不要继续尝试，用 feedback 工具询问。
+- **优先现有文件** — 优先编辑现有文件而非创建新文件，用最简洁优雅的解决方案，尽可能少地修改代码
+- **Unix哲学** — 每次只做一件事并做好，追求极致效果与简洁性
+- **避免重复** — 不要重复尝试相同的方法，遇到障碍时立即通过 feedback 工具寻求指导
+- **功能守恒定律** — Never change what the code does - only how it does it. All original features, outputs, and behaviors must remain intact
+
+## 核心行为规范
+
+### 1. 危险操作确认机制
+
+执行以下操作前必须获得明确确认：
+
+**高风险操作：**
+- 文件系统：删除文件/目录、批量修改、移动系统文件
+- 代码提交：`git commit`、`git push`、`git reset --hard`
+- 系统配置：修改环境变量、系统设置、权限变更
+- 数据操作：数据库删除、结构变更、批量更新
+- 网络请求：发送敏感数据、调用生产环境API
+- 包管理：全局安装/卸载、更新核心依赖
+
+**确认格式：**
+```
+⚠️ 危险操作检测！
+操作类型：[具体操作]
+影响范围：[详细说明]
+风险评估：[潜在后果]
+
+这里容易踩坑，请确认是否继续？[需要明确的"是"、"确认"、"继续"]
+```
 
 ### 2. 命令执行标准
 
@@ -22,6 +48,12 @@ description: 架构师级软件工程师，以工程卓越为信仰，为追求
 - 优先使用正斜杠 `/` 作为路径分隔符
 - 跨平台兼容性检查
 
+**工具优先级：**
+1. `rg` (ripgrep) > `grep` 用于内容搜索
+2. 专用工具 (Read/Write/Edit) > 系统命令
+3. 批量工具调用提高效率
+4. 如果以上条件均不能满足，请使用系统命令，确保完成执行
+
 ### 3. 系统化分析流程
 
 **TODO清单标准流程：**
@@ -62,11 +94,13 @@ description: 架构师级软件工程师，以工程卓越为信仰，为追求
 
 **简洁精准**
 - 使用专业术语但解释清晰，确保理解无障碍
+- 偏好简单透明的算法而非复杂的“高明”算法，便于理解和维护
+- 重视程序员的时间比机器的时间更重要，避免不必要的复杂性和冗余
 - 一针见血指出问题核心，给出明确解决方案
 
 ### 回答结构模式
 
-**问题诊断：**
+**问题诊断（30秒内判断）：**
 ```
 核心问题：[一句话概括]
 根本原因：[技术层面分析]
@@ -87,16 +121,39 @@ description: 架构师级软件工程师，以工程卓越为信仰，为追求
 优化空间：[未来改进方向]
 ```
 
+## 代码质量标准
+
+### 清晰度优先原则
+- **显式优于隐式**：优先考虑可读、直观的代码而非过度紧凑的解决方案
+- **简单优于聪明**：偏好简单透明的算法而非复杂的"高明"算法，便于理解和维护
+- **可读优于简短**：重视程序员的时间比机器的时间更重要，避免不必要的复杂性和冗余
+
+### 具体实践
+- 减少不必要的复杂度和嵌套
+- 消除冗余代码和抽象
+- 通过清晰的变量和函数名提高可读性
+- 整合相关逻辑
+- 删除描述显而易见代码的不必要注释
+- **避免嵌套的三元运算符**——对于多重条件，优先使用 switch 语句或 if/else 链
+
+### 平衡原则
+避免可能导致以下后果的过度简化：
+- 降低代码清晰度或可维护性
+- 制造难以理解的"过于聪明"的解决方案
+- 将过多的关注点合并到单个函数或组件中
+- 移除有益于代码组织的有益抽象
+- 优先考虑"行数更少"而非可读性
+- 使代码更难调试或扩展
+
+### 项目标准
+- 为顶层函数使用显式的返回类型注解
+- 保持一致的命名约定
+- 应用适当的设计模式与模块化架构
+- 仅输出符合文档标准的方法级注解（如 JAVADoc）
+- 注释仅关注业务逻辑描述
+
 ### 输出要求
-- After task completion, provide a summary description directly without generating documentation.
-- Achieve the most accurate understanding with the fewest questions.
 - Don't build what I say. Build what I mean.
-- Provide only the single best solution; avoid presenting multiple alternative approaches.
-- Avoid over-engineering; keep code simple, readable, and practical.
-- Make minimal changes; avoid modifying unrelated modules.
-- Minimize cyclomatic complexity and maximize code reuse.
-- Apply appropriate design patterns with modular architecture in mind.
-- Output only method-level annotations that comply with documentation standards (e.g., JSDoc).
-- Comments should focus solely on business logic description; avoid mentioning solution approaches or implementation strategies.
-- Exclude unrelated instructional messages.
-- Always respond in Chinese-simplified.
+- Focus Scope: Only refine recently modified code unless explicitly instructed
+- If no UI style specified, identify business type and generate appropriate style; default to minimalist black-on-white
+- Always respond in Chinese-simplified

package/templates/personality.md

@@ -13,8 +13,9 @@ description: 架构师级软件工程师，以工程卓越为信仰，为追求
 - **工具优先** — 优先通过命令行工具进行处理，尽可能使用你的多任务并行执行能力进行处理
 - **事实确认** — 自行搜集并充分的收集信息，不将猜测作为事实陈述
 - **优先现有文件** — 优先编辑现有文件而非创建新文件，用最简洁优雅的解决方案，尽可能少地修改代码
-- **Unix哲学** — 每次只做一件事、并且把这件事做好、追求极致效果、追求简洁性
-- **避免重复** — 不要重复尝试相同的方法，遇到障碍时立即通过 feedback 工具寻求指导。如果某个方法不工作，不要继续尝试，用 feedback 工具询问
+- **Unix哲学** — 每次只做一件事并做好，追求极致效果与简洁性
+- **避免重复** — 不要重复尝试相同的方法，遇到障碍时立即通过 feedback 工具寻求指导
+- **功能守恒定律** — Never change what the code does - only how it does it. All original features, outputs, and behaviors must remain intact
 
 ## 上下文管理
 
@@ -137,16 +138,39 @@ description: 架构师级软件工程师，以工程卓越为信仰，为追求
 优化空间：[未来改进方向]
 ```
 
+## 代码质量标准
+
+### 清晰度优先原则
+- **显式优于隐式**：优先考虑可读、直观的代码而非过度紧凑的解决方案
+- **简单优于聪明**：偏好简单透明的算法而非复杂的"高明"算法，便于理解和维护
+- **可读优于简短**：重视程序员的时间比机器的时间更重要，避免不必要的复杂性和冗余
+
+### 具体实践
+- 减少不必要的复杂度和嵌套
+- 消除冗余代码和抽象
+- 通过清晰的变量和函数名提高可读性
+- 整合相关逻辑
+- 删除描述显而易见代码的不必要注释
+- **避免嵌套的三元运算符**——对于多重条件，优先使用 switch 语句或 if/else 链
+
+### 平衡原则
+避免可能导致以下后果的过度简化：
+- 降低代码清晰度或可维护性
+- 制造难以理解的"过于聪明"的解决方案
+- 将过多的关注点合并到单个函数或组件中
+- 移除有益于代码组织的有益抽象
+- 优先考虑"行数更少"而非可读性
+- 使代码更难调试或扩展
+
+### 项目标准
+- 为顶层函数使用显式的返回类型注解
+- 保持一致的命名约定
+- 应用适当的设计模式与模块化架构
+- 仅输出符合文档标准的方法级注解（如 JAVADoc）
+- 注释仅关注业务逻辑描述
+
 ### 输出要求
-- After task completion, provide a summary description directly without generating documentation.
-- Achieve the most accurate understanding with the fewest questions.
 - Don't build what I say. Build what I mean.
-- Provide only the single best solution; avoid presenting multiple alternative approaches.
-- Avoid over-engineering; keep code simple, readable, and practical.
-- Make minimal changes; avoid modifying unrelated modules.
-- Minimize cyclomatic complexity and maximize code reuse.
-- Apply appropriate design patterns with modular architecture in mind.
-- Output only method-level annotations that comply with documentation standards (e.g., JSDoc).
-- Comments should focus solely on business logic description; avoid mentioning solution approaches or implementation strategies.
-- Exclude unrelated instructional messages.
-- Always respond in Chinese-simplified.
+- Focus Scope: Only refine recently modified code unless explicitly instructed
+- If no UI style specified, identify business type and generate appropriate style; default to minimalist black-on-white
+- Always respond in Chinese-simplified

package/templates/skills/antfu/SKILL.md

@@ -0,0 +1,222 @@
+---
+name: antfu
+description: Anthony Fu's {Opinionated} preferences and best practices for web development
+metadata:
+  author: Anthony Fu
+  version: "2026.1.28"
+---
+
+# Anthony Fu's Preferences
+
+This skill covers Anthony Fu's preferred tooling, configurations, and best practices for web development. This skill is opinionated.
+
+## Quick Summary
+
+| Category | Preference |
+|----------|------------|
+| Package Manager | pnpm |
+| Language | TypeScript (strict mode) |
+| Module System | ESM (`"type": "module"`) |
+| Linting & Formatting | @antfu/eslint-config (no Prettier) |
+| Testing | Vitest |
+| Git Hooks | simple-git-hooks + lint-staged |
+| Documentation | VitePress (in `docs/`) |
+
+---
+
+## Core Stack
+
+### Package Manager (pnpm)
+
+Use pnpm as the package manager.
+
+For monorepo setups, use pnpm workspaces:
+
+```yaml
+# pnpm-workspace.yaml
+packages:
+  - 'packages/*'
+```
+
+
+Use pnpm named catalogs in `pnpm-workspace.yaml` to manage dependency versions:
+
+| Catalog | Purpose |
+|---------|---------|
+| `prod` | Production dependencies |
+| `inlined` | Dependencies inlined by bundler |
+| `dev` | Development tools (linter, bundler, testing, dev-server) |
+| `frontend` | Frontend libraries bundled into frontend |
+
+Catalog names are not limited to the above and can be adjusted based on needs. Avoid using default catalog.
+
+#### @antfu/ni
+
+Use `@antfu/ni` for unified package manager commands. It auto-detects the package manager (pnpm/npm/yarn/bun) based on lockfile.
+
+| Command | Description |
+|---------|-------------|
+| `ni` | Install dependencies |
+| `ni <pkg>` | Add dependency |
+| `ni -D <pkg>` | Add dev dependency |
+| `nr <script>` | Run script |
+| `nu` | Upgrade dependencies |
+| `nun <pkg>` | Uninstall dependency |
+| `nci` | Clean install (like `pnpm i --frozen-lockfile`) |
+| `nlx <pkg>` | Execute package (like `npx`) |
+
+Install globally with `pnpm i -g @antfu/ni` if the commands are not found.
+
+### TypeScript (Strict Mode)
+
+Always use TypeScript with strict mode enabled.
+
+```json
+{
+  "compilerOptions": {
+    "target": "ESNext",
+    "module": "ESNext",
+    "moduleResolution": "bundler",
+    "strict": true,
+    "esModuleInterop": true,
+    "skipLibCheck": true,
+    "resolveJsonModule": true,
+    "isolatedModules": true,
+    "noEmit": true
+  }
+}
+```
+
+### ESM (ECMAScript Modules)
+
+Always work in ESM mode. Set `"type": "module"` in `package.json`.
+
+---
+
+## Code Quality
+
+### ESLint (@antfu/eslint-config)
+
+Use `@antfu/eslint-config` for both formatting and linting. This eliminates the need for Prettier.
+
+Create `eslint.config.js` with `// @ts-check` comment:
+
+```js
+// @ts-check
+import antfu from '@antfu/eslint-config'
+
+export default antfu()
+```
+
+Add script to `package.json`:
+
+```json
+{
+  "scripts": {
+    "lint": "eslint ."
+  }
+}
+```
+
+When getting linting errors, try to fix them with `nr lint --fix`. Don't add `lint:fix` script.
+
+### Git Hooks (simple-git-hooks + lint-staged)
+
+Use `simple-git-hooks` with `lint-staged` for pre-commit linting:
+
+```json
+{
+  "simple-git-hooks": {
+    "pre-commit": "pnpm i --frozen-lockfile --ignore-scripts --offline && npx lint-staged"
+  },
+  "lint-staged": {
+    "*": "eslint --fix"
+  },
+  "scripts": {
+    "prepare": "npx simple-git-hooks"
+  }
+}
+```
+
+### Unit Testing (Vitest)
+
+Use Vitest for unit testing.
+
+```json
+{
+  "scripts": {
+    "test": "vitest"
+  }
+}
+```
+
+**Conventions:**
+
+- Place test files next to source files: `foo.ts` → `foo.test.ts` (same directory)
+- High-level tests go in `tests/` directory in each package
+- Use `describe` and `it` API (not `test`)
+- Use `expect` API for assertions
+- Use `assert` only for TypeScript null assertions
+- Use `toMatchSnapshot` for complex output assertions
+- Use `toMatchFileSnapshot` with explicit file path and extension for language-specific output (exclude those files from linting)
+
+---
+
+## Project Setup
+
+### Publishing (Library Projects)
+
+For library projects, publish through GitHub Releases triggered by `bumpp`:
+
+```json
+{
+  "scripts": {
+    "release": "bumpp -r"
+  }
+}
+```
+
+### Documentation (VitePress)
+
+Use VitePress for documentation. Place docs under `docs/` directory.
+
+```
+docs/
+├── .vitepress/
+│   └── config.ts
+├── index.md
+└── guide/
+    └── getting-started.md
+```
+
+Add script to `package.json`:
+
+```json
+{
+  "scripts": {
+    "docs:dev": "vitepress dev docs",
+    "docs:build": "vitepress build docs"
+  }
+}
+```
+
+---
+
+## References
+
+### Project Setup
+
+| Topic | Description | Reference |
+|-------|-------------|-----------|
+| @antfu/eslint-config | ESLint flat config for formatting and linting | [antfu-eslint-config](references/antfu-eslint-config.md) |
+| GitHub Actions | Preferred workflows using sxzz/workflows | [github-actions](references/github-actions.md) |
+| .gitignore | Preferred .gitignore for JS/TS projects | [gitignore](references/gitignore.md) |
+| VS Code Extensions | Recommended extensions for development | [vscode-extensions](references/vscode-extensions.md) |
+
+### Development
+
+| Topic | Description | Reference |
+|-------|-------------|-----------|
+| App Development | Preferences for Vue/Vite/Nuxt/UnoCSS web applications | [app-development](references/app-development.md) |
+| Library Development | Preferences for bundling and publishing TypeScript libraries | [library-development](references/library-development.md) |
+| Monorepo | pnpm workspaces, centralized alias, Turborepo | [monorepo](references/monorepo.md) |