@thinkingai/ae-cli 6.0.30 → 6.0.31

package/skills/ae-team/SKILL.md

@@ -30,7 +30,7 @@ Output and errors:
 
 Safety constraints:
 - Read commands (`+list`, `+list-templates`, `+list-projects`, `+run-result`, `+run-artifacts`, `+ai-generate`) can execute directly once required IDs are known.
-- Write commands require explicit user intent and keep the confirmation prompt by default. Pass `--yes` only in fully automated pipelines.
+- Ordinary `write` commands require explicit user intent but no CLI confirmation. Only `high-risk-write` commands use the confirmation gate and may receive `--yes` after explicit user authorization.
 - Never invent team IDs, run IDs, `agentId` values, `mcpServerIds`, `skillIds`, `knowledgeBaseIds`, project IDs, or any resource identifiers. Discover them with list commands or accept them from the user.
 
 ## When to Use
@@ -105,7 +105,7 @@ ae-cli team +list
 ae-cli team +list-projects
 
 # 3. Start a run
-ae-cli team +run-start --team-id <team_id> --input "分析上周用户留存数据" --yes
+ae-cli team +run-start --team-id <team_id> --input "分析上周用户留存数据"
 
 # 4. Stream until done (blocks; no polling needed)
 ae-cli team +run-watch --id <run_id>
@@ -114,7 +114,7 @@ ae-cli team +run-watch --id <run_id>
 # exit 2 → waiting_user → go to step 4a
 
 # 4a. Handle waiting_user: read pendingQuestion from stdout, get user's answer, reply, re-watch
-ae-cli team +run-reply --id <run_id> --input "<user_answer>" --yes
+ae-cli team +run-reply --id <run_id> --input "<user_answer>"
 ae-cli team +run-watch --id <run_id>   # repeat until exit 0 or 1
 
 # 5. Retrieve artifacts
@@ -128,23 +128,23 @@ ae-cli team +run-artifacts --id <run_id> --include-content true
 ae-cli team +ai-generate --prompt "需要一个分析用户行为并自动生成留存报告的团队"
 
 # 2. Create the team (paste / adjust the returned config)
-ae-cli team +create --name "留存分析团队" --config '<config_json>' --yes
+ae-cli team +create --name "留存分析团队" --config '<config_json>'
 
 # 3. Start a run
-ae-cli team +run-start --team-id <new_team_id> --input "分析本月留存" --yes
+ae-cli team +run-start --team-id <new_team_id> --input "分析本月留存"
 ```
 
 ### Workflow C — Multi-turn chat
 
 ```bash
 # First turn
-ae-cli team +run-chat --team-id <team_id> --input "帮我分析DAU趋势" --yes
+ae-cli team +run-chat --team-id <team_id> --input "帮我分析DAU趋势"
 
 # If run status is waiting_user, reply:
-ae-cli team +run-reply --id <run_id> --input "请重点分析周末下降原因" --yes
+ae-cli team +run-reply --id <run_id> --input "请重点分析周末下降原因"
 
 # Continue same session
-ae-cli team +run-chat --team-id <team_id> --session-id <session_id> --input "给出优化建议" --yes
+ae-cli team +run-chat --team-id <team_id> --session-id <session_id> --input "给出优化建议"
 ```
 
 ### Workflow D — Use a template to create a team
@@ -154,7 +154,7 @@ ae-cli team +run-chat --team-id <team_id> --session-id <session_id> --input "给
 ae-cli team +list-templates --locale zh
 
 # 2. Create from a template's config
-ae-cli team +create --name "我的分析团队" --config '<template_config>' --yes
+ae-cli team +create --name "我的分析团队" --config '<template_config>'
 ```
 
 ## Quick Verification

package/skills/ae-team/references/create.md

@@ -13,7 +13,7 @@ Domain: **Team management / write**
 - `--name` must be 1–100 characters.
 - `--description` must be ≤2000 characters if provided.
 - `--scope` must be `personal` or `company` if provided; defaults to `personal` on the server.
-- Write operation: keep the confirmation prompt unless `--yes` is explicitly requested.
+- This is an ordinary `write` operation and does not require CLI confirmation.
 
 ## TeamConfig Structure
 
@@ -66,7 +66,7 @@ ae-cli team +create \
   --name "日报分析团队" \
   --config '{"version":1,"mode":"serial","steps":[{"id":"s1","name":"分析师","agentId":"xxx","prompt":"分析数据","role":"agent"}]}'
 
-ae-cli team +create --name "My Team" --config '...' --scope company --yes
+ae-cli team +create --name "My Team" --config '...' --scope company
 ae-cli team +create --dry-run --name "Test" --config '{}'
 ```
 

package/skills/ae-team/references/delete.md

@@ -15,9 +15,9 @@ Domain: **Team management / write**
 
 ## Command
 ```bash
-ae-cli team +delete --id <team_id>
+ae-cli team +delete --id <team_id> --dry-run
+# Summarize the target and impact, then wait for explicit user confirmation.
 ae-cli team +delete --id <team_id> --yes
-ae-cli team +delete --dry-run --id <team_id>
 ```
 
 ## Parameters
@@ -31,7 +31,7 @@ ae-cli team +delete --dry-run --id <team_id>
 - Do not retry delete until all active runs have reached a terminal status.
 
 ## Next Steps on Failure
-- `409 Conflict`: cancel active runs first (`+run-cancel --id <run_id> --yes`), then retry.
+- `409 Conflict`: cancel active runs first (`+run-cancel --id <run_id>`), then retry.
 - `404`: team already deleted or wrong ID — re-run `+list` to verify.
 
 ## Recommended Chaining

package/skills/ae-team/references/run-cancel.md

@@ -10,13 +10,13 @@ Domain: **TeamRun execution / write**
 
 ## Mandatory Rules (MUST)
 - `--id` is required. Obtain the real run ID from a previous `+run-start` or `+run-chat` response — do not guess.
-- Write operation: keep the confirmation prompt unless `--yes` is explicitly requested.
+- This is an ordinary `write` operation and does not require CLI confirmation.
 - Cancellation is irreversible. To re-run the same task, call `+run-start` again.
 
 ## Command
 ```bash
 ae-cli team +run-cancel --id <run_id>
-ae-cli team +run-cancel --id <run_id> --yes
+ae-cli team +run-cancel --id <run_id>
 ae-cli team +run-cancel --dry-run --id <run_id>
 ```
 
@@ -34,5 +34,5 @@ ae-cli team +run-cancel --dry-run --id <run_id>
 - Already terminal: the run has already completed, failed, or been cancelled — no action needed.
 
 ## Recommended Chaining
-- `+run-result` (verify status) → `+run-cancel --yes`
+- `+run-result` (verify status) → `+run-cancel`
 - `+run-cancel` (clear active runs) → `+delete` (team)

package/skills/ae-team/references/run-chat.md

@@ -13,16 +13,16 @@ Domain: **TeamRun execution / write**
 - `--team-id` is required. Obtain the real team ID via `+list` — do not guess.
 - `--input` is required. Pass the user's message verbatim.
 - To continue an existing session, pass `--session-id` with the `session.id` from the previous turn.
-- Write operation: keep the confirmation prompt unless `--yes` is explicitly requested.
+- This is an ordinary `write` operation and does not require CLI confirmation.
 - After each turn, capture `session.id` and `run.id` for subsequent turns or replies.
 
 ## Command
 ```bash
 # First turn (starts a new session)
-ae-cli team +run-chat --team-id <team_id> --input "帮我分析最近的DAU趋势" --yes
+ae-cli team +run-chat --team-id <team_id> --input "帮我分析最近的DAU趋势"
 
 # Continue the same session
-ae-cli team +run-chat --team-id <team_id> --session-id <session_id> --input "继续上次的分析" --yes
+ae-cli team +run-chat --team-id <team_id> --session-id <session_id> --input "继续上次的分析"
 
 ae-cli team +run-chat --dry-run --team-id <team_id> --input "test"
 ```
@@ -43,7 +43,7 @@ ae-cli team +run-chat --dry-run --team-id <team_id> --input "test"
 ## Waiting User Flow
 ```
 +run-chat → run.status = waiting_user
-→ +run-reply --id <run_id> --input "..." --yes
+→ +run-reply --id <run_id> --input "..."
 → poll +run-result until terminal
 → optionally continue with +run-chat --session-id <session_id>
 ```

package/skills/ae-team/references/run-reply.md

@@ -11,13 +11,13 @@ Domain: **TeamRun execution / write**
 ## Mandatory Rules (MUST)
 - `--id` is required. The run **must be in `waiting_user` state** — sending a reply to a run in any other state will fail.
 - `--input` is required (1–50000 chars). Pass the user's reply verbatim.
-- Write operation: keep the confirmation prompt unless `--yes` is explicitly requested.
+- This is an ordinary `write` operation and does not require CLI confirmation.
 - After replying, poll `+run-result` until the run reaches a terminal status.
 
 ## Command
 ```bash
-ae-cli team +run-reply --id <run_id> --input "请继续，使用方案A" --yes
-ae-cli team +run-reply --id <run_id> --input "好的，请重点分析周末下降原因" --yes
+ae-cli team +run-reply --id <run_id> --input "请继续，使用方案A"
+ae-cli team +run-reply --id <run_id> --input "好的，请重点分析周末下降原因"
 ae-cli team +run-reply --dry-run --id <run_id> --input "test"
 ```
 

package/skills/ae-team/references/run-start.md

@@ -14,19 +14,18 @@ Domain: **TeamRun execution / write**
 - `--input` is required (1–50000 chars). Pass the user's task description verbatim; do not truncate.
 - JSON array flags (`--project-ids`, `--project-names`, `--space-ids`, etc.) must be valid JSON arrays, e.g. `'["id1","id2"]'`.
 - `--notification` must be valid JSON if provided, e.g. `'{"channels":["feishu"],"feishuChatId":"..."}'`.
-- Write operation: keep the confirmation prompt unless `--yes` is explicitly requested.
+- This is an ordinary `write` operation and does not require CLI confirmation.
 - After starting, capture the returned `id` (run ID) and use it to poll `+run-result`.
 
 ## Command
 ```bash
-ae-cli team +run-start --team-id <team_id> --input "分析上周用户留存情况，生成报告" --yes
+ae-cli team +run-start --team-id <team_id> --input "分析上周用户留存情况，生成报告"
 
 ae-cli team +run-start \
   --team-id <team_id> \
   --input "分析本月DAU趋势" \
   --notification '{"channels":["feishu"],"feishuChatId":"oc_xxx"}' \
-  --save-to-kb-id <kb_id> \
-  --yes
+  --save-to-kb-id <kb_id>
 
 ae-cli team +run-start --dry-run --team-id <team_id> --input "test"
 ```
@@ -59,7 +58,7 @@ ae-cli team +run-watch --id <run_id>
 # exit 0 → completed/partial_success
 # exit 1 → failed/cancelled/stale
 # exit 2 → waiting_user: read pendingQuestion from stdout, reply, re-watch
-ae-cli team +run-reply --id <run_id> --input "<user_answer>" --yes
+ae-cli team +run-reply --id <run_id> --input "<user_answer>"
 ae-cli team +run-watch --id <run_id>
 ```
 

package/skills/ae-team/references/run-watch.md

@@ -58,7 +58,7 @@ ae-cli team +run-watch --id <run_id>
 
 # 2. Read pendingQuestion from stdout, present to user, collect answer
 # 3. Submit the reply
-ae-cli team +run-reply --id <run_id> --input "<user_answer>" --yes
+ae-cli team +run-reply --id <run_id> --input "<user_answer>"
 
 # 4. Resume watching
 ae-cli team +run-watch --id <run_id>

package/skills/ae-team/references/update.md

@@ -13,13 +13,13 @@ Domain: **Team management / write**
 - At least one optional field must be provided in addition to `--id`.
 - `--config` replaces the entire TeamConfig; provide the complete new config, not a partial patch.
 - `--scope` must be `personal` or `company` if provided.
-- Write operation: keep the confirmation prompt unless `--yes` is explicitly requested.
+- This is an ordinary `write` operation and does not require CLI confirmation.
 
 ## Command
 ```bash
 ae-cli team +update --id <team_id> --name "新名称"
 ae-cli team +update --id <team_id> --enabled false
-ae-cli team +update --id <team_id> --config '<full_new_config_json>' --yes
+ae-cli team +update --id <team_id> --config '<full_new_config_json>'
 ae-cli team +update --dry-run --id <team_id> --name "Test"
 ```
 

package/dist/chunk-P2JRP6HJ.js

@@ -1,42 +0,0 @@
-import {
-  resolveGatewayDomain
-} from "./chunk-CWZUGF2J.js";
-import {
-  buildCapabilityGatewayUrl,
-  executeCapability
-} from "./chunk-THBBNYXI.js";
-
-// src/core/capability-command.ts
-function createCapabilityCommand(config) {
-  return {
-    service: config.cliService,
-    resource: config.resource,
-    command: config.command,
-    description: config.description,
-    flags: config.flags,
-    risk: config.risk,
-    validate: config.validate,
-    dryRun: (ctx) => {
-      const gatewayDomain = resolveGatewayDomain(config.cliService, config.gatewayDomain);
-      const input = config.buildInput(ctx);
-      return {
-        method: "POST",
-        url: buildCapabilityGatewayUrl(
-          ctx.host(),
-          gatewayDomain,
-          `capabilities/${config.capabilityId}/dry-run`
-        ),
-        body: { input }
-      };
-    },
-    execute: async (ctx) => {
-      const gatewayDomain = resolveGatewayDomain(config.cliService, config.gatewayDomain);
-      const input = config.buildInput(ctx);
-      return executeCapability(ctx.host(), gatewayDomain, config.capabilityId, input);
-    }
-  };
-}
-
-export {
-  createCapabilityCommand
-};

package/dist/chunk-S5XN6KEX.js

@@ -1,42 +0,0 @@
-import {
-  resolveGatewayDomain
-} from "./chunk-CWZUGF2J.js";
-import {
-  buildCapabilityGatewayUrl,
-  executeCapability
-} from "./chunk-OJR23CIK.js";
-
-// src/core/capability-command.ts
-function createCapabilityCommand(config) {
-  return {
-    service: config.cliService,
-    resource: config.resource,
-    command: config.command,
-    description: config.description,
-    flags: config.flags,
-    risk: config.risk,
-    validate: config.validate,
-    dryRun: (ctx) => {
-      const gatewayDomain = resolveGatewayDomain(config.cliService, config.gatewayDomain);
-      const input = config.buildInput(ctx);
-      return {
-        method: "POST",
-        url: buildCapabilityGatewayUrl(
-          ctx.host(),
-          gatewayDomain,
-          `capabilities/${config.capabilityId}/dry-run`
-        ),
-        body: { input }
-      };
-    },
-    execute: async (ctx) => {
-      const gatewayDomain = resolveGatewayDomain(config.cliService, config.gatewayDomain);
-      const input = config.buildInput(ctx);
-      return executeCapability(ctx.host(), gatewayDomain, config.capabilityId, input);
-    }
-  };
-}
-
-export {
-  createCapabilityCommand
-};