copilotkit 4.26.0 → 4.27.0

package/onboarding/prompts/framework/pydantic-ai.md

@@ -1,9 +1,24 @@
 # Configure Pydantic AI
 
+First run `npx --prefer-offline --yes copilotkit@4.27.0 onboard setup-answers`. Its `vendor` is the
+vendor the framework step recorded, even after this conversation lost it, with
+`vendor.baseUrl` and `vendor.modelId` for an OpenAI-compatible provider.
+
 Preserve an existing Pydantic AI model setup. For a new agent, use the vendor that the
-framework step recorded. If it recorded none, use OpenAI. Offer another vendor only after
-an exact CopilotKit Markdown page names it. The page must name its credential variables
-and setup steps.
+framework step recorded. Use OpenAI only when the record and this conversation have no
+vendor. This release offers a new agent on this framework OpenAI or an OpenAI-compatible
+provider only. For a new agent, if the developer names Anthropic or Google, say that this
+release supports OpenAI or an OpenAI-compatible provider on this framework, that Anthropic
+and Google come in a later release, and offer the built-in CopilotKit agent if they need
+Anthropic or Google now. An existing agent keeps its vendor and model. If it runs on
+Anthropic or Google, add one line to the plan: the page context that CopilotKit sends can
+fail with that vendor until a CopilotKit SDK release fixes it (PE-728). Take that vendor's
+package, class, and credential variable names from the framework's own documentation, and
+use a model id that the vendor serves to a new key today. For an OpenAI-compatible
+provider, keep `OPENAI_API_KEY`, use the model id that `setup/questions` recorded, and
+write the base URL that `setup/questions` recorded as `OPENAI_BASE_URL` in the app's env
+file. The key can stay in its own file. Where the framework does not read that variable,
+also pass it in code. Take every CopilotKit step from the pages below.
 
 Name the default model credential `OPENAI_API_KEY`.
 
@@ -44,7 +59,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, and the two-step context route.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/strands-python.md

@@ -1,12 +1,26 @@
 # Configure Strands Agents Python
 
-Preserve an existing Strands model setup. For a new agent, use the vendor that the
-framework step recorded. If it recorded none, use OpenAI. Offer another vendor only after
-an exact CopilotKit Markdown page names it. The page must name its credential variables
-and setup steps.
+First run `npx --prefer-offline --yes copilotkit@4.27.0 onboard setup-answers`. Its `vendor` is the
+vendor the framework step recorded, even after this conversation lost it, with
+`vendor.baseUrl` and `vendor.modelId` for an OpenAI-compatible provider.
 
-Name the default model credential `OPENAI_API_KEY`. For Anthropic, follow the
-quickstart's "Using Anthropic instead" steps, and name the credential `ANTHROPIC_API_KEY`.
+Preserve an existing Strands model setup. For a new agent, use the vendor that the
+framework step recorded. Use OpenAI only when the record and this conversation have no
+vendor. This release offers a new agent on this framework OpenAI or an OpenAI-compatible
+provider only. For a new agent, if the developer names Anthropic or Google, say that this
+release supports OpenAI or an OpenAI-compatible provider on this framework, that Anthropic
+and Google come in a later release, and offer the built-in CopilotKit agent if they need
+Anthropic or Google now. An existing agent keeps its vendor and model. If it runs on
+Anthropic or Google, add one line to the plan: the page context that CopilotKit sends can
+fail with that vendor until a CopilotKit SDK release fixes it (PE-728). Take that vendor's
+package, class, and credential variable names from the framework's own documentation, and
+use a model id that the vendor serves to a new key today. For an OpenAI-compatible
+provider, keep `OPENAI_API_KEY`, use the model id that `setup/questions` recorded, and
+write the base URL that `setup/questions` recorded as `OPENAI_BASE_URL` in the app's env
+file. The key can stay in its own file. Where the framework does not read that variable,
+also pass it in code. Take every CopilotKit step from the pages below.
+
+Name the default model credential `OPENAI_API_KEY`.
 The dynamic A2UI tool still calls OpenAI, so a developer who later adds A2UI also needs
 `OPENAI_API_KEY`.
 
@@ -23,17 +37,18 @@ A2UI is not on this path. If the developer asks for it, say first that the fixed
 A2UI tool makes its own OpenAI call, so it bills a second model call this plan does not
 account for.
 
-No Strands agent-app-context Markdown page is available. Do not invent an
-agent-app-context setup. If the requested work passes project data to the agent, run the unsupported
-route below. Otherwise, record the gap and continue.
+The agent receives `useAgentContext` entries on the AG-UI run input, in its `context`
+field, as https://docs.copilotkit.ai/agent-app-context.md shows. If the requested work
+passes project data to the agent, read `context` in the agent with this framework's own
+API, and pass it to the model. Name that code in the plan.
 
 Connect the Copilot Runtime with `HttpAgent` from `@ag-ui/client`.
 
 Record the selected framework, vendor, model, required credential variable names, these
-URLs, and the context documentation gap.
+URLs, and how the agent reads `context`.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/strands-typescript.md

@@ -1,12 +1,26 @@
 # Configure Strands Agents TypeScript
 
-Preserve an existing Strands model setup. For a new agent, use the vendor that the
-framework step recorded. If it recorded none, use OpenAI. Offer another vendor only after
-an exact CopilotKit Markdown page names it. The page must name its credential variables
-and setup steps.
+First run `npx --prefer-offline --yes copilotkit@4.27.0 onboard setup-answers`. Its `vendor` is the
+vendor the framework step recorded, even after this conversation lost it, with
+`vendor.baseUrl` and `vendor.modelId` for an OpenAI-compatible provider.
 
-Name the default model credential `OPENAI_API_KEY`. For Anthropic, follow the
-quickstart's "Using Anthropic instead" steps, and name the credential `ANTHROPIC_API_KEY`.
+Preserve an existing Strands model setup. For a new agent, use the vendor that the
+framework step recorded. Use OpenAI only when the record and this conversation have no
+vendor. This release offers a new agent on this framework OpenAI or an OpenAI-compatible
+provider only. For a new agent, if the developer names Anthropic or Google, say that this
+release supports OpenAI or an OpenAI-compatible provider on this framework, that Anthropic
+and Google come in a later release, and offer the built-in CopilotKit agent if they need
+Anthropic or Google now. An existing agent keeps its vendor and model. If it runs on
+Anthropic or Google, add one line to the plan: the page context that CopilotKit sends can
+fail with that vendor until a CopilotKit SDK release fixes it (PE-728). Take that vendor's
+package, class, and credential variable names from the framework's own documentation, and
+use a model id that the vendor serves to a new key today. For an OpenAI-compatible
+provider, keep `OPENAI_API_KEY`, use the model id that `setup/questions` recorded, and
+write the base URL that `setup/questions` recorded as `OPENAI_BASE_URL` in the app's env
+file. The key can stay in its own file. Where the framework does not read that variable,
+also pass it in code. Take every CopilotKit step from the pages below.
+
+Name the default model credential `OPENAI_API_KEY`.
 The dynamic A2UI tool still calls OpenAI, so a developer who later adds A2UI also needs
 `OPENAI_API_KEY`.
 
@@ -21,9 +35,10 @@ The documentation scope is `strands-typescript`. Use only the TypeScript example
 these pages. Install `@modelcontextprotocol/sdk` as a runtime dependency.
 `@strands-agents/sdk` loads it even when the application does not use MCP.
 
-No Strands TypeScript agent-app-context Markdown page is available. Do not translate
-another language's backend example or invent that setup. If the requested work passes project data
-to the agent, run the unsupported route below. Otherwise, record the gap and continue.
+The agent receives `useAgentContext` entries on the AG-UI run input, in its `context`
+field, as https://docs.copilotkit.ai/agent-app-context.md shows. If the requested work
+passes project data to the agent, read `context` in the agent with this framework's own
+API, and pass it to the model. Name that code in the plan.
 
 A2UI is not on this path. If the developer asks for it, say first that its page has no
 Strands TypeScript backend example, so a TypeScript project has nothing to follow.
@@ -31,10 +46,10 @@ Strands TypeScript backend example, so a TypeScript project has nothing to follo
 Connect the Copilot Runtime with `HttpAgent` from `@ag-ui/client`.
 
 Record the selected framework, vendor, model, required credential variable names, these
-URLs, and the context documentation gap.
+URLs, and how the agent reads `context`.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/angular.md

@@ -6,13 +6,13 @@ This step asks the developer nothing. If the run must wait for the developer any
 the pause first:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.27.0 onboard checkpoint --phase awaiting-developer
 ```
 
 Use the starter shortcut only if all these facts are true: the target directory holds no
 project, its name is a valid `init` project name, and the selected framework is ADK.
 If all three facts are true, record Angular as the selected frontend. Then run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read starter/clone` before you fetch documentation.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read starter/clone` before you fetch documentation.
 
 ## Documentation
 
@@ -59,7 +59,7 @@ you create or build an Angular project. If the installed version is lower, selec
 supported version first and use it for every later command in this project.
 
 If the pages support the selection, record Angular and these URLs. Then run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read credentials/finalize-plan`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, or the two version lines do not fit
-together, run `npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+together, run `npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/nextjs.md

@@ -6,7 +6,7 @@ This step asks the developer nothing. If the run must wait for the developer any
 the pause first:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.27.0 onboard checkpoint --phase awaiting-developer
 ```
 
 Use the starter shortcut only if the target directory holds no project and its name is
@@ -22,7 +22,7 @@ These TypeScript options have starters: Claude Agent SDK TypeScript, LangGraph T
 Mastra, and Strands Agents TypeScript. The .NET option is Microsoft Agent Framework .NET.
 
 If all shortcut conditions are true, record Next.js as the selected frontend. Then run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read starter/clone` before you fetch documentation.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read starter/clone` before you fetch documentation.
 
 ## Documentation
 
@@ -73,7 +73,7 @@ also sets `outputFileTracingRoot`. Do not set `outputFileTracingRoot` to a
 different folder. For an existing frontend, name this change in the report.
 
 If the page supports the selection, record Next.js and this URL. Then run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read credentials/finalize-plan`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/plan.md

@@ -8,37 +8,45 @@ If the copied prompt came from a Slack or Teams docs page, use that page as the
 Either one is final here. Do not ask the frontend question on that run. Do not let an
 existing frontend take a web route instead: the project keeps the frontend it has, and the
 Channel is what this run adds. Take the Slack or Microsoft Teams route below and name the
-provider to it. A Slack page names Slack. A Teams page names Teams.
+provider to it. A Slack page names Slack. A Teams page names Teams. Tell the developer in
+one sentence that the CopilotKit runtime runs in a long-running Channel host.
 
 Every rule below is for a run that named neither.
 
 ## Use the recorded frontend
 
-Use the frontend that `setup/questions` recorded. If the project has a frontend, preserve it
-and use the matching route below. Do not change application code in this phase. If neither
-settles it, ask one question that lists the recommendation and the valid choices: React
-SPA, Next.js, Angular, Vue 3, React Native, Slack, and Microsoft Teams.
+Run `npx --prefer-offline --yes copilotkit@4.27.0 onboard setup-answers` and use its `frontend`. It holds
+the answer that `setup/questions` recorded, even after this conversation lost it. If the
+project has a frontend, preserve it and use the matching route below. Do not change
+application code in this phase. If neither settles it, ask one line as the setup message
+does: the recommendation first, in bold, and the alternatives on one `Other:` line, from
+React SPA, Next.js, Angular, Vue 3, React Native, Slack, and Microsoft Teams. Record the answer with
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard setup-answers --frontend <name>`.
 
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.27.0 onboard checkpoint --phase awaiting-developer
 ```
 
+When the recorded frontend is not Next.js, tell the developer in one sentence where it runs
+the CopilotKit runtime. Angular runs it in its SSR server. React SPA, Vue 3 and React
+Native run it in a separate process. Next.js runs it in a route handler, so say nothing for it.
+
 Route names are this graph's own bookkeeping. Say what the run is doing in the developer's
 words instead.
 
 Use exactly one matching internal route:
 
-1. React SPA: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read frontend/react-spa`
-2. Next.js: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read frontend/nextjs`
-3. Angular: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read frontend/angular`
-4. Vue 3: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read frontend/vue`
-5. React Native: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read frontend/react-native`
-6. Slack or Microsoft Teams: `npx --prefer-offline --yes copilotkit@4.26.0 onboard read feature/channels/start`
+1. React SPA: `npx --prefer-offline --yes copilotkit@4.27.0 onboard read frontend/react-spa`
+2. Next.js: `npx --prefer-offline --yes copilotkit@4.27.0 onboard read frontend/nextjs`
+3. Angular: `npx --prefer-offline --yes copilotkit@4.27.0 onboard read frontend/angular`
+4. Vue 3: `npx --prefer-offline --yes copilotkit@4.27.0 onboard read frontend/vue`
+5. React Native: `npx --prefer-offline --yes copilotkit@4.27.0 onboard read frontend/react-native`
+6. Slack or Microsoft Teams: `npx --prefer-offline --yes copilotkit@4.27.0 onboard read feature/channels/start`
 
 If they chose Slack or Microsoft Teams, tell that node which one they chose so it
 does not ask again.
 
 If no listed frontend fits, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/react-native.md

@@ -6,7 +6,7 @@ This step asks the developer nothing. If the run must wait for the developer any
 the pause first:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.27.0 onboard checkpoint --phase awaiting-developer
 ```
 
 React Native has no starter. For a target directory that holds no project, build the new
@@ -25,7 +25,7 @@ documents `useRenderTool`, which is React Native's own hook for drawing a tool t
 already has. That is a different job and needs a tool in the agent.
 
 If the pages support the selection, record React Native and these URLs. Then run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read credentials/finalize-plan`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/react-spa.md

@@ -6,7 +6,7 @@ This step asks the developer nothing. If the run must wait for the developer any
 the pause first:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.27.0 onboard checkpoint --phase awaiting-developer
 ```
 
 React SPA has no starter. For a target directory that holds no project, build the new
@@ -26,7 +26,7 @@ that import when Vite leaves the package external.
 - https://docs.copilotkit.ai/react-spa.md
 
 If the page supports the selection, record React SPA and this URL. Then run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read credentials/finalize-plan`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/vue.md

@@ -6,7 +6,7 @@ This step asks the developer nothing. If the run must wait for the developer any
 the pause first:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.27.0 onboard checkpoint --phase awaiting-developer
 ```
 
 Vue 3 has no starter. For a target directory that holds no project, build the new
@@ -26,7 +26,7 @@ page above. Vue has its own `useComponent`, which is not the React package. Take
 that reference page rather than from a Vue generative-UI guide, which is not published.
 
 If the pages support the selection, record Vue 3 and these URLs. Then run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read credentials/finalize-plan`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/implementation/build-and-validate.md

@@ -7,13 +7,13 @@ Do not implement the plan yourself. Use the step order in the approved plan.
 Two rules below stop onboarding. A Learning Container create that fails for a reason other
 than the container already existing stops it. An implementation subagent that still reports
 a missing Learning Container after the one restart stops it too. Each ends a run the
-developer has already approved a plan for. Name the exact
+developer has already seen a plan for. Name the exact
 command, id, and error code that stopped you: a report that names only the step cannot be
 acted on. Send one short report before you stop. The friction command follows the telemetry
 setting the developer already chose, so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.27.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -26,11 +26,15 @@ carries any of those, prints the reason, and exits zero. A refused report is not
 step. Send the report, then stop. Reporting is not a route change and does not resume the
 run.
 
+If the developer replies **stop** while this phase runs, follow the section with that
+name in the plan prompt, `credentials/write-plan`.
+
 ## Departing from the approved plan
 
-The developer approved a written plan and was told that approval was the last question this
-run asked them. A step that cannot be built as written is therefore a change to the
-only thing they agreed to.
+The developer saw a written plan and answered any risky change in it. The approved plan is
+that plan, with their answer. They were told that no question comes after it unless a step
+cannot be built as written. Such a step is therefore a change to the only thing they agreed
+to.
 
 Where you depart from a path, a version, or a step the plan named, record it: what the
 plan said, what you did instead, and why. Carry that record into the closing summary,
@@ -53,7 +57,7 @@ This prompt pauses for the developer in several places. Before you end your turn
 for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.27.0 onboard checkpoint --phase awaiting-developer
 ```
 
 The existing agent's behavior is never a departure to record and carry on from. It is four
@@ -70,14 +74,15 @@ declines, use the route-out rules below.
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.27.0 onboard checkpoint --phase awaiting-developer
 ```
 
 ## The developer's uncommitted files
 
 `onboard start` backed up the developer's work, so nothing is recorded before an edit. The
-approved plan lists the files that had uncommitted changes under `Uncommitted files`, and
-approving the plan is the developer agreeing to those edits. Any other such file is a file
+approved plan lists the files that had uncommitted changes under `Uncommitted files`. Each
+one is a risky change, so the developer's answer to the plan is their agreement to those
+edits. Any other such file is a file
 the plan does not name: ask the developer, as above.
 
 Never repair, reset, or revert a file the developer changed outside this run. Do not delete,
@@ -92,12 +97,12 @@ or from an environment variable.
 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.26.0 onboard tripwire --continue`. Then read the step again. If
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard tripwire --continue`. Then read the step again. If
 you cannot ask, use the route-out rules below. Before you end your turn to wait for the
 developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.27.0 onboard checkpoint --phase awaiting-developer
 ```
 
 ## Implement the plan
@@ -107,11 +112,11 @@ subagent, because the subagent writes a selector that names it. A selector that
 container the platform does not hold fails thread initialization on every agent run. Where
 the plan names no container, skip this step.
 
-Run this from the target app directory. The developer approved the id with the plan, so this
-is the first point at which it can be created:
+Run this from the target app directory. The developer saw the id in the plan, so this is
+the first point at which it can be created:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 learning containers create --id <id> --name <name> --json
+npx --prefer-offline --yes copilotkit@4.27.0 learning containers create --id <id> --name <name> --json
 ```
 
 Pass the id the plan names. Take the name from the selected project's own display name, so
@@ -125,7 +130,7 @@ failure to repair and not a reason to pick a new id. Any other error code: repor
 stop onboarding, so no run wires a selector to an id the platform does not hold.
 
 Spawn one implementation subagent. Tell it to run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read subagent/implement-and-validate` first and
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read subagent/implement-and-validate` 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
@@ -133,8 +138,8 @@ handoff. Give it the plan, selected framework, frontend, model, exact target app
 selected documentation URLs, and the
 documentation policy recorded during framework selection or conversion planning. On a
 conversion, also give it the frozen criterion. Give it the paths that had uncommitted
-changes when the run started. Give it the developer's answer on the Skills install, so that it runs an
-approved install and skips a declined one. Require it to implement every step in plan order
+changes when the run started. Give it the developer's answer on the Skills install, so that it skips a
+declined install. Require it to implement every step in plan order
 and run the full validation list. Wait for it.
 
 One subagent implements the whole plan. Do not divide the work across concurrent subagents,
@@ -160,7 +165,7 @@ Report it and take the failure ending.
 If the implementation result does not start with `Status: passed`, do not continue to proof.
 
 Then run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read proof/round-trip`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read proof/round-trip`.
 
 ## Repair rules
 
@@ -188,9 +193,9 @@ developer
 declined a file the plan does not name, or the run cannot ask them about it. A defect in a
 package this run installed is not a stack CopilotKit does not serve, and a command this run
 cannot get to pass is not one either. In those cases run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read stopped/run-failed`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read stopped/run-failed`.
 
 A plan with no path to follow takes the unsupported ending: the fix requires changing the
 developer's existing agent or frontend, or the documentation does not support the plan. In
 those cases run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/proof/complete.md

@@ -24,7 +24,7 @@ friction commands follow the telemetry setting the developer already chose, so t
 separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard friction --category <slug> --cost-seconds <seconds> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.27.0 onboard friction --category <slug> --cost-seconds <seconds> --message "<sentences>"
 ```
 
 Put one or two sentences in `--message`. Pick one category from docs-missing, docs-wrong,
@@ -46,7 +46,7 @@ Pass the surface-check outcome the proof subagent returned, not the one you want
 web frontend, pass `--visual-check` and the URL the browser opened, unchanged:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard complete --visual-check <outcome> \
+npx --prefer-offline --yes copilotkit@4.27.0 onboard complete --visual-check <outcome> \
   --frontend-url <the url you opened>
 ```
 
@@ -74,7 +74,7 @@ this graph opens.
 nothing drove the frontend:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard complete --visual-check failed --blocked-by browser-control-unresponsive
+npx --prefer-offline --yes copilotkit@4.27.0 onboard complete --visual-check failed --blocked-by browser-control-unresponsive
 ```
 
 ## Write the handoff
@@ -89,16 +89,19 @@ command prints them. Do not add a separate line, heading, or opening sentence ab
 missing browser.
 
 Paste the **Handoff facts** block the command printed, as it is. The command also prints
-`## The developer's files`: relay that report as printed, with its restore command. The
-dashboard line there only tells the developer where the
+`## The developer's files`: relay that report as printed, with its restore command. When
+the report says the run started in an empty folder, relay that one line alone: list no
+files and offer no restore. The dashboard line there only tells the developer where the
 dashboard is. Do not open it. Nothing in this graph gates on the dashboard. Then add what
 only you can say:
 
 - What the project now does, and the first thing to try in it.
 - What changed since the developer approved the plan: every path, version, or step the run
   departed from, and why. Where nothing departed, say so in one line. A file the approved
-  plan named under `Files the run writes itself` is not a departure, and neither is a
-  Skills install the developer declined.
+  plan named under `Files the run writes itself` or `Skills install` is not a departure, and
+  neither is a Skills install the developer declined.
+- Where this run installed the CopilotKit Skills, the Skills files the install added:
+  `.agents/skills/` and its links in `.claude/skills/`. Say that deleting both removes them.
 - Every change to the existing agent's behavior: its instructions, its tools, its model or
   provider, or its memory. Name each one and its file, and say the developer approved it.
   Where none changed, write `none`.

package/onboarding/prompts/proof/oss-baseline.md

@@ -1,7 +1,7 @@
 # Prove the existing OSS baseline
 
 Do not prove the baseline yourself. Spawn one proof subagent. Tell it to run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read subagent/prove-oss-baseline` first and follow
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read subagent/prove-oss-baseline` 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
@@ -18,7 +18,7 @@ Wait for the subagent to finish.
 Record what that proof returned before you route on it:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
+npx --prefer-offline --yes copilotkit@4.27.0 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
 ```
 
 Report the gate whatever it returned. Use the list below. A proof that never ran is `skipped`, not failed. The command prints one line and sends
@@ -40,7 +40,7 @@ Do not change project files before this proof ends. Starting existing developmen
 processes and their ignored runtime files is allowed.
 
 If the subagent proves the `both-oss` predicate, keep its evidence with the plan and run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read conversion/plan`. That project already works.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read conversion/plan`. That project already works.
 What it needs is the conversion, not a build.
 
 A failed baseline does not end the run, and this step does not repair it. Decide which
@@ -55,12 +55,12 @@ pass. This proof only reads.
 A failed baseline whose cause is in the project is the starting state of this project. So
 is an operational failure still there after the third attempt. Record the starting state
 `both-copilotkit-unproved` and run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read credentials/plan`. This prompt is served
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read credentials/plan`. This prompt is served
 whenever a project looks like an OSS integration, so a baseline that did not prove is an
 ordinary starting state rather than a failure. The build that follows fixes the
 integration, and `proof/round-trip` proves the result, with its own bounded repair cycle.
 Keep the failing predicate and the check the subagent named with the plan, and tell the
-developer that the existing integration did not prove before you ask for plan approval.
+developer that the existing integration did not prove when you show the plan.
 
 Do not record a state that says the CopilotKit integration is absent. This prompt is
 reached only when the merged findings prove that the integration is there, so `both` is
@@ -75,5 +75,5 @@ operational. Run the proof again, three times in total, then record the starting
 above and go on. Both causes lead to the same plan.
 
 If the proof cannot identify the running process safely, or it exposes a secret, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read stopped/run-failed`. Neither means the
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read stopped/run-failed`. Neither means the
 project is unsupported: each means this run did not establish what it needed to.