copilotkit 4.10.0 → 4.10.1

package/README.md

@@ -229,6 +229,14 @@ npx --yes copilotkit@latest onboard start \
 | `add-chat-suggestions`   | Configure and send visible chat suggestions                 |
 | `add-voice`              | Add documented voice transcription to the existing composer |
 | `add-realtime-sync`      | Prove managed thread changes sync between active clients    |
+| `add-channels`           | Connect Slack or Teams and prove a real mention             |
+
+Run `copilotkit channels setup` to copy `onboard start --intent add-channels` with a run id.
+`add-channels` does not need a CopilotKit web app. The graph asks Slack or Teams.
+Its first prompt records the coding agent with `onboard identify`, including when
+the entry command omitted `--coding-agent`. Channel setup stage events include
+the existing `onboarding_run_id` when the command runs inside an onboarding run;
+standalone commands omit it. These events use the CLI's existing telemetry consent gate.
 
 The intent describes the developer's requested outcome, not a claim about the
 current project state. Each path inspects the app first: it preserves a proven
@@ -362,14 +370,13 @@ copilotkit channels setup
 copilotkit channels setup --no-clipboard
 ```
 
+The command copies `onboard start --intent add-channels` with a run id.
 It installs the `channels-setup` skill, then prints a one-line prompt to paste
 into your coding agent and copies it to your clipboard. The prompt is always
 printed, so you can read it before handing it over. Pass `--no-clipboard` in a
 headless or remote shell.
 
-Everything the run needs is in the skill, so the prompt only names the skill and
-the goal. It does not name a provider: Slack or Microsoft Teams is the skill's
-own first question.
+The copied command does not name a provider. The graph asks Slack or Teams.
 
 Only the prompt goes to stdout. The line introducing it and the clipboard result
 go to stderr, so `copilotkit channels setup > prompt.txt` gives you the payload

package/cli-build-info.json

@@ -2,20 +2,20 @@
   "schemaVersion": 1,
   "package": {
     "name": "copilotkit",
-    "version": "4.10.0"
+    "version": "4.10.1"
   },
   "intelligence": {
-    "commit": "c8e38c8634104047e47545c1ed45a21c259a8658"
+    "commit": "b5b41dba88259cb723cfd2560be82b234417efa7"
   },
   "copilotKit": {
-    "submittedInput": "ce490419d0",
-    "commit": "ce490419d046abe697438b070a99ad5d674365cc"
+    "submittedInput": "7e6964f",
+    "commit": "7e6964fc11092b685bbea62bc331d5d177b738c1"
   },
   "channel": "production",
-  "triggeringActor": "BenTaylorDev",
+  "triggeringActor": "AlemTuzlak",
   "workflow": {
-    "runId": "35011911410",
-    "runUrl": "https://github.com/CopilotKit/Intelligence/actions/runs/35011911410"
+    "runId": "35080956003",
+    "runUrl": "https://github.com/CopilotKit/Intelligence/actions/runs/35080956003"
   },
   "validationResult": "passed",
   "ag2": {
@@ -24,5 +24,5 @@
     "revision": "main",
     "pinned": false
   },
-  "builtAt": "2026-09-15T19:10:59Z"
+  "builtAt": "2026-09-16T09:44:44Z"
 }

package/index.js

@@ -96,14 +96,14 @@ function getTelemetryEndpointUrl() {
 }
 function getBuildInfo() {
   return {
-    version: true ? "4.10.0" : "dev",
-    buildNumber: true ? "35011911410" : "dev",
-    commitSha: true ? "c8e38c8634104047e47545c1ed45a21c259a8658" : "dev",
+    version: true ? "4.10.1" : "dev",
+    buildNumber: true ? "35080956003" : "dev",
+    commitSha: true ? "b5b41dba88259cb723cfd2560be82b234417efa7" : "dev",
     copilotKitCommit: getTemplateRef()
   };
 }
 function getTemplateRef() {
-  return true ? "ce490419d046abe697438b070a99ad5d674365cc" : "main";
+  return true ? "7e6964fc11092b685bbea62bc331d5d177b738c1" : "main";
 }
 function getC15tBackendUrl() {
   return true ? "https://calm-hazelnut-joy-copilotkit.inth.app" : "";
@@ -66837,7 +66837,7 @@ var require_websocket = __commonJS({
     var http4 = __require("http");
     var net = __require("net");
     var tls = __require("tls");
-    var { randomBytes: randomBytes3, createHash: createHash8 } = __require("crypto");
+    var { randomBytes: randomBytes4, createHash: createHash8 } = __require("crypto");
     var { Duplex, Readable: Readable5 } = __require("stream");
     var { URL: URL7 } = __require("url");
     var PerMessageDeflate2 = require_permessage_deflate();
@@ -67384,7 +67384,7 @@ var require_websocket = __commonJS({
         }
       }
       const defaultPort = isSecure ? 443 : 80;
-      const key = randomBytes3(16).toString("base64");
+      const key = randomBytes4(16).toString("base64");
       const request = isSecure ? https2.request : http4.request;
       const protocolSet = /* @__PURE__ */ new Set();
       let perMessageDeflate;
@@ -92313,7 +92313,8 @@ function recordChannelsStage(input) {
       // the builder writes every key explicitly from its input so customer
       // content cannot leak in by construction, and reading ambient process
       // state inside it would break that guarantee. Both values are booleans.
-      ...currentCliStateProperties(input.command ?? "channels")
+      ...currentCliStateProperties(input.command ?? "channels"),
+      ...currentOnboardingRunProperties()
     }
   });
 }
@@ -97856,13 +97857,15 @@ var init_clipboard = __esm({
 });
 
 // apps/cli/src/services/agent-prompt.ts
+import { randomBytes as randomBytes2 } from "node:crypto";
 function buildSkillsOnboardPrompt() {
   return SKILLS_ONBOARD_AGENT_PROMPT;
 }
 function buildChannelsSetupPrompt() {
-  return CHANNELS_SETUP_PROMPT;
+  const runId = randomBytes2(9).toString("base64url");
+  return `npx --yes copilotkit@latest onboard start --intent add-channels --run=${runId}`;
 }
-var SKILLS_ONBOARD_AGENT_PROMPT, CHANNELS_SETUP_SKILL, CHANNELS_SETUP_PROMPT;
+var SKILLS_ONBOARD_AGENT_PROMPT, CHANNELS_SETUP_SKILL;
 var init_agent_prompt = __esm({
   "apps/cli/src/services/agent-prompt.ts"() {
     "use strict";
@@ -97876,7 +97879,6 @@ Use the copilotkit-setup skill to:
 
 Start by inspecting my repo, then walk me through the setup.`;
     CHANNELS_SETUP_SKILL = "channels-setup";
-    CHANNELS_SETUP_PROMPT = `Use the \`${CHANNELS_SETUP_SKILL}\` skill to set up a Channel for this project.`;
   }
 });
 
@@ -141620,7 +141622,7 @@ var require_websocket2 = __commonJS({
     var http4 = __require("http");
     var net = __require("net");
     var tls = __require("tls");
-    var { randomBytes: randomBytes3, createHash: createHash8 } = __require("crypto");
+    var { randomBytes: randomBytes4, createHash: createHash8 } = __require("crypto");
     var { Duplex, Readable: Readable5 } = __require("stream");
     var { URL: URL7 } = __require("url");
     var PerMessageDeflate2 = require_permessage_deflate2();
@@ -142175,7 +142177,7 @@ var require_websocket2 = __commonJS({
         }
       }
       const defaultPort = isSecure ? 443 : 80;
-      const key = randomBytes3(16).toString("base64");
+      const key = randomBytes4(16).toString("base64");
       const request = isSecure ? https2.request : http4.request;
       const protocolSet = /* @__PURE__ */ new Set();
       let perMessageDeflate;
@@ -386886,7 +386888,7 @@ __export(onboard_exports, {
   ONBOARD_SUBCOMMANDS: () => ONBOARD_SUBCOMMANDS,
   runOnboard: () => runOnboard
 });
-import { randomBytes as randomBytes2 } from "node:crypto";
+import { randomBytes as randomBytes3 } from "node:crypto";
 import { parseArgs as parseArgs2 } from "node:util";
 async function runOnboard(argv, dependencies) {
   const deps = dependencies ?? {
@@ -386896,7 +386898,7 @@ async function runOnboard(argv, dependencies) {
     stderr: process.stderr,
     store: configStore,
     cliVersion: getBuildInfo().version,
-    randomRunId: () => randomBytes2(9).toString("base64url"),
+    randomRunId: () => randomBytes3(9).toString("base64url"),
     loadPrompt: loadOnboardingPrompt,
     loadGraphTree: loadOnboardingGraphTree,
     loadStartPrompt: loadOnboardingStartPrompt,

package/onboarding/index.json

@@ -1,7 +1,8 @@
 {
-  "graphTree": "d0d29f5f2ed37dd76f08bb7655e28da124813c2f",
+  "graphTree": "6b3586ba65cfeed7befa35d0c8794713198ac438",
   "intentRoots": {
     "add-a2ui": "feature/a2ui/start",
+    "add-channels": "feature/channels/start",
     "add-chat-suggestions": "feature/chat-suggestions/start",
     "add-learning": "feature/learning/start",
     "add-open-generative-ui": "feature/open-generative-ui/start",
@@ -106,6 +107,30 @@
       "milestone": "feature",
       "name": "feature/a2ui/start"
     },
+    {
+      "edges": [
+        "feature/stop",
+        "feature/channels/proof"
+      ],
+      "milestone": "feature",
+      "name": "feature/channels/implement"
+    },
+    {
+      "edges": [
+        "feature/stop",
+        "feature/complete"
+      ],
+      "milestone": "feature",
+      "name": "feature/channels/proof"
+    },
+    {
+      "edges": [
+        "feature/stop",
+        "feature/channels/implement"
+      ],
+      "milestone": "feature",
+      "name": "feature/channels/start"
+    },
     {
       "edges": [
         "feature/stop",

package/onboarding/prompts/authenticate/start.md

@@ -5,7 +5,7 @@
 Run this before anything else in this prompt, including the welcome message below:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard identify --coding-agent <coding-agent-slug>
+npx --yes copilotkit@4.10.1 onboard identify --coding-agent <coding-agent-slug>
 ```
 
 Report your own product with one short slug, such as `codex` or `claude-code`.
@@ -37,7 +37,7 @@ Every later command must run from the directory this run started in. A command r
 somewhere else, such as a sibling of that directory, is refused rather than answered,
 because the run it belongs to cannot be found from there. That refusal is a step to take,
 not a stop to report: run
-`npx --yes copilotkit@4.10.0 onboard start --run <onboarding_run_id>` in the directory
+`npx --yes copilotkit@4.10.1 onboard start --run <onboarding_run_id>` in the directory
 you are now in, which binds it to the same run, then run the refused command again. Do not
 start a run without that id. A run started without it is a second run, and the work already
 done stops counting toward the first.
@@ -82,7 +82,7 @@ stop no prompt anticipated, including one your own harness causes. Run the frict
 sent.
 
 ```text
-npx --yes copilotkit@4.10.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.10.1 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.
@@ -103,7 +103,7 @@ graph cannot fix.
 
 ## Check sign-in
 
-Run `npx --yes copilotkit@4.10.0 login --json` before any project work. This command
+Run `npx --yes copilotkit@4.10.1 login --json` before any project work. This command
 checks the current session. It starts sign-in only as needed. Treat this as a long-lived
 streaming process. Do not wait for the command to exit before you read its standard output.
 
@@ -139,8 +139,8 @@ Do not use `whoami` for this check. It has no JSON output and some failures exit
 zero. Do not put account tokens or credentials in the conversation.
 
 When sign-in is settled, run
-`npx --yes copilotkit@4.10.0 onboard read research/gather`.
+`npx --yes copilotkit@4.10.1 onboard read research/gather`.
 
 If sign-in stops onboarding, run
-`npx --yes copilotkit@4.10.0 onboard read stopped/run-failed`. It says nothing about
+`npx --yes copilotkit@4.10.1 onboard read stopped/run-failed`. It says nothing about
 whether this project's stack is supported, which is not yet known at this point.

package/onboarding/prompts/conversion/plan.md

@@ -100,7 +100,7 @@ of this journey, and a drawer that lists nothing is not a reason to mint one. Li
 tokens stay a self-hosted concern.
 
 Where this journey's frontend framework ships no threads drawer -- React Native --, the
-fifth item is proved by `npx --yes copilotkit@4.10.0 verify --round-trip`, which sends a
+fifth item is proved by `npx --yes copilotkit@4.10.1 verify --round-trip`, which sends a
 real request and reads the answer back off the thread it landed on. The run says which of
 the two it proved. Do not send a run to the managed Intelligence dashboard to prove this.
 An authenticated browser session at a hosted dashboard is the one thing an agent-driven run
@@ -116,7 +116,7 @@ and passed -- so a run scored on either one was scored on the same fact. Every r
 resolves that condition from, while `licenseStatus` is a compatibility projection of it
 for older thread surfaces and outlives them only until those surfaces go.
 
-Then run `npx --yes copilotkit@4.10.0 onboard read credentials/finalize-plan`.
+Then run `npx --yes copilotkit@4.10.1 onboard read credentials/finalize-plan`.
 
 If a selected page does not load after the second method, run
-`npx --yes copilotkit@4.10.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.1 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/credentials/finalize-plan.md

@@ -23,7 +23,7 @@ stop. Run the friction command without another developer question. The CLI telem
 decides whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.10.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.10.1 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.
@@ -58,7 +58,7 @@ the command refuses one of them from a run that was served that node.
 Run this command with the exact selected slugs:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend>
+npx --yes copilotkit@4.10.1 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend>
 ```
 
 Do not continue if a value is refused. Fix the value from the choices that the earlier
@@ -152,7 +152,7 @@ passes against the wrong one.
 Create it, from the target directory:
 
 ```text
-npx --yes copilotkit@4.10.0 project select --create <name> --json
+npx --yes copilotkit@4.10.1 project select --create <name> --json
 ```
 
 If the command fails as a duplicate, the organization already holds that display name and
@@ -166,13 +166,13 @@ Take this branch only when the developer asks for an existing project, or asks t
 projects they have. Read the choices:
 
 ```text
-npx --yes copilotkit@4.10.0 project list --json
+npx --yes copilotkit@4.10.1 project list --json
 ```
 
 Narrow them:
 
 ```text
-npx --yes copilotkit@4.10.0 project list --search <query> --json
+npx --yes copilotkit@4.10.1 project list --search <query> --json
 ```
 
 With `--json` the payload is the only thing on standard output, so it is safe to parse. Do
@@ -184,7 +184,7 @@ this directory's.
 Then record the project they name, from the target directory:
 
 ```text
-npx --yes copilotkit@4.10.0 project select --project <slug-or-id> --json
+npx --yes copilotkit@4.10.1 project select --project <slug-or-id> --json
 ```
 
 The two flags cannot be combined. A slug that does not exist fails and lists the real ones,
@@ -226,4 +226,4 @@ project-record path and environment path as the credential setup path list. Do n
 to the baseline yet.
 
 When project selection is settled, run
-`npx --yes copilotkit@4.10.0 onboard read credentials/settle-credentials`.
+`npx --yes copilotkit@4.10.1 onboard read credentials/settle-credentials`.

package/onboarding/prompts/credentials/plan.md

@@ -68,26 +68,26 @@ another framework. Do not show the internal route.
 
 Use exactly one matching internal route:
 
-1. AG2: `npx --yes copilotkit@4.10.0 onboard read framework/ag2`
-2. Agno: `npx --yes copilotkit@4.10.0 onboard read framework/agno`
-3. Built-in CopilotKit agent: `npx --yes copilotkit@4.10.0 onboard read framework/built-in`
-4. Claude Agent SDK Python: `npx --yes copilotkit@4.10.0 onboard read framework/claude-sdk-python`
-5. Claude Agent SDK TypeScript: `npx --yes copilotkit@4.10.0 onboard read framework/claude-sdk-typescript`
-6. CrewAI Flows: `npx --yes copilotkit@4.10.0 onboard read framework/crewai-flows`
-7. Deep Agents: `npx --yes copilotkit@4.10.0 onboard read framework/deep-agents`
-8. LangGraph Python: `npx --yes copilotkit@4.10.0 onboard read framework/langgraph-python`
-9. LangGraph FastAPI: `npx --yes copilotkit@4.10.0 onboard read framework/langgraph-fastapi`
-10. LangGraph TypeScript: `npx --yes copilotkit@4.10.0 onboard read framework/langgraph-typescript`
-11. LlamaIndex: `npx --yes copilotkit@4.10.0 onboard read framework/llamaindex`
-12. ADK: `npx --yes copilotkit@4.10.0 onboard read framework/google-adk`
-13. Microsoft Agent Framework Python: `npx --yes copilotkit@4.10.0 onboard read framework/ms-agent-python`
-14. Microsoft Agent Framework .NET: `npx --yes copilotkit@4.10.0 onboard read framework/ms-agent-dotnet`
-15. Mastra: `npx --yes copilotkit@4.10.0 onboard read framework/mastra`
-16. MS Agent Harness .NET: `npx --yes copilotkit@4.10.0 onboard read framework/ms-agent-harness-dotnet`
-17. Pydantic AI: `npx --yes copilotkit@4.10.0 onboard read framework/pydantic-ai`
-18. Strands Agents Python: `npx --yes copilotkit@4.10.0 onboard read framework/strands-python`
-19. Strands Agents TypeScript: `npx --yes copilotkit@4.10.0 onboard read framework/strands-typescript`
+1. AG2: `npx --yes copilotkit@4.10.1 onboard read framework/ag2`
+2. Agno: `npx --yes copilotkit@4.10.1 onboard read framework/agno`
+3. Built-in CopilotKit agent: `npx --yes copilotkit@4.10.1 onboard read framework/built-in`
+4. Claude Agent SDK Python: `npx --yes copilotkit@4.10.1 onboard read framework/claude-sdk-python`
+5. Claude Agent SDK TypeScript: `npx --yes copilotkit@4.10.1 onboard read framework/claude-sdk-typescript`
+6. CrewAI Flows: `npx --yes copilotkit@4.10.1 onboard read framework/crewai-flows`
+7. Deep Agents: `npx --yes copilotkit@4.10.1 onboard read framework/deep-agents`
+8. LangGraph Python: `npx --yes copilotkit@4.10.1 onboard read framework/langgraph-python`
+9. LangGraph FastAPI: `npx --yes copilotkit@4.10.1 onboard read framework/langgraph-fastapi`
+10. LangGraph TypeScript: `npx --yes copilotkit@4.10.1 onboard read framework/langgraph-typescript`
+11. LlamaIndex: `npx --yes copilotkit@4.10.1 onboard read framework/llamaindex`
+12. ADK: `npx --yes copilotkit@4.10.1 onboard read framework/google-adk`
+13. Microsoft Agent Framework Python: `npx --yes copilotkit@4.10.1 onboard read framework/ms-agent-python`
+14. Microsoft Agent Framework .NET: `npx --yes copilotkit@4.10.1 onboard read framework/ms-agent-dotnet`
+15. Mastra: `npx --yes copilotkit@4.10.1 onboard read framework/mastra`
+16. MS Agent Harness .NET: `npx --yes copilotkit@4.10.1 onboard read framework/ms-agent-harness-dotnet`
+17. Pydantic AI: `npx --yes copilotkit@4.10.1 onboard read framework/pydantic-ai`
+18. Strands Agents Python: `npx --yes copilotkit@4.10.1 onboard read framework/strands-python`
+19. Strands Agents TypeScript: `npx --yes copilotkit@4.10.1 onboard read framework/strands-typescript`
 
 If the project has an agent in another framework, or no listed framework fits, keep the
 developer's current agent and run
-`npx --yes copilotkit@4.10.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.1 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/credentials/settle-credentials.md

@@ -11,7 +11,7 @@ friction command without another developer question. The CLI telemetry gate deci
 the report is sent.
 
 ```text
-npx --yes copilotkit@4.10.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.10.1 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.
@@ -47,7 +47,7 @@ skip this step and name the skip, rather than inventing a name.
 Then ask the platform about that id, from the target directory:
 
 ```text
-npx --yes copilotkit@4.10.0 learning containers get <id> --json
+npx --yes copilotkit@4.10.1 learning containers get <id> --json
 ```
 
 The read carries the same availability gate as the create, so it answers the entitlement
@@ -72,7 +72,7 @@ Never invent an id, scrape a dashboard, or treat an arbitrary string as a contai
 Report what the read found, before anything is planned:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase container-surveyed
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase container-surveyed
 ```
 
 Carry the derived id into the planning subagent's handoff, with whether the platform
@@ -102,7 +102,7 @@ protected path list. Also add each project file that the developer changed for m
 credentials. Record them in the baseline from the target app directory:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard protect --path <path>
+npx --yes copilotkit@4.10.1 onboard protect --path <path>
 ```
 
 Pass one `--path` for each. The command captures a digest for each path and never re-reads
@@ -116,7 +116,7 @@ Then re-capture the files this graph wrote itself. For each path the first captu
 as `deferred` that this run has now written, run:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard protect --rebaseline --path <path>
+npx --yes copilotkit@4.10.1 onboard protect --rebaseline --path <path>
 ```
 
 From that point they are protected like any other path, so a later step that rewrites
@@ -135,7 +135,7 @@ environment path. The command below is what to run at that point, from the targe
 directory:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard protect --accept-credential --path <environment path>
+npx --yes copilotkit@4.10.1 onboard protect --accept-credential --path <environment path>
 ```
 
 The command compares the variable names the baseline recorded with the names the file holds
@@ -150,4 +150,4 @@ now. Read its result:
   is not a failed step. It answers the question and the run carries on.
 
 When the credential question is answered, run
-`npx --yes copilotkit@4.10.0 onboard read credentials/write-plan`.
+`npx --yes copilotkit@4.10.1 onboard read credentials/write-plan`.

package/onboarding/prompts/credentials/write-plan.md

@@ -11,7 +11,7 @@ friction command without another developer question. The CLI telemetry gate deci
 the report is sent.
 
 ```text
-npx --yes copilotkit@4.10.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.10.1 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.
@@ -52,7 +52,7 @@ proof subagents:
 Fetch them together with the pages already selected rather than on their own.
 
 Spawn one planning subagent. Tell it to run
-`npx --yes copilotkit@4.10.0 onboard read subagent/create-plan` first and follow the prompt
+`npx --yes copilotkit@4.10.1 onboard read subagent/create-plan` first and follow the prompt
 it returns. If that read fails because the subagent cannot use the shell, stop that subagent.
 Run the same command yourself, then spawn a fresh subagent with the returned prompt and the
 same handoff. Give it the repository findings, selected framework, frontend, model, credential
@@ -63,7 +63,7 @@ Wait for the subagent to finish.
 Continue only if the planning result starts with `Status: passed`. For `Status: failed`,
 send the result back to the planning subagent for repair, up to three attempts. For
 `Status: blocked`, or a third failed result, run
-`npx --yes copilotkit@4.10.0 onboard read stopped/run-failed`. A plan this run cannot
+`npx --yes copilotkit@4.10.1 onboard read stopped/run-failed`. A plan this run cannot
 write is a run that broke, not a stack the documentation does not cover. Do not show or
 ask for approval of a non-pass plan.
 
@@ -87,7 +87,7 @@ that waits at the terminal through all of them for a question that never comes.
 the same message as the plan, and do not turn it into a second question.
 
 If the developer approves the plan, run
-`npx --yes copilotkit@4.10.0 onboard read implementation/build-and-validate`.
+`npx --yes copilotkit@4.10.1 onboard read implementation/build-and-validate`.
 
 If no exact supported path or documentation URL exists, run
-`npx --yes copilotkit@4.10.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.1 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/fallback/best-effort.md

@@ -13,7 +13,7 @@ existing agent or frontend. Send one short report before you stop. Run the frict
 report is sent.
 
 ```text
-npx --yes copilotkit@4.10.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.10.1 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.
@@ -59,13 +59,13 @@ stop.
 
 Use these rules for every protected-path check in this fallback:
 
-- Run `npx --yes copilotkit@4.10.0 onboard audit` from the target app directory.
+- Run `npx --yes copilotkit@4.10.1 onboard audit` from the target app directory.
 - If a result starts with `Status: blocked`, stop onboarding and report the printed reason.
   It proved nothing changed, so do not report a preservation failure.
 - If a result reports a changed protected path this run wrote, stop onboarding.
 - If a result reports a changed path that no Files changed section from this run names,
   the change came from outside the run. Accept it by name with
-  `npx --yes copilotkit@4.10.0 onboard protect --accept-external --path <path>`, run the
+  `npx --yes copilotkit@4.10.1 onboard protect --accept-external --path <path>`, run the
   audit again, and name it in the closing report.
 - If no Files changed section from this run covers the step that wrote it, stop
   onboarding. The proof subagent here returns no such section, so a finding it raises is
@@ -118,13 +118,13 @@ application passes proof. Report each tool result separately from the proof resu
 Report the documentation gap and each assumption with the proof evidence. Do not claim
 that the selected documentation proved an inferred step.
 
-When the proof is complete, run `npx --yes copilotkit@4.10.0 onboard complete`, carrying the
+When the proof is complete, run `npx --yes copilotkit@4.10.1 onboard complete`, carrying the
 surface-check result the proof subagent returned. Pass exactly one flag, matching this
 journey's surface:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard complete --visual-check <outcome>
-npx --yes copilotkit@4.10.0 onboard complete --device-check <outcome>
+npx --yes copilotkit@4.10.1 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.10.1 onboard complete --device-check <outcome>
 ```
 
 `--visual-check` is for a web frontend and takes `performed`, `skipped-no-browser-tool`, or

package/onboarding/prompts/feature/a2ui/implement.md

@@ -18,7 +18,7 @@ without exposing secrets.
 After validation and each repair, run:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard audit
+npx --yes copilotkit@4.10.1 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to change:` is
@@ -29,7 +29,7 @@ with the implementation subagent's `Files changed` section. If that section does
 the path, accept the developer's external change:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.10.1 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -38,24 +38,24 @@ or its report does not settle who changed it, ask the developer to allow the unp
 change. Only after they agree, record their answer:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --yes copilotkit@4.10.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Run the audit again after each accepted or authorized change. If it still fails, or starts
 with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard read feature/stop
+npx --yes copilotkit@4.10.1 onboard read feature/stop
 ```
 
 When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase build-validated
 ```
 
 If validation cannot pass, or this intent needs a prerequisite the app does not have, use
 the feature stop route above without further changes.
 
 Otherwise run
-`npx --yes copilotkit@4.10.0 onboard read feature/a2ui/proof`.
+`npx --yes copilotkit@4.10.1 onboard read feature/a2ui/proof`.

package/onboarding/prompts/feature/a2ui/proof.md

@@ -19,23 +19,23 @@ user's agent response with a hard-coded UI.
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 After the final attempt, report the gate exactly once:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.10.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Use `passed` only for a proved A2UI surface, `failed` for an attempted proof that failed,
-and `skipped` when the proof could not run. Then run `npx --yes copilotkit@4.10.0 onboard audit`.
+and `skipped` when the proof could not run. Then run `npx --yes copilotkit@4.10.1 onboard audit`.
 Continue only when it starts with `Status: passed`.
 
 If the audit fails, never repair, reset, or revert a protected path. Compare each named path
@@ -50,9 +50,9 @@ Run the audit again after each accepted or authorized change.
 If the audit still fails, or starts with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard read feature/stop
+npx --yes copilotkit@4.10.1 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --yes copilotkit@4.10.0 onboard read feature/complete` with the actual browser-proof
+`npx --yes copilotkit@4.10.1 onboard read feature/complete` with the actual browser-proof
 outcome.