copilotkit 4.25.1 → 4.26.0

package/onboarding/index.json

@@ -1,5 +1,5 @@
 {
-  "graphTree": "1a9ef53767a2ceacc3c29b8670490e18776f43e6",
+  "graphTree": "62f012b65ba17a579b853bdbbd55bc81dc4759ac",
   "intentRoots": {
     "add-a2ui": "feature/a2ui/start",
     "add-chat-suggestions": "feature/chat-suggestions/start",
@@ -9,7 +9,7 @@
     "add-rich-threads": "feature/rich-threads/start",
     "add-voice": "feature/voice/start"
   },
-  "packageSpec": "copilotkit@4.25.1",
+  "packageSpec": "copilotkit@4.26.0",
   "root": "authenticate/start",
   "prompts": [
     {

package/onboarding/prompts/authenticate/start.md

@@ -13,7 +13,7 @@ Intelligence has a free Developer plan, and this run needs no paid subscription.
 
 Run each CLI call exactly as written, as its own command: no pipe, `tee`, `&&`, redirect,
 or variable prefix. Every CLI call in this run matches the prefix rule
-`["npx", "--prefer-offline", "--yes", "copilotkit@4.25.1"]`. If a command can request
+`["npx", "--prefer-offline", "--yes", "copilotkit@4.26.0"]`. If a command can request
 escalation with a prefix rule, request this one on the `onboard identify` call. If your
 harness asks the developer to approve commands, tell them one approval of that prefix covers
 every CLI call. Say then that the install, the dev servers, `curl` to the local app, and
@@ -23,7 +23,7 @@ Never add or edit a permission rule or a settings file yourself. That choice bel
 the developer.
 
 If your harness refuses a CLI call without asking the developer, do not retry it or run it
-another way. Report the pause: `npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-developer`.
+another way. Report the pause: `npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer`.
 Name the refused command, ask the developer to approve it or to switch to a
 mode that asks them, and end your turn. When they answer, run it once more.
 That refusal is a pause, not a stop.
@@ -33,7 +33,7 @@ That refusal is a pause, not a stop.
 Run this first, before the welcome message below:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
+npx --prefer-offline --yes copilotkit@4.26.0 onboard identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
 ```
 
 Report your product slug, such as `codex` or `claude-code`.
@@ -76,18 +76,18 @@ you here. Otherwise you hear from me next when the app is running and I hand you
 To self-host on your machine with Docker, say so before you sign in.
 
 That message belongs to the run. Send it only once, including after a second read of this prompt.
-Then run `npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase welcome-sent`.
+Then run `npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase welcome-sent`.
 
 ## Report a stop, wherever it happens
 
 If you stop this run at any point, send one short report before you stop. This includes
 unexpected stops and stops caused by your harness.
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
-Report the pause: `npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-developer`.
+Report the pause: `npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer`.
 A terminal that sends the report itself, or says to file none, overrides this.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.26.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -105,15 +105,15 @@ rule that stopped you says next: send the report, then stop.
 Take the local route only when the developer already asked to run CopilotKit locally,
 with Docker, or self-hosted: in their request, the copied prompt, or a later reply, or
 when this run already recorded local. Then run
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard read deployment/choose-local` instead.
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard read deployment/choose-local` instead.
 
 Otherwise keep managed. Do not ask the developer to choose. Run
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard deployment --choice managed`, then continue with
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard deployment --choice managed`, then continue with
 “Check sign-in”. If it refuses because of a local stack, take the local route.
 
 ## Check sign-in
 
-Run `npx --prefer-offline --yes copilotkit@4.25.1 login --json` before any project work. It checks the
+Run `npx --prefer-offline --yes copilotkit@4.26.0 login --json` before any project work. It checks the
 session and 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.
 
@@ -147,11 +147,11 @@ Read each JSON Lines record as it arrives:
 7. If that process emits `type: failed`, report the error and stop onboarding. On
    `reason: repeated_expiry`, rerun `login` with `--force` only if the developer asks.
 
-On `type: completed`, run `npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase sign-in-settled`
+On `type: completed`, run `npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase sign-in-settled`
 before you continue.
 
 If your harness ends the login process or your turn before the process emits
-`type: completed` or `type: failed`, that is a pause, not a failed sign-in. Report the pause: `npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-developer`.
+`type: completed` or `type: failed`, that is a pause, not a failed sign-in. Report the pause: `npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer`.
 If the process
 still runs, end your turn and wait for the developer to say they signed in, then read the
 same process. If the process ended without emitting `type: failed`, run `login --json`
@@ -162,9 +162,9 @@ conversation.
 
 Research reads only this project and needs no account. Start it as soon as the session is
 valid or the developer has the sign-in page, and keep monitoring the login process while it
-runs: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read research/gather`. If this run already
+runs: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read research/gather`. If this run already
 started the research, do not start it again.
 
 If sign-in stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard read stopped/run-failed`. It does not judge
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard read stopped/run-failed`. It does not judge
 this project's stack.

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 --prefer-offline --yes copilotkit@4.25.1 verify --round-trip`, which sends a
+fifth item is proved by `npx --prefer-offline --yes copilotkit@4.26.0 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 --prefer-offline --yes copilotkit@4.25.1 onboard read credentials/finalize-plan`.
+Then run `npx --prefer-offline --yes copilotkit@4.26.0 onboard read credentials/finalize-plan`.
 
 If a selected page does not load after the second method, run
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.

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

@@ -1,7 +1,7 @@
 # Select the Intelligence project
 
 For a recorded local choice, run
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard read deployment/local-evaluation`.
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard read deployment/local-evaluation`.
 That path obtains approval and connects the local project. Skip hosted selection.
 Keep the implementation and feature-proof requirements.
 
@@ -17,7 +17,7 @@ evidence in one sentence. Keep plan approval a separate, later question.
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
 ```
 
 ## Record the audit cell
@@ -35,7 +35,7 @@ Choose the starting state from the repository findings:
 A run served `proof/oss-baseline` records one of the last two.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend> --model-vendor <model-vendor> --model-vendor-choice <model-vendor-choice>
+npx --prefer-offline --yes copilotkit@4.26.0 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend> --model-vendor <model-vendor> --model-vendor-choice <model-vendor-choice>
 ```
 
 `<model-vendor>` is `openai`, `anthropic`, `google`, or `other`. `<model-vendor-choice>` is
@@ -52,7 +52,7 @@ runtime `.env` file, that directory is the target, not the repository root. Do n
 the developer to another terminal.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard credentials --json
+npx --prefer-offline --yes copilotkit@4.26.0 onboard credentials --json
 ```
 
 Every credential this run writes goes to the environment path: the target's `.env`, or
@@ -87,7 +87,7 @@ unless the developer says that it is this app's.
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
 ```
 
 If no developer answers, create with the derived name in `suggestedName`. Never select a
@@ -96,9 +96,9 @@ project from a listing without an answer that names it.
 `--runtime-url` is the URL port research settled, mount path included:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard credentials --create <name> \
+npx --prefer-offline --yes copilotkit@4.26.0 onboard credentials --create <name> \
   --runtime-url http://localhost:<port>/api/copilotkit --json
-npx --prefer-offline --yes copilotkit@4.25.1 onboard credentials --project <slug-or-id> \
+npx --prefer-offline --yes copilotkit@4.26.0 onboard credentials --project <slug-or-id> \
   --runtime-url http://localhost:<port>/api/copilotkit --json
 ```
 
@@ -110,12 +110,12 @@ show only what they asked for, and do not order it by creation time:
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
 ```
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 project list --json
-npx --prefer-offline --yes copilotkit@4.25.1 project list --search <query> --json
+npx --prefer-offline --yes copilotkit@4.26.0 project list --json
+npx --prefer-offline --yes copilotkit@4.26.0 project list --search <query> --json
 ```
 
 `app-directory` means that the key landed where no app reads it. Pick the directory in
@@ -130,11 +130,11 @@ developer answered that line itself. For a line that is still open, ask the deve
 `question.ask` in those words. When `question.alternative` is present, the question offers
 two choices. If the developer chose `question.alternative`, here or in the setup message,
 run the same command again with `question.alternative.rerun` added. The CLI adds
-`question.alternative.ignoreLine` itself, and later steps keep that file without the flag.
+`question.alternative.ignoreLines` itself, and later steps keep that file without the flag.
 If they approve the untrack, add
 `question.ignoreLine` to `question.ignoreFile`. If `question.untrack` is present, run it
 too. Or the developer does both. Report the pause with
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-developer`, end your
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer`, end your
 turn, and wait for the answer. Then run the same command again. Write the key only to
 `question.file`, or to `question.alternative.file` by rerunning with
 `question.alternative.rerun`.
@@ -147,4 +147,4 @@ turn, and wait for the answer. Then run the same command again. Write the key on
   reused. The round-trip proof later runs the authenticated Intelligence checks, so record
   the reused project credentials as unverified in the plan until those checks pass.
 
-Then run `npx --prefer-offline --yes copilotkit@4.25.1 onboard read credentials/settle-credentials`.
+Then run `npx --prefer-offline --yes copilotkit@4.26.0 onboard read credentials/settle-credentials`.

package/onboarding/prompts/credentials/plan.md

@@ -10,7 +10,7 @@ session, do not guess. Ask the framework and model provider lines in one message
 the framework that the repository findings show, or, for an empty project, a documented
 default. For the provider, offer the vendors the framework's CopilotKit pages document.
 Report the pause with
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-developer`, then end your
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer`, then end your
 turn and wait for the answer. A route that records no framework or vendor on purpose is not
 this case: an empty project with Slack or Microsoft Teams, a "Project-defined" vendor, or
 "The agent's own" vendor.
@@ -34,7 +34,7 @@ Microsoft Teams docs page, do not ask the framework question. So does an empty p
 whose frontend `setup/questions` recorded as Slack or Microsoft Teams: it recorded no
 framework. The Channel starter brings its own agent, so an answer here decides nothing. Tell the developer that the Channel
 starter decides the agent, then run
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard read frontend/plan`.
 
 ## Route on the recorded framework
 
@@ -43,27 +43,27 @@ The framework and vendor come from `setup/questions`, with how the vendor was ch
 
 Use exactly one matching internal route:
 
-1. AG2: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/ag2`
-2. Agno: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/agno`
-3. Built-in CopilotKit agent: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/built-in`
-4. Claude Agent SDK Python: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/claude-sdk-python`
-5. Claude Agent SDK TypeScript: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/claude-sdk-typescript`
-6. CrewAI Flows: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/crewai-flows`
-7. Existing AG-UI agent: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/custom-ag-ui`
-8. Deep Agents: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/deep-agents`
-9. LangGraph Python: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/langgraph-python`
-10. LangGraph FastAPI: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/langgraph-fastapi`
-11. LangGraph TypeScript: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/langgraph-typescript`
-12. LlamaIndex: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/llamaindex`
-13. ADK: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/google-adk`
-14. Microsoft Agent Framework Python: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/ms-agent-python`
-15. Microsoft Agent Framework .NET: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/ms-agent-dotnet`
-16. Mastra: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/mastra`
-17. MS Agent Harness .NET: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/ms-agent-harness-dotnet`
-18. Pydantic AI: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/pydantic-ai`
-19. Strands Agents Python: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/strands-python`
-20. Strands Agents TypeScript: `npx --prefer-offline --yes copilotkit@4.25.1 onboard read framework/strands-typescript`
+1. AG2: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/ag2`
+2. Agno: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/agno`
+3. Built-in CopilotKit agent: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/built-in`
+4. Claude Agent SDK Python: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/claude-sdk-python`
+5. Claude Agent SDK TypeScript: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/claude-sdk-typescript`
+6. CrewAI Flows: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/crewai-flows`
+7. Existing AG-UI agent: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/custom-ag-ui`
+8. Deep Agents: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/deep-agents`
+9. LangGraph Python: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/langgraph-python`
+10. LangGraph FastAPI: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/langgraph-fastapi`
+11. LangGraph TypeScript: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/langgraph-typescript`
+12. LlamaIndex: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/llamaindex`
+13. ADK: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/google-adk`
+14. Microsoft Agent Framework Python: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/ms-agent-python`
+15. Microsoft Agent Framework .NET: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/ms-agent-dotnet`
+16. Mastra: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/mastra`
+17. MS Agent Harness .NET: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/ms-agent-harness-dotnet`
+18. Pydantic AI: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/pydantic-ai`
+19. Strands Agents Python: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/strands-python`
+20. Strands Agents TypeScript: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read framework/strands-typescript`
 
 If the project has an agent in another framework that does not speak AG-UI, or no
 listed framework fits, keep the developer's current agent and run
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.

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

@@ -21,7 +21,7 @@ The plan names the model credential variables. Run this from the directory that
 `environmentPath` in the project step's result, with one `--model-key` for each variable:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard credentials --model-key <variable> --json
+npx --prefer-offline --yes copilotkit@4.26.0 onboard credentials --model-key <variable> --json
 ```
 
 If `setup/questions` recorded a key file, add `--env-path <file>` to the first check.
@@ -35,21 +35,22 @@ never prints a value. Read `status`:
 - `ready`: continue. Name each `unsupported` or `undetermined` `reason` in `modelKeys` in
   the closing report. Name each `copiedKeys` entry with the outcome `kept` or `no-value`
   too: that service does not get the checked key. When `outsideRepository` names a file, the app does not load it by
-  itself. By default, plan to copy the key into the app's env file, which git ignores.
+  itself. By default, plan to copy the key into `environmentPath`, the app's env file that git ignores.
   The copy is a file the run writes itself, so list the copy under
   `Files the run writes itself`.
   The developer's approval of the plan is their consent to the copy. After the approval,
   copy the key with the command that `next` names. It has this form:
-  `npx --prefer-offline --yes copilotkit@4.25.1 onboard credentials --model-key <variable> --env-path <file> --copy-to <env file> --json`.
-  It writes the key without printing it. Do not copy the key
+  `npx --prefer-offline --yes copilotkit@4.26.0 onboard credentials --model-key <variable> --env-path <file> --copy-to <env file> --json`.
+  `<env file>` is `environmentPath`, never the tracked `.env` of a run that chose
+  `question.alternative.file`. It writes the key without printing it. Do not copy the key
   yourself, and do not write a `sed`, `grep`, or `cat` command for it. If you cannot run
   the command, for example because a sandbox refuses the path, ask the developer to run it.
   Give them exactly this one line, with `<app directory>` as the directory that holds
   `environmentPath`:
-  `! cd <app directory> && npx --prefer-offline --yes copilotkit@4.25.1 onboard credentials --model-key <variable> --env-path <file> --copy-to <env file>`.
+  `! cd <app directory> && npx --prefer-offline --yes copilotkit@4.26.0 onboard credentials --model-key <variable> --env-path <file> --copy-to <env file>`.
   The command needs no input. Without `!`, they run the same command in a terminal.
   Report the pause with
-  `npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-model-credential`,
+  `npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-model-credential`,
   end your turn, and wait. When they reply, run the same command with `--json` and read `copiedKeys`.
   If the developer declines the copy, the plan has the app read the key from an
   environment variable that the developer sets. The plan then says how to set it. Never
@@ -88,4 +89,4 @@ Never read a file outside the project directory to find a credential: a key foun
 bills another project. Asking for a path is not requesting a secret. A path the developer
 names is theirs to give, including one outside the project. A path this run finds is not.
 
-Then run `npx --prefer-offline --yes copilotkit@4.25.1 onboard read credentials/write-plan`.
+Then run `npx --prefer-offline --yes copilotkit@4.26.0 onboard read credentials/write-plan`.

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

@@ -11,7 +11,7 @@ friction command follows the telemetry setting the developer already chose, so i
 separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.26.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -72,7 +72,7 @@ page is selected yet, add the one for the frontend selected above to the same li
    Native, so the planner proves the thread with `verify --round-trip` instead.
 
 Spawn one planning subagent. Tell it to run
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard read subagent/create-plan` first and follow the
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard read subagent/create-plan` first and follow the
 prompt it returns. Tell it to return at once, and say so, if that read is refused or fails,
 and not to wait for an approval. If it returns that way, stop that subagent. Run the same
 command yourself, then spawn a fresh subagent with the returned prompt and the same handoff.
@@ -87,7 +87,7 @@ 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 --prefer-offline --yes copilotkit@4.25.1 onboard read stopped/run-failed`. A plan this run cannot
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard read stopped/run-failed`. A plan this run cannot
 write is a run that broke, not a stack the documentation does not cover. The exception is
 a blocked result that names `unsupported/no-validated-path`: the planning subagent found
 that no page supports the plan, so take the no-supported-path route at the end of this
@@ -136,17 +136,17 @@ Before you end your turn to wait for the answer, report the pause, each time you
 plan:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-plan-approval
+npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-plan-approval
 ```
 
 After the approval, run the same `onboard credentials --model-key` check again when the plan
 carries a missing model key. On `ready`, continue. If the key is still missing, ask the
 developer `question.ask` in those words. Report the pause with
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-model-credential`, end
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-model-credential`, end
 your turn, and run the check again when they answer.
 
 If the developer approves the plan, run
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard read implementation/build-and-validate`.
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard read implementation/build-and-validate`.
 
 If no exact supported path or documentation URL exists, run
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/deployment/choose-local.md

@@ -9,15 +9,15 @@ A local request can arrive after this run created a hosted project: `init --crea
 Tell the developer that this run already created a hosted project, so it stays managed.
 Return to the step you were on.
 
-First run `npx --prefer-offline --yes copilotkit@4.25.1 local --help`. If it does not list `setup`
+First run `npx --prefer-offline --yes copilotkit@4.26.0 local --help`. If it does not list `setup`
 ("Configure model access and install or resume the local stack"), this release has no
 local evaluation. Tell the developer so, and keep managed. If this run has not recorded
-managed yet, run `npx --prefer-offline --yes copilotkit@4.25.1 onboard deployment --choice managed`.
+managed yet, run `npx --prefer-offline --yes copilotkit@4.26.0 onboard deployment --choice managed`.
 Then return to “Check sign-in” in the start prompt. If a login process from it still
 runs, keep reading that process and start no second one. Otherwise record the choice:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard deployment --choice local
+npx --prefer-offline --yes copilotkit@4.26.0 onboard deployment --choice local
 ```
 
 Explain these conditions before sign-in:
@@ -46,10 +46,10 @@ and Learning starts its first run only after 15 conversations. Offer these choic
 
 1. Configure later, the default. Install with `--defer-model`. In the closing report, write
    "Learning configuration incomplete". Name the command that adds the model later:
-   `npx --prefer-offline --yes copilotkit@4.25.1 local setup`, run in a terminal in the app directory.
+   `npx --prefer-offline --yes copilotkit@4.26.0 local setup`, run in a terminal in the app directory.
 2. Guided setup. If the developer named Learning as a goal, offer it first. Install
    the stack with `--defer-model`. After the stack is ready, the developer runs
-   `npx --prefer-offline --yes copilotkit@4.25.1 local setup` in their own terminal window, in the app
+   `npx --prefer-offline --yes copilotkit@4.26.0 local setup` in their own terminal window, in the app
    directory. Never give it as a `!` line: its guided prompt needs a terminal, and a coding
    agent's shell has none. The prompt asks for the model and its key, and it saves them
    privately. On a running stack, it restarts only Learning. Do not ask the developer to
@@ -60,7 +60,7 @@ and Learning starts its first run only after 15 conversations. Offer these choic
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
 ```
 
 Record the model choice, and any candidate path, in the plan, but no secret values.
@@ -74,7 +74,7 @@ If the managed sign-in message was already sent, send this once and no other sig
 message: “You asked to run it locally, so this project gets no managed CopilotKit project.
 Signing in only gets the renewable evaluation license.”
 
-Otherwise run `npx --prefer-offline --yes copilotkit@4.25.1 login --json`. Follow the streaming sign-in
+Otherwise run `npx --prefer-offline --yes copilotkit@4.26.0 login --json`. Follow the streaming sign-in
 protocol from “Check sign-in” in the start prompt: open the first authentication URL
 once, keep the same process running, and continue only after its completed record.
 When the first authentication URL arrives, send this message in place of the managed
@@ -82,9 +82,9 @@ sign-in message: “Sign in to get the renewable evaluation license. Your local
 will use CLI approval.”
 On failed or declined sign-in, take the failure path below.
 
-After sign-in completes, report it: `npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase sign-in-settled`.
+After sign-in completes, report it: `npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase sign-in-settled`.
 Then continue with
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard read research/gather`, unless research already started.
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard read research/gather`, unless research already started.
 If it already started, return to the step you were on. `starter/clone` and
 `credentials/finalize-plan` each have a branch for a recorded local choice.
 Keep the local choice and collected paths in the run's plan and worker context.
@@ -92,4 +92,4 @@ Keep the local choice and collected paths in the run's plan and worker context.
 ## Failure path
 
 If sign-in fails or is declined, stop before cluster creation.
-Run `npx --prefer-offline --yes copilotkit@4.25.1 onboard read stopped/run-failed`.
+Run `npx --prefer-offline --yes copilotkit@4.26.0 onboard read stopped/run-failed`.

package/onboarding/prompts/deployment/local-evaluation.md

@@ -25,7 +25,7 @@ does not authorize replacing an existing app's connection.
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
 ```
 
 ## Run the shared installer
@@ -33,7 +33,7 @@ npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting
 From the exact app directory, use the collected model choice:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 local setup --defer-model --json
+npx --prefer-offline --yes copilotkit@4.26.0 local setup --defer-model --json
 ```
 
 For supplied model access, replace `--defer-model` with `--model-config <private-file>`.
@@ -51,7 +51,7 @@ A copied app needs explicit `--share-stack`. Do not infer sharing from a copied
 After setup reports the stack ready, run the approved connection step from that directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 local connect --approve-connection --json
+npx --prefer-offline --yes copilotkit@4.26.0 local connect --approve-connection --json
 ```
 
 Read the local `.copilotkit/project.json` for its project ID and slug. Do not run hosted
@@ -71,7 +71,7 @@ stack is ready. Then:
 Ask the developer to run this command in their own terminal window, in the app directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 local setup
+npx --prefer-offline --yes copilotkit@4.26.0 local setup
 ```
 
 Do not give it as a `!` line, and do not run it yourself. Its guided model prompt needs a
@@ -80,9 +80,9 @@ changes nothing. The prompt asks for the model and its key, and it saves them pr
 On a running stack, it restarts only Learning. Do not ask for a model file.
 
 Say that the run continues when they reply or resume this session. Report the pause with
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-model-credential`, end your
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-model-credential`, end your
 turn, and wait. When the developer replies, run
-`npx --prefer-offline --yes copilotkit@4.25.1 local status --json` and read `learning.configuration`.
+`npx --prefer-offline --yes copilotkit@4.26.0 local status --json` and read `learning.configuration`.
 
 If the model is still missing or was deferred, report “Learning configuration incomplete”
 and name the same command, run in a terminal window. No Learning run is required to finish
@@ -96,6 +96,6 @@ must not block Threads, the dashboard, or later Learning configuration.
 If the developer cancels the connection, run `local cancel --json` from the app directory.
 Report conflict names only. Keep the stack unless deletion is separately confirmed.
 
-Continue with `npx --prefer-offline --yes copilotkit@4.25.1 onboard read credentials/settle-credentials`.
+Continue with `npx --prefer-offline --yes copilotkit@4.26.0 onboard read credentials/settle-credentials`.
 For this local route, skip the hosted selection-result checks and use the local project
 record. Continue the existing implementation and proof paths against local endpoints.

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

@@ -14,7 +14,7 @@ you stop. The friction command follows the telemetry setting the developer alrea
 so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.26.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -61,7 +61,7 @@ or frontend, stop onboarding.
 If the CLI prints `## Stop: this run deleted or moved the developer's work` instead of a
 step, show the developer the list it printed, and run what they choose:
 the `onboard restore` command the tripwire stop prints, which names each deleted file, or
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard tripwire --continue`. Then read the step again. If
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard tripwire --continue`. Then read the step again. If
 you cannot ask, stop onboarding. Never repair, reset, or revert a file the developer changed
 outside this run.
 
@@ -110,16 +110,16 @@ that the selected documentation proved an inferred step.
 Record what the proof returned before you complete:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.26.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
-When the proof is complete, run `npx --prefer-offline --yes copilotkit@4.25.1 onboard complete`, carrying the
+When the proof is complete, run `npx --prefer-offline --yes copilotkit@4.26.0 onboard complete`, carrying the
 surface-check result the proof subagent returned. Pass exactly one of `--visual-check` or
 `--device-check`, matching this journey's surface:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard complete --visual-check <outcome>
-npx --prefer-offline --yes copilotkit@4.25.1 onboard complete --device-check <outcome>
+npx --prefer-offline --yes copilotkit@4.26.0 onboard complete --visual-check <outcome>
+npx --prefer-offline --yes copilotkit@4.26.0 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

@@ -24,7 +24,7 @@ That result is a question for the developer. Name the file and why the work need
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
 ```
 
 Then end your turn and wait for the developer's answer. If they allow it, spawn a fresh
@@ -34,16 +34,16 @@ cannot ask, or the developer declines, take the feature stop route below.
 If the CLI prints `## Stop: this run deleted or moved the developer's work` instead of
 a step, show the developer the list it printed, and run what they choose:
 the `onboard restore` command the tripwire stop prints, which names each deleted file, or
-`npx --prefer-offline --yes copilotkit@4.25.1 onboard tripwire --continue`. Then read the step again.
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard tripwire --continue`. Then read the step again.
 
 To route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.26.0 onboard read feature/stop
 ```
 
 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 --prefer-offline --yes copilotkit@4.25.1 onboard read feature/a2ui/proof`.
+`npx --prefer-offline --yes copilotkit@4.26.0 onboard read feature/a2ui/proof`.

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

@@ -12,7 +12,7 @@ The approval is a wait for the developer. Before you end your turn to wait, repo
 pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
 ```
 
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
@@ -49,7 +49,7 @@ renders a compact visible surface. Ask for approval as its own question.
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.25.1 onboard checkpoint --phase awaiting-plan-approval
+npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-plan-approval
 ```
 
 Ask the developer before you edit a file that has uncommitted changes. List those files in
@@ -57,4 +57,4 @@ the plan under `Uncommitted files`, each with one sentence explaining why, or wr
 `git status` names them. The CLI records no consent: the approved plan is the record. The
 plan must not delete, move, or rename one of those files.
 
-Then run `npx --prefer-offline --yes copilotkit@4.25.1 onboard read feature/a2ui/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.26.0 onboard read feature/a2ui/implement`.