copilotkit 4.9.0 → 4.9.2

package/onboarding/index.json

@@ -203,6 +203,7 @@
     },
     {
       "edges": [
+        "starter/clone",
         "credentials/finalize-plan",
         "unsupported/no-validated-path"
       ],
@@ -211,6 +212,7 @@
     },
     {
       "edges": [
+        "starter/clone",
         "credentials/finalize-plan",
         "unsupported/no-validated-path"
       ],
@@ -282,6 +284,14 @@
       "milestone": "proof",
       "name": "proof/round-trip"
     },
+    {
+      "edges": [
+        "proof/round-trip",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "starter",
+      "name": "starter/clone"
+    },
     {
       "edges": [],
       "milestone": "subagent",

package/onboarding/prompts/authenticate/start.md

@@ -14,24 +14,38 @@ question from the documentation this graph gives you. Another checkout on this m
 not a source. The developer running this has none, so an answer taken from one is an
 answer they cannot get, and it hides the documentation gap that blocks them.
 
-Tell the developer that onboarding can send feedback outside this machine. Explain that
-the reports contain short descriptions of CLI or documentation problems. Ask whether the
-developer permits these reports before project work starts. Record the answer. Do not send
-feedback unless the developer permits it.
+Before you run a command or spawn a subagent, send this exact message:
 
-Run `npx --yes copilotkit@4.9.0 login --json` before any project work. This command checks the
-current session. It starts sign-in only as needed.
+Welcome to CopilotKit. I will check sign-in, inspect your project, recommend a setup, and
+show you a plan before I change files. After you approve the plan, I will build the
+integration, prove the full round trip, and leave the app running with its URLs.
 
-Read its JSON Lines output in order:
+Do not ask for separate feedback consent. The feedback commands enforce the developer's
+CLI telemetry setting when a later step tries to send a report.
 
-1. If it emits `authentication_url`, show only that URL to the developer.
+Run `npx --yes copilotkit@4.9.2 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.
+
+Read each JSON Lines record as the running command writes it:
+
+1. If the process emits `authentication_url`, show the `authentication_url` to the
+   developer as soon as that line arrives. The process is still running.
 2. Tell the developer to open the URL and finish sign-in.
-3. Wait for the command to emit `type: completed`.
-4. If it emits `type: failed`, report the error and stop onboarding.
+3. Keep monitoring the same process after you show the URL. Do not start a second login
+   command.
+4. Continue onboarding only after that same process emits `type: completed`.
+5. If that process emits `type: failed`, report the error and stop onboarding.
 
 Do not use `whoami` for this check. It has no JSON output and some failures exit with code
 zero. Do not put account tokens or credentials in the conversation.
 
+Before you ask the developer any setup question, finish every read-only investigation and
+preflight check in this section. Record whether your coding-agent environment has browser
+or device control. Use the control that matches the selected surface later. Do not install
+a browser or device tool during this preflight. Do not ask the developer about this tool
+limit.
+
 Spawn one research subagent. Give it the full text of the research brief at the end of this
 prompt and tell it to follow that brief and return only its findings. Add these tasks:
 
@@ -39,6 +53,7 @@ prompt and tell it to follow that brief and return only its findings. Add these
 - Check whether `.copilotkit/project.json` has `projectId`, `projectSlug`, and `clerkOrgId`.
 - Check whether `.env` has a non-empty `INTELLIGENCE_API_KEY` entry.
 - Record the `.env` file modification time without returning it.
+- Report whether the target project directory contains any entries.
 - Report whether an agent, frontend, and CopilotKit integration are present.
 - Report whether the runtime constructor uses a `runner` option, an `intelligence`
   option, or neither can be proved from project files.
@@ -46,9 +61,10 @@ prompt and tell it to follow that brief and return only its findings. Add these
 Do not print either file or any secret value. Return only paths, presence checks, and missing
 field names. Wait for the subagent to finish.
 
-If the findings show an empty project and do not prove its purpose, ask what the developer
-wants to build before you select a framework. Ask this question immediately. Record the
-answer and give it to each later subagent.
+If the findings show an empty project and do not prove its purpose, ask one guided question
+about the user outcome. This asks what the developer wants to build before you select a
+framework. Give two or three short examples and offer a minimal starter. Record the answer
+and give it to each later subagent.
 
 If a repository file exists, each finding must cite it. For an empty project, the subagent
 must cite its directory check and report absent parts.
@@ -60,13 +76,13 @@ that the repository answers.
 Do not infer a working OSS path from packages, imports, project files, or keys. If an
 agent, frontend, and CopilotKit integration are present, prove the live starting state
 before any project file changes. Run
-`npx --yes copilotkit@4.9.0 onboard read proof/oss-baseline`.
+`npx --yes copilotkit@4.9.2 onboard read proof/oss-baseline`.
 
 For every other inspected state, run
-`npx --yes copilotkit@4.9.0 onboard read credentials/plan`.
+`npx --yes copilotkit@4.9.2 onboard read credentials/plan`.
 
 If authentication or inspection stops onboarding, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.
 
 ## Research subagent brief
 
@@ -84,6 +100,15 @@ Inspect the repository without changing it. Find evidence for:
 - current CopilotKit packages and configuration
 - authentication boundaries
 - names of required credential variables, without reading their values
+- package manager and lockfile
+- required toolchains and their installed versions
+- declared ports and whether each port is available
+- CopilotKit package versions and package compatibility risks
+
+For the CopilotKit versions, report the exact installed version of every `@copilotkit/*`
+dependency, read from the lockfile rather than a manifest range, and state whether any of
+them is below 1.64.0. The conversion decides its upgrade from exactly that, and a caret
+range does not answer it.
 
 A project states what it is for in its `README.md`, in its package description, or in
 the prompt of an agent it already has. Quote that statement rather than rewriting it. An
@@ -92,7 +117,8 @@ evidence. State the purpose as unproved when the project never says.
 
 Gather what you need in as few commands as possible. Combine independent reads into one
 command rather than running them one at a time. Split a command only when its result decides
-what you run next.
+what you run next. Keep this preflight read-only. Do not install packages, stop processes,
+or change a port. Check only the toolchains and ports that repository files require.
 
 Return the file paths and a short finding for each item. State each absent or unproved item.
 Do not read, print, or return secret values. Do not read a file outside the project

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

@@ -5,6 +5,31 @@ repository findings. Ask the developer only for choices that the repository does
 show. Do not change application code in this phase. Do not read, show, store, or request
 a secret value.
 
+Use a gentle wizard. Ask one short question at a time. Do not combine separate choices in
+one question. Put the recommendation first, give its evidence in one sentence, and keep
+the alternatives short. When project selection is unknown, ask only which Intelligence
+project to use. Keep final plan approval as its own later question.
+
+## Record the audit cell
+
+Use the repository findings and selected choices to record the path before project work
+starts. Choose one starting state: empty, agent-only, frontend-only, both, both-oss.
+
+- `empty`: no agent and no frontend.
+- `agent-only`: an agent and no frontend.
+- `frontend-only`: a frontend and no agent.
+- `both`: an agent and frontend that do not have a proved CopilotKit round trip.
+- `both-oss`: an agent and frontend with the proved OSS CopilotKit baseline.
+
+Run this command with the exact selected slugs:
+
+```text
+npx --yes copilotkit@4.9.2 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
+prompts gave, then run the command again.
+
 ## Select the Intelligence project
 
 Use the target app or runtime directory from the repository findings. If a nested app owns
@@ -23,7 +48,7 @@ target directory. Do not send the developer to another terminal.
 Read the choices first:
 
 ```text
-npx --yes copilotkit@4.9.0 project list --json
+npx --yes copilotkit@4.9.2 project list --json
 ```
 
 With `--json` the payload is the only thing on standard output, so it is safe to parse.
@@ -34,17 +59,17 @@ developer asks.
 If the developer searches, run:
 
 ```text
-npx --yes copilotkit@4.9.0 project list --search <query> --json
+npx --yes copilotkit@4.9.2 project list --search <query> --json
 ```
 
 If the developer asks for all projects, show the result of the first list command. Ask
-which project to use, or ask for a new project name. Ask this with the frontend and model
-choices when those choices remain unknown.
+which project to use, or ask for a new project name. Do not combine this question with a
+frontend, framework, model, credential, or plan-approval question.
 
 Then record their answer, from the target directory:
 
 ```text
-npx --yes copilotkit@4.9.0 project select --project <slug-or-id> --json
+npx --yes copilotkit@4.9.2 project select --project <slug-or-id> --json
 ```
 
 Use `--create <name> --json` instead when they want a new project. The two flags cannot be
@@ -110,16 +135,21 @@ names, and selected documentation URLs. Wait for the subagent to finish.
 
 Make sure that the plan preserves each part that already exists. The plan must name the
 credential variables, the Intelligence runtime wiring, the application the project asks
-for, implementation steps, validation steps, and proof steps. It must not contain secret
-values.
+for, implementation steps, validation steps, and proof steps. Where the plan upgrades the
+CopilotKit dependencies, it must name the versions it moves and the revert it falls back
+to. It must not contain secret values.
+
+Show only the selected framework, frontend, model, planned file changes, the CopilotKit dependency upgrade and the versions it moves, validation commands, and proof steps.
 
-Show only the selected framework, frontend, model, planned file changes, validation commands, and proof steps.
+An upgrade to a working install is the developer's call, so it belongs in the plan they
+approve rather than in the implementation that follows. Do not upgrade a dependency the
+developer did not approve.
 
 If the developer approves the plan, run
-`npx --yes copilotkit@4.9.0 onboard read implementation/build-and-validate`.
+`npx --yes copilotkit@4.9.2 onboard read implementation/build-and-validate`.
 
 If no exact supported path or documentation URL exists, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.
 
 ## Planning subagent brief
 
@@ -160,10 +190,28 @@ combined. Take the constructor from the connect-your-runtime page. Where a frame
 quickstart shows a `runner` option instead, the connect-your-runtime page wins.
 
 When the starting state is `both-oss`, use its recorded live baseline evidence. Preserve
-the working agent, frontend, CopilotKit integration, and OSS behavior. Plan only the
-project selection, Intelligence runtime configuration, and authenticated proof needed for
-the conversion. Preserve the existing persistence and user-visible request. Do not
-rebuild a path that already works.
+the working agent, frontend, CopilotKit integration, and OSS behavior. Plan the project
+selection, the CopilotKit dependency upgrade below, the Intelligence runtime
+configuration, and the authenticated proof needed for the conversion. Preserve the
+existing persistence and user-visible request. Do not rebuild a path that already works.
+
+Preserving the OSS baseline preserves the application, not its CopilotKit dependency
+versions. An install that predates the managed platform defaults carries a bundled
+reference naming hosts that route nothing, and it requires the platform URLs the same
+documentation calls optional. A run that reads that reference configures the runtime
+against a dead host, and the failure arrives as an empty-body 404 with no cause named.
+
+If any `@copilotkit/*` dependency is below 1.64.0, plan to upgrade every `@copilotkit/*`
+dependency to its latest published version. Packages that share a version line must end
+on the same version. Never force a package onto a version line it does not publish on.
+Resolve each latest version at run time rather than from a remembered version number.
+Where every `@copilotkit/*` dependency already meets that floor, plan no dependency
+change.
+
+Plan the upgrade as its own step before the Intelligence runtime wiring, and plan to
+re-run the recorded baseline checks immediately after it. Name the revert: restore the
+manifest and lockfile to their recorded state and stop, rather than wiring Intelligence
+onto a baseline the upgrade broke.
 
 Where the SDK requires an application-level value that the repository cannot supply, such
 as an end-user identity for threads, use one clearly marked local placeholder and name what

package/onboarding/prompts/credentials/plan.md

@@ -4,6 +4,12 @@ Use the repository findings to select the agent framework. Ask the developer onl
 choices that the repository does not show. Do not change application code in this phase.
 Do not read, show, store, or request a secret value.
 
+Use a gentle wizard. Ask one short question at a time. Do not combine separate choices in
+one question. Put the recommendation first, give its evidence in one sentence, and keep
+the alternatives short. When the framework is unknown, ask only whether to use the
+recommended framework. If the developer declines it, ask one follow-up question that lists
+the valid framework choices. Do not ask about the frontend, model, or project in this step.
+
 These are the agent frameworks and their default vendors:
 
 | Framework                          | Default vendor  |
@@ -45,26 +51,26 @@ another framework. Do not show the internal route.
 
 Use exactly one matching internal route:
 
-1. AG2: `npx --yes copilotkit@4.9.0 onboard read framework/ag2`
-2. Agno: `npx --yes copilotkit@4.9.0 onboard read framework/agno`
-3. Built-in CopilotKit agent: `npx --yes copilotkit@4.9.0 onboard read framework/built-in`
-4. Claude Agent SDK Python: `npx --yes copilotkit@4.9.0 onboard read framework/claude-sdk-python`
-5. Claude Agent SDK TypeScript: `npx --yes copilotkit@4.9.0 onboard read framework/claude-sdk-typescript`
-6. CrewAI Flows: `npx --yes copilotkit@4.9.0 onboard read framework/crewai-flows`
-7. Deep Agents: `npx --yes copilotkit@4.9.0 onboard read framework/deep-agents`
-8. LangGraph Python: `npx --yes copilotkit@4.9.0 onboard read framework/langgraph-python`
-9. LangGraph FastAPI: `npx --yes copilotkit@4.9.0 onboard read framework/langgraph-fastapi`
-10. LangGraph TypeScript: `npx --yes copilotkit@4.9.0 onboard read framework/langgraph-typescript`
-11. LlamaIndex: `npx --yes copilotkit@4.9.0 onboard read framework/llamaindex`
-12. ADK: `npx --yes copilotkit@4.9.0 onboard read framework/google-adk`
-13. Microsoft Agent Framework Python: `npx --yes copilotkit@4.9.0 onboard read framework/ms-agent-python`
-14. Microsoft Agent Framework .NET: `npx --yes copilotkit@4.9.0 onboard read framework/ms-agent-dotnet`
-15. Mastra: `npx --yes copilotkit@4.9.0 onboard read framework/mastra`
-16. MS Agent Harness .NET: `npx --yes copilotkit@4.9.0 onboard read framework/ms-agent-harness-dotnet`
-17. Pydantic AI: `npx --yes copilotkit@4.9.0 onboard read framework/pydantic-ai`
-18. Strands Agents Python: `npx --yes copilotkit@4.9.0 onboard read framework/strands-python`
-19. Strands Agents TypeScript: `npx --yes copilotkit@4.9.0 onboard read framework/strands-typescript`
+1. AG2: `npx --yes copilotkit@4.9.2 onboard read framework/ag2`
+2. Agno: `npx --yes copilotkit@4.9.2 onboard read framework/agno`
+3. Built-in CopilotKit agent: `npx --yes copilotkit@4.9.2 onboard read framework/built-in`
+4. Claude Agent SDK Python: `npx --yes copilotkit@4.9.2 onboard read framework/claude-sdk-python`
+5. Claude Agent SDK TypeScript: `npx --yes copilotkit@4.9.2 onboard read framework/claude-sdk-typescript`
+6. CrewAI Flows: `npx --yes copilotkit@4.9.2 onboard read framework/crewai-flows`
+7. Deep Agents: `npx --yes copilotkit@4.9.2 onboard read framework/deep-agents`
+8. LangGraph Python: `npx --yes copilotkit@4.9.2 onboard read framework/langgraph-python`
+9. LangGraph FastAPI: `npx --yes copilotkit@4.9.2 onboard read framework/langgraph-fastapi`
+10. LangGraph TypeScript: `npx --yes copilotkit@4.9.2 onboard read framework/langgraph-typescript`
+11. LlamaIndex: `npx --yes copilotkit@4.9.2 onboard read framework/llamaindex`
+12. ADK: `npx --yes copilotkit@4.9.2 onboard read framework/google-adk`
+13. Microsoft Agent Framework Python: `npx --yes copilotkit@4.9.2 onboard read framework/ms-agent-python`
+14. Microsoft Agent Framework .NET: `npx --yes copilotkit@4.9.2 onboard read framework/ms-agent-dotnet`
+15. Mastra: `npx --yes copilotkit@4.9.2 onboard read framework/mastra`
+16. MS Agent Harness .NET: `npx --yes copilotkit@4.9.2 onboard read framework/ms-agent-harness-dotnet`
+17. Pydantic AI: `npx --yes copilotkit@4.9.2 onboard read framework/pydantic-ai`
+18. Strands Agents Python: `npx --yes copilotkit@4.9.2 onboard read framework/strands-python`
+19. Strands Agents TypeScript: `npx --yes copilotkit@4.9.2 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.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

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

@@ -21,9 +21,16 @@ the application passes proof. Report each tool result separately.
 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.9.0 onboard complete`, carrying the
-visual-check result:
+When the proof is complete, run `npx --yes copilotkit@4.9.2 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.9.0 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.9.2 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.9.2 onboard complete --device-check <outcome>
 ```
+
+`--visual-check` is for a web frontend and takes `performed`, `skipped-no-browser-tool`, or
+`failed`. `--device-check` is for React Native and takes `performed`, `skipped-no-device`,
+or `failed`. Anything but `performed` ends this run as blocked, and the command's output
+names the evidence that is missing. Report it that way.

package/onboarding/prompts/framework/ag2.md

@@ -42,7 +42,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/agno.md

@@ -42,7 +42,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/built-in.md

@@ -37,7 +37,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/claude-sdk-python.md

@@ -43,7 +43,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/claude-sdk-typescript.md

@@ -47,7 +47,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/crewai-flows.md

@@ -50,7 +50,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/deep-agents.md

@@ -39,7 +39,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/google-adk.md

@@ -40,7 +40,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/langgraph-fastapi.md

@@ -36,7 +36,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

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

@@ -27,7 +27,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

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

@@ -27,7 +27,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/llamaindex.md

@@ -45,7 +45,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/mastra.md

@@ -57,7 +57,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/ms-agent-dotnet.md

@@ -65,7 +65,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/ms-agent-harness-dotnet.md

@@ -56,7 +56,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/ms-agent-python.md

@@ -40,7 +40,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

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

@@ -42,7 +42,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

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

@@ -36,7 +36,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

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

@@ -36,7 +36,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/angular.md

@@ -2,6 +2,11 @@
 
 Preserve an existing Angular frontend. Use the selected page for a new frontend.
 
+Use the starter shortcut only if all these facts are true: the target directory contains
+no entries, 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 --yes copilotkit@4.9.2 onboard read starter/clone` before you fetch documentation.
+
 ## Documentation
 
 - Credentials and plan: `Not applicable`
@@ -26,8 +31,8 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the page supports the selection, run
-`npx --yes copilotkit@4.9.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.2 onboard read credentials/finalize-plan`.
 
 If a second method also fails, or the page that loads does not support the selection,
 run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/nextjs.md

@@ -2,6 +2,21 @@
 
 Preserve an existing Next.js frontend. Use the selected pages for a new frontend.
 
+Use the starter shortcut only if the target directory contains no entries and its name is
+a valid `init` project name. The selected framework must also match one of these options.
+
+These Python options have Next.js starters: Agno, Claude Agent SDK Python, CrewAI Flows,
+LangGraph Python, LlamaIndex, and ADK.
+
+These Python options also have starters: Microsoft Agent Framework Python, Pydantic AI,
+and Strands Agents Python.
+
+These TypeScript options have starters: Claude Agent SDK TypeScript, LangGraph TypeScript,
+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 --yes copilotkit@4.9.2 onboard read starter/clone` before you fetch documentation.
+
 ## Documentation
 
 - Credentials and plan: `Not applicable`
@@ -22,7 +37,7 @@ not a fact about the page. Retrieve the same URL a second way before you judge i
 unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.2 onboard read credentials/finalize-plan`.
 
 If a second method also fails, or a page that loads does not support the selection, run
-`npx --yes copilotkit@4.9.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.