refactor(examples): fold plan mode into ACP demo

2026-07-21 00:40:15 +08:00
parent 0022979e4c
commit c3f4332b8d
96 changed files with 990 additions and 364 deletions
@@ -33,6 +33,27 @@ The available tools:

 ```ts
 declare const tools: {
+  /** Ask the user a concise question when you need confirmation, a choice, or missing information before proceeding. Send one or more questions, each with a stable id that will be echoed in the answer. */
+  ask_user_question(args: {
+    /** Questions to ask the user before continuing. */
+    questions: {
+      /** Stable id for this question; echoed in the answer. */
+      id: string;
+      /** The specific question to ask the user. */
+      question: string;
+      /** Optional short heading for the question, such as "Confirm" or "Choose Mode". */
+      header?: string;
+      /** Optional choices to show the user. If you recommend one, put it first and append "(Recommended)" to that label. */
+      options?: {
+        /** Short user-facing option label. */
+        label: string;
+        /** One sentence explaining the tradeoff or impact. */
+        description?: string;
+      }[];
+      /** Whether the user may select more than one option. Defaults to false. */
+      multi_select?: boolean;
+    }[];
+  }): Promise<string>;
  /** Execute a bash command (`bash -c`) and return its stdout/stderr. Each call runs in a fresh shell: no state (cwd, variables, functions) persists between calls — pass `workdir` instead of using `cd`. Non-zero exits are reported as `[exit code: N]`. Current harness environment facts are exposed through managed `$DSH_*` variables; inspect them when needed. Commands may run under a file sandbox; a blocked file operation is reported as `[sandbox: file access denied under <mode> mode]` — a policy denial, not a bug in the command; do not retry another way. Long output is truncated to its tail; the full output is saved to a file whose path is reported when available. Set `run_in_background: true` for long-running commands: the call returns a task id immediately; read its output with `task_output` and stop it with `task_kill`. Attempting a command the sandbox may deny is safe and expected: run it and read the marker rather than assuming the denial. When a command is denied and a wider mode would let it succeed, escalate immediately in the same turn — the one sanctioned exception to a denial: retry the exact same command once with `sandbox_permissions` (the narrowest wider mode that suffices) plus a one-sentence `justification`. Do not detour through chat to ask permission first — the approval prompt raised by that retry is how the user consents. If the session states approval prompts are disabled, there is no exception: a denial is final — do not set `sandbox_permissions`. Never escalate speculatively: ground the request in a real denial — normally the one this command just hit; escalating up front is fine only when this session already denied the same access. A rejected escalation is final for that command — stop and explain, never work around it — but it does not forbid attempting or escalating other commands later. */
  bash(args: {
    /** The bash command to execute. */