copilotkit 4.9.2 → 4.9.17

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

@@ -1,71 +1,40 @@
 # Configure Microsoft Agent Framework for .NET
 
-Preserve an existing Microsoft Agent Framework model setup. Start with GitHub Models for
-a new agent, which is what the starter configures. Offer another vendor only after an
-exact CopilotKit Markdown page names it. The page must name its credential variables and
-setup steps.
+Preserve an existing Microsoft Agent Framework model setup. Use direct OpenAI for a new
+agent. Name its credential `OPENAI_API_KEY`. Do not change an existing provider.
 
-This agent resolves its model credential in a fixed order: the `OPENAI_API_KEY`
-environment variable, then `OPENAI_API_KEY` in configuration, then a `GitHubToken` user
-secret. The environment variable wins.
+.NET configuration reads appsettings, environment variables, and user secrets. It does not
+read a `.env` file. If the project uses `.env`, application code must load it before the
+OpenAI client starts. Do not create a `.env` file without that loader.
 
-Neither this framework nor .NET configuration reads a `.env`. `builder.Configuration`
-sources appsettings, environment variables, and user secrets, and none of those is a
-dotenv file. A credential in `.env` works only if application code loads it into the
-environment before the chat client constructs: walk up from the working directory for a
-`.env` and set each name that is not already set. Otherwise pick a mechanism .NET reads
-on its own, an exported variable or a user secret. A scaffold that writes `.env`, reads
-`builder.Configuration["OPENAI_API_KEY"]`, and loads nothing falls silently to the
-`GitHubToken` branch.
+For a user secret, run `dotnet user-secrets set OPENAI_API_KEY` from the agent directory.
+The app must read the same name through .NET configuration. An exported environment
+variable with that name takes precedence over the user secret.
 
-Pick one and say which. For GitHub Models, set the user secret from the agent directory
-with `dotnet user-secrets set GitHubToken`. The agent reads it through
-`builder.Configuration["GitHubToken"]`, so the name in the store and the name in the
-code have to match exactly. For an OpenAI-compatible vendor, name `OPENAI_API_KEY`
-instead.
-
-The GitHub Models catalog is not the OpenAI catalog. A model name that is valid against
-`api.openai.com` can return 404 against `https://models.inference.ai.azure.com`, so a
-run that falls back to the `GitHubToken` branch and keeps the same model name gets a 404
-that looks like an outage rather than a wrong catalog. Name a model the endpoint you
-selected serves.
-
-Check whether `OPENAI_API_KEY` is already set in the environment before you configure a
-user secret. It takes precedence, so a run on a machine that already exports one uses
-that key rather than the token you just set, and reports success for the wrong reason.
-
-The .NET SDK has to be installed before any of this. Confirm `dotnet --version` answers
-before scaffolding, rather than after.
-
-Keep `INTELLIGENCE_API_KEY` separate from model-vendor credentials. Do not read, show,
-store, or request a secret value.
+Run `dotnet --version` before you change the project.
 
 ## Documentation
 
 - https://docs.copilotkit.ai/ms-agent-dotnet/quickstart.md
 - https://docs.copilotkit.ai/ms-agent-dotnet/inspector.md
-- https://docs.copilotkit.ai/ms-agent-dotnet/generative-ui/a2ui/fixed-schema.md
+- https://docs.copilotkit.ai/ms-agent-dotnet/generative-ui/tool-based.md
 - https://docs.copilotkit.ai/ms-agent-dotnet/agent-app-context.md
-
-Fetch all four pages in one step rather than one after another. Sequential fetching
-cost about nine minutes of the first proven journey.
+- https://learn.microsoft.com/en-us/agent-framework/integrations/by-component/ui/ag-ui/getting-started
 
 The documentation scope is `ms-agent-dotnet`. The quickstart at that scope is
 byte-identical to the one at `ms-agent-python`: one page serves both languages through
 a `.NET` and `Python` tab group. The scope in the URL does not select the language, so
 read the .NET tab.
 
-Record the selected framework, vendor, model, required credential variable names, and
-these URLs.
-Do not use remembered CopilotKit instructions.
+Use `Microsoft.Agents.AI.Hosting.AGUI.AspNetCore` from the Learn guide. Register the server
+with `AddAGUIServer`. Map the existing `AIAgent` with `MapAGUIServer`. The endpoint accepts
+`RunAgentInput` requests and streams AG-UI events with server-sent events.
 
-A fetch tool that refuses a URL, or fails to reach it, reports a limit of the tool and
-not a fact about the page. Retrieve the same URL a second way before you judge it. Run
-`curl -fsSL <url>`, or read the same page without the `.md` suffix. Treat a page as
-unavailable only after a second method also fails.
+Record the selected framework, provider, model, required credential variable names, and
+these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.17 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.2 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.

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

@@ -1,45 +1,38 @@
 # Configure MS Agent Harness for .NET
 
-Preserve an existing MS Agent Harness model, vendor, credential name, and host setup. The
-documented .NET starter uses GitHub Models. Use that vendor for a new matching setup.
+Preserve an existing MS Agent Harness model, provider, credential name, and host setup.
+Use direct OpenAI for a new setup. Name its credential `OPENAI_API_KEY`.
 
-For GitHub Models, name the user secret `GitHubToken`. Set it from the agent directory
-with `dotnet user-secrets set GitHubToken`. The app must read the same name through .NET
-configuration. Confirm `dotnet --version` works before changing the project.
-
-For an existing OpenAI setup, keep `OPENAI_API_KEY` and the existing OpenAI client. Do not
-convert it to GitHub Models.
-
-Keep `INTELLIGENCE_API_KEY` separate from model-vendor credentials. Do not read, show,
-store, or request a secret value.
+For a user secret, run `dotnet user-secrets set OPENAI_API_KEY` from the agent directory.
+The app must read the same name through .NET configuration. Run `dotnet --version` before
+you change the project.
 
 ## Documentation
 
 - https://docs.copilotkit.ai/ms-agent-harness-dotnet/quickstart.md
 - https://docs.copilotkit.ai/ms-agent-harness-dotnet/inspector.md
-- https://docs.copilotkit.ai/ms-agent-harness-dotnet/generative-ui/a2ui/fixed-schema.md
+- https://docs.copilotkit.ai/ms-agent-harness-dotnet/generative-ui/tool-based.md
 - https://docs.copilotkit.ai/ms-agent-harness-dotnet/agent-app-context.md
-
-Fetch all four pages in one step rather than one after another.
+- https://learn.microsoft.com/en-us/agent-framework/get-started/harness
+- https://learn.microsoft.com/en-us/agent-framework/integrations/by-component/ui/ag-ui/getting-started
 
 The documentation scope is `ms-agent-harness-dotnet`. Read only the `.NET` tab of the
 quickstart. Do not use its Python tab. Use `Microsoft.Agents.AI.Harness --version 1.19.0`
 for the stable agent package. The current AG-UI host package is
 `Microsoft.Agents.AI.Hosting.AGUI.AspNetCore --version 1.19.0-preview.260822.1`.
-Use `AddAGUIServer` service registration and a `MapAGUIServer` endpoint. The older
-showcase uses `AddAGUI` and `MapAGUI`. Do not copy those stale names into the current
-host. Register the remote endpoint in Copilot Runtime with `HttpAgent`.
+Use `AddAGUIServer` service registration and a `MapAGUIServer` endpoint. Register the
+remote endpoint in Copilot Runtime with `HttpAgent`.
 
-The quickstart's generic .NET example uses `CreateAIAgent`. Do not replace an existing
-Harness agent with that example. For a new Harness agent, use `AsHarnessAgent` with
-`HarnessAgentOptions`. Disable built-in providers that add environment-dependent tools,
-then pass the project-owned tools through `ChatOptions`.
+The Learn Harness guide creates a Harness agent from an `IChatClient` with
+`AsHarnessAgent`. Keep one `AgentSession` across turns. The quickstart's generic .NET
+example uses `CreateAIAgent`. Do not replace an existing Harness agent with that example.
+For a new Harness agent, use `AsHarnessAgent` with `HarnessAgentOptions`. Disable built-in
+providers that add environment-dependent tools. Pass the project-owned tools through
+`ChatOptions`.
 
-For fixed-schema A2UI, keep the C# tool and its inline schema in the Harness agent. Set
-`injectA2UITool` to `false` in the runtime. The page omits a bundled setup block, and its
-action-handler note describes Python SDK behavior. Do not infer C# action-handler support
-from the Python-only note. If the visible C# steps do not cover the requested setup, run
-the unsupported route below.
+A2UI is not on this path. If the developer asks for it, say first that its page omits a
+bundled setup block and that its action-handler note describes Python SDK behavior, so C#
+action-handler support cannot be inferred from it.
 
 A bare `HarnessAgent` does not consume AG-UI app context. The published example adds a
 custom `DelegatingAIAgent` wrapper that reads context from `ChatOptions.AdditionalProperties`
@@ -47,16 +40,11 @@ and injects a system message. Keep app context unsupported until that wrapper pa
 browser proof. Do not copy the page's generic `CreateAIAgent` constructor over an existing
 Harness agent.
 
-Record the selected framework, vendor, model, required credential variable names, these
-URLs, and the quickstart and A2UI gaps. Do not use remembered CopilotKit instructions.
-
-A fetch tool that refuses a URL, or fails to reach it, reports a limit of the tool and
-not a fact about the page. Retrieve the same URL a second way before you judge it. Run
-`curl -fsSL <url>`, or read the same page without the `.md` suffix. Treat a page as
-unavailable only after a second method also fails.
+Record the selected framework, provider, model, required credential variable names, these
+URLs, and the quickstart gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.17 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.2 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.

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

@@ -12,19 +12,13 @@ looks finished and reads no key.
 This framework reads no `.env` on its own. Whatever loads the file is application code,
 so a scaffold that writes `agent/.env` and never loads it starts with no credential.
 
-Keep `INTELLIGENCE_API_KEY` separate from model-vendor credentials. Do not read, show,
-store, or request a secret value.
-
 ## Documentation
 
 - https://docs.copilotkit.ai/ms-agent-python/quickstart.md
 - https://docs.copilotkit.ai/ms-agent-python/inspector.md
-- https://docs.copilotkit.ai/ms-agent-python/generative-ui/a2ui/fixed-schema.md
+- https://docs.copilotkit.ai/ms-agent-python/generative-ui/tool-based.md
 - https://docs.copilotkit.ai/ms-agent-python/agent-app-context.md
 
-Fetch all four pages in one step rather than one after another. Sequential fetching
-cost about nine minutes of the first proven journey.
-
 The documentation scope is `ms-agent-python`. The quickstart at that scope is
 byte-identical to the one at `ms-agent-dotnet`: one page serves both languages through
 a `.NET` and `Python` tab group. The scope in the URL does not select the language, so
@@ -32,15 +26,9 @@ read the Python tab. The first code block on the page is the .NET one.
 
 Record the selected framework, vendor, model, required credential variable names, and
 these URLs.
-Do not use remembered CopilotKit instructions.
-
-A fetch tool that refuses a URL, or fails to reach it, reports a limit of the tool and
-not a fact about the page. Retrieve the same URL a second way before you judge it. Run
-`curl -fsSL <url>`, or read the same page without the `.md` suffix. Treat a page as
-unavailable only after a second method also fails.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.17 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.2 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.

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

@@ -6,43 +6,44 @@ its credential variables and setup steps.
 
 Name the default model credential `OPENAI_API_KEY`.
 
-Keep `INTELLIGENCE_API_KEY` separate from model-vendor credentials. Do not read, show,
-store, or request a secret value.
-
 ## Documentation
 
 - https://docs.copilotkit.ai/pydantic-ai/quickstart.md
 - https://docs.copilotkit.ai/pydantic-ai/inspector.md
-- https://docs.copilotkit.ai/pydantic-ai/generative-ui/a2ui/fixed-schema.md
+- https://docs.copilotkit.ai/pydantic-ai/generative-ui/tool-based.md
+- https://docs.copilotkit.ai/pydantic-ai/agent-app-context.md
 - https://docs.copilotkit.ai/reference/v2/hooks/useAgentContext.md
 
-Fetch all four pages in one step rather than one after another.
-
 The documentation scope is `pydantic-ai`. For an existing agent, install the exact
 documented backend set with
 `uv add 'pydantic-ai-slim[ag-ui,openai]>=2,<3' 'starlette>=0.46.2' uvicorn`.
-Keep the Starlette endpoint that calls `AGUIAdapter.dispatch_request`. Register it in
-Copilot Runtime with `HttpAgent` and keep `InMemoryAgentRunner` for the documented local
-OSS setup. Do not replace this transport with a different Pydantic AI adapter.
-
-For fixed-schema A2UI, keep the tool in the agent. Set `injectA2UITool` to `false` in the
-runtime. The documented Python setup does not support `action_handlers` on
-`a2ui.render`. Do not add them or claim that the fixed-schema button callback works.
-
-No Pydantic AI agent-app-context Markdown page is available. The reference page above
-documents the frontend hook only. Do not invent the missing agent-side context setup. If
-the requested work needs that setup, run the unsupported route below.
+Keep the Starlette endpoint that calls `AGUIAdapter.dispatch_request`, unless the app
+context route below replaces it with the two-step form. Register it in Copilot Runtime
+with `HttpAgent` and keep `InMemoryAgentRunner` for the documented local OSS setup. Do not replace this transport with a different Pydantic AI adapter.
+
+A2UI is not on this path. If the developer asks for it, say first that the documented
+Python setup does not support `action_handlers` on `a2ui.render`, so its button callback
+cannot return a decision to the agent.
+
+The AG-UI adapter does not pass `RunAgentInput.context` to the agent, and it does not
+warn when it drops it. The frontend hook alone leaves the agent with nothing, and the
+agent still answers as though it had the data. Wiring `useAgentContext` is not enough on
+its own.
+
+Follow the agent-app-context page above for the agent side. Build the adapter with
+`AGUIAdapter.from_request`, pass `adapter.run_input.context` into `deps`, and read the
+entries back through a tool. `dispatch_request` parses the request itself and leaves no
+`run_input`, so the context route needs the two-step form even though every other route
+here uses the one-liner. Parse `value` with `json.loads`: the hook stringifies it and
+AG-UI types it as a string, so a shape check on it never passes. Never build
+`instructions` from an entry. Entries are client-submitted and reach the model as tool
+output only.
 
 Record the selected framework, vendor, model, required credential variable names, these
-URLs, and the context and A2UI limits. Do not use remembered CopilotKit instructions.
-
-A fetch tool that refuses a URL, or fails to reach it, reports a limit of the tool and
-not a fact about the page. Retrieve the same URL a second way before you judge it. Run
-`curl -fsSL <url>`, or read the same page without the `.md` suffix. Treat a page as
-unavailable only after a second method also fails.
+URLs, and the two-step context route.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.17 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.2 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.

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

@@ -6,37 +6,28 @@ credential variables and setup steps.
 
 Name the default model credential `OPENAI_API_KEY`.
 
-Keep `INTELLIGENCE_API_KEY` separate from model-vendor credentials. Do not read, show,
-store, or request a secret value.
-
 ## Documentation
 
 - https://docs.copilotkit.ai/strands/quickstart.md
 - https://docs.copilotkit.ai/strands/inspector.md
-- https://docs.copilotkit.ai/strands/generative-ui/a2ui/fixed-schema.md
+- https://docs.copilotkit.ai/strands/generative-ui/tool-based.md
 - https://docs.copilotkit.ai/strands/shared-state/agent-readonly.md
 
-Fetch all four pages in one step rather than one after another.
-
 The documentation scope is `strands`. Use the Python examples from these pages.
-The fixed-schema A2UI tool makes its own OpenAI call. Set `injectA2UITool` to `false` when
-the fixed-schema A2UI tool makes its own OpenAI call. This prevents a second injected A2UI
-tool from changing the documented setup.
+
+A2UI is not on this path. If the developer asks for it, say first that the fixed-schema
+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 needs that missing setup, run the
 unsupported route below.
 
 Record the selected framework, vendor, model, required credential variable names, these
-URLs, and the context documentation gap. Do not use remembered CopilotKit instructions.
-
-A fetch tool that refuses a URL, or fails to reach it, reports a limit of the tool and
-not a fact about the page. Retrieve the same URL a second way before you judge it. Run
-`curl -fsSL <url>`, or read the same page without the `.md` suffix. Treat a page as
-unavailable only after a second method also fails.
+URLs, and the context documentation gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.17 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.2 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.

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

@@ -6,37 +6,29 @@ credential variables and setup steps.
 
 Name the default model credential `OPENAI_API_KEY`.
 
-Keep `INTELLIGENCE_API_KEY` separate from model-vendor credentials. Do not read, show,
-store, or request a secret value.
-
 ## Documentation
 
 - https://docs.copilotkit.ai/strands-typescript/quickstart.md
 - https://docs.copilotkit.ai/strands-typescript/inspector.md
-- https://docs.copilotkit.ai/strands-typescript/generative-ui/a2ui/fixed-schema.md
+- https://docs.copilotkit.ai/strands-typescript/generative-ui/tool-based.md
 - https://docs.copilotkit.ai/strands-typescript/shared-state/agent-readonly.md
 
-Fetch all four pages in one step rather than one after another.
-
 The documentation scope is `strands-typescript`. Use only the TypeScript examples from
 these pages. Install `@modelcontextprotocol/sdk` as a runtime dependency.
 `@strands-agents/sdk` loads it even when the application does not use MCP.
 
-The fixed-schema page has no Strands TypeScript backend example. No Strands TypeScript
-agent-app-context Markdown page is available. Do not translate another language's backend
-example or invent either missing setup. If the requested work needs either missing setup,
+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 needs it,
 run the unsupported route below.
 
-Record the selected framework, vendor, model, required credential variable names, these
-URLs, and both documentation gaps. Do not use remembered CopilotKit instructions.
+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.
 
-A fetch tool that refuses a URL, or fails to reach it, reports a limit of the tool and
-not a fact about the page. Retrieve the same URL a second way before you judge it. Run
-`curl -fsSL <url>`, or read the same page without the `.md` suffix. Treat a page as
-unavailable only after a second method also fails.
+Record the selected framework, vendor, model, required credential variable names, these
+URLs, and the context documentation gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.2 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.17 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.2 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/angular.md

@@ -5,34 +5,37 @@ 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.
+`npx --yes copilotkit@4.9.17 onboard read starter/clone` before you fetch documentation.
 
 ## Documentation
 
-- Credentials and plan: `Not applicable`
-- Implementation and validation: https://docs.copilotkit.ai/angular.md
-- Proof: https://docs.copilotkit.ai/angular.md
-- Frontend context: https://docs.copilotkit.ai/reference/angular/directives/CopilotKitAgentContext.md
-
-Fetch both selected documentation pages in one step rather than one after another.
-Record Angular as the selected frontend and keep these URLs. Do not use remembered
-CopilotKit instructions.
+- https://docs.copilotkit.ai/angular.md
+- https://docs.copilotkit.ai/angular/inspector.md
+- https://docs.copilotkit.ai/reference/angular/directives/CopilotKitAgentContext.md
+- https://docs.copilotkit.ai/angular/guides/frontend-tools-generative-ui.md
 
 Take the frontend-context step from the directive page. The agent-framework page shows
 the React hook, and Angular shares the same context through this directive instead.
+Use the Inspector page for proof.
+
+Angular has no `useComponent`. Render the terminal component with `registerComponent` from
+`@copilotkit/angular`, from the generative-UI guide above. The component is an ordinary
+`ToolRenderer`: it takes a required `toolCall` signal input and reads `toolCall().args`.
+The framework page shows the React hook. This function is Angular's equivalent, and the
+two are the same tool to the agent, so nothing changes on the agent side.
+
+`registerComponent` takes no `handler`, because the component only displays. If the
+installed `@copilotkit/angular` does not export it, use `registerFrontendTool` with the
+same `component` and `handler: async () => {}` instead, and record that substitution. Do
+not give the handler a body: a display-only tool that returns a value writes it into the
+thread as the tool's result.
 
 Angular CLI 22 requires Node `^22.22.3 || ^24.15.0 || >=26`. Check the Node version before
 you create or build an Angular project. If the installed version is lower, select a
 supported version first and use it for every later command in this project.
 
-A fetch tool that refuses a URL, or fails to reach it, reports a limit of the tool and
-not a fact about the page. Retrieve the same URL a second way before you judge it. Run
-`curl -fsSL <url>`, or read the same page without the `.md` suffix. Treat a page as
-unavailable only after a second method also fails.
-
-If the page supports the selection, run
-`npx --yes copilotkit@4.9.2 onboard read credentials/finalize-plan`.
+If the pages support the selection, record Angular and these URLs. Then run
+`npx --yes copilotkit@4.9.17 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.2 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/nextjs.md

@@ -15,29 +15,19 @@ 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 --yes copilotkit@4.9.2 onboard read starter/clone` before you fetch documentation.
+`npx --yes copilotkit@4.9.17 onboard read starter/clone` before you fetch documentation.
 
 ## Documentation
 
-- Credentials and plan: `Not applicable`
-- Implementation and validation: https://docs.copilotkit.ai/quickstart.md
-- Proof: https://docs.copilotkit.ai/quickstart.md
-
-Fetch each selected documentation URL. Record Next.js as the selected frontend and keep
-these URLs. Do not use remembered CopilotKit instructions.
+- https://docs.copilotkit.ai/quickstart.md
 
 Take the frontend scaffolding from this page. Take the runtime agent wiring from the
 agent framework documentation instead. This page configures the CopilotKit built-in
 agent as the default agent, which is correct only for a project that has no agent.
 Do not replace the developer's existing agent with the built-in agent.
 
-A fetch tool that refuses a URL, or fails to reach it, reports a limit of the tool and
-not a fact about the page. Retrieve the same URL a second way before you judge it. Run
-`curl -fsSL <url>`, or read the same page without the `.md` suffix. Treat a page as
-unavailable only after a second method also fails.
-
-If the pages support the selection, run
-`npx --yes copilotkit@4.9.2 onboard read credentials/finalize-plan`.
+If the page supports the selection, record Next.js and this URL. Then run
+`npx --yes copilotkit@4.9.17 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.2 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/plan.md

@@ -5,9 +5,9 @@ that the repository does not show. Do not change application code in this phase.
 
 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 frontend is unknown, ask only whether to use the
-recommended frontend. If the developer declines it, ask one follow-up question that lists
-the valid frontend choices. Do not ask about the model or project in this step.
+the alternatives short. When the frontend is unknown, use this rule: Ask one frontend
+question that lists the recommendation and valid choices. Do not ask a yes-or-no question
+first. Do not ask about the model or project in this step.
 
 If the project has a frontend, preserve it and use the matching route below. If the project
 needs a frontend, show the valid choices and one recommendation based on repository
@@ -22,18 +22,13 @@ CopilotKit runtime lives: Next.js hosts it in a route handler, Angular in its SS
 server, and Vue 3, React SPA and React Native reach a runtime that runs as its own
 process.
 
-A fetch tool that refuses a URL, or fails to reach it, reports a limit of the tool and
-not a fact about the page. Retrieve the same URL a second way before you judge it. Run
-`curl -fsSL <url>`, or read the same page without the `.md` suffix. Treat a page as
-unavailable only after a second method also fails.
-
 Use exactly one matching internal route:
 
-1. React SPA: `npx --yes copilotkit@4.9.2 onboard read frontend/react-spa`
-2. Next.js: `npx --yes copilotkit@4.9.2 onboard read frontend/nextjs`
-3. Angular: `npx --yes copilotkit@4.9.2 onboard read frontend/angular`
-4. Vue 3: `npx --yes copilotkit@4.9.2 onboard read frontend/vue`
-5. React Native: `npx --yes copilotkit@4.9.2 onboard read frontend/react-native`
+1. React SPA: `npx --yes copilotkit@4.9.17 onboard read frontend/react-spa`
+2. Next.js: `npx --yes copilotkit@4.9.17 onboard read frontend/nextjs`
+3. Angular: `npx --yes copilotkit@4.9.17 onboard read frontend/angular`
+4. Vue 3: `npx --yes copilotkit@4.9.17 onboard read frontend/vue`
+5. React Native: `npx --yes copilotkit@4.9.17 onboard read frontend/react-native`
 
 If no listed frontend fits, run
-`npx --yes copilotkit@4.9.2 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.

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

@@ -4,21 +4,18 @@ Preserve an existing React Native frontend. Use the selected page for a new fron
 
 ## Documentation
 
-- Credentials and plan: `Not applicable`
-- Implementation and validation: https://docs.copilotkit.ai/react-native.md
-- Proof: https://docs.copilotkit.ai/react-native.md
+- https://docs.copilotkit.ai/react-native.md
+- https://docs.copilotkit.ai/troubleshooting/event-inspector.md
 
-Fetch the selected documentation page. Record React Native as the selected frontend and
-keep this URL. Do not use remembered CopilotKit instructions.
+Use the Event Inspector page for proof.
 
-A fetch tool that refuses a URL, or fails to reach it, reports a limit of the tool and
-not a fact about the page. Retrieve the same URL a second way before you judge it. Run
-`curl -fsSL <url>`, or read the same page without the `.md` suffix. Treat a page as
-unavailable only after a second method also fails.
+Render the terminal component with `useComponent` from `@copilotkit/react-native`. The
+package re-exports it from react-core, and it behaves as it does on the web. The page also
+documents `useRenderTool`, which is React Native's own hook for drawing a tool the agent
+already has. That is a different job and needs a tool in the agent.
 
-If the page supports the selection, run
-`npx --yes copilotkit@4.9.2 onboard read credentials/finalize-plan`.
+If the pages support the selection, record React Native and these URLs. Then run
+`npx --yes copilotkit@4.9.17 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.2 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.

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

@@ -8,20 +8,10 @@ not move the agent into it.
 
 ## Documentation
 
-- Credentials and plan: `Not applicable`
-- Implementation and validation: https://docs.copilotkit.ai/react-spa.md
-- Proof: https://docs.copilotkit.ai/react-spa.md
+- https://docs.copilotkit.ai/react-spa.md
 
-Fetch the selected documentation page. Record React SPA as the selected frontend and
-keep this URL. Do not use remembered CopilotKit instructions.
+If the page supports the selection, record React SPA and this URL. Then run
+`npx --yes copilotkit@4.9.17 onboard read credentials/finalize-plan`.
 
-A fetch tool that refuses a URL, or fails to reach it, reports a limit of the tool and
-not a fact about the page. Retrieve the same URL a second way before you judge it. Run
-`curl -fsSL <url>`, or read the same page without the `.md` suffix. Treat a page as
-unavailable only after a second method also fails.
-
-If the page supports the selection, run
-`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.2 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.