copilotkit 4.9.1 → 4.9.4

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

@@ -24,7 +24,7 @@ starts. Choose one starting state: empty, agent-only, frontend-only, both, both-
 Run this command with the exact selected slugs:
 
 ```text
-npx --yes copilotkit@4.9.1 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend>
+npx --yes copilotkit@4.9.4 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
@@ -35,12 +35,10 @@ prompts gave, then run the command again.
 Use the target app or runtime directory from the repository findings. If a nested app owns
 the runtime `.env` file, do not default to the repository root.
 
-If valid project fields and a non-empty `INTELLIGENCE_API_KEY` already exist, ask whether to
-keep that selection. Recommend keeping it to avoid minting another key. Ask the developer to
-confirm that the prior project selection had no key-provision warning.
-
-Reused project credentials remain unverified until an authenticated Intelligence call
-succeeds. Record that state in the plan.
+If valid project fields and a non-empty `INTELLIGENCE_API_KEY` already exist, use this
+rule: Reuse that project without another question. Do not mint another key. The round-trip
+proof later runs the authenticated Intelligence checks. Record the reused project
+credentials as unverified in the plan until those checks pass.
 
 If the developer needs a project or another project, do the selection yourself from the
 target directory. Do not send the developer to another terminal.
@@ -48,7 +46,7 @@ target directory. Do not send the developer to another terminal.
 Read the choices first:
 
 ```text
-npx --yes copilotkit@4.9.1 project list --json
+npx --yes copilotkit@4.9.4 project list --json
 ```
 
 With `--json` the payload is the only thing on standard output, so it is safe to parse.
@@ -59,7 +57,7 @@ developer asks.
 If the developer searches, run:
 
 ```text
-npx --yes copilotkit@4.9.1 project list --search <query> --json
+npx --yes copilotkit@4.9.4 project list --search <query> --json
 ```
 
 If the developer asks for all projects, show the result of the first list command. Ask
@@ -69,7 +67,7 @@ frontend, framework, model, credential, or plan-approval question.
 Then record their answer, from the target directory:
 
 ```text
-npx --yes copilotkit@4.9.1 project select --project <slug-or-id> --json
+npx --yes copilotkit@4.9.4 project select --project <slug-or-id> --json
 ```
 
 Use `--create <name> --json` instead when they want a new project. The two flags cannot be
@@ -123,28 +121,37 @@ it. The credential reaches the platform only when the runtime is constructed wit
 Intelligence client, and a runtime built without one compiles, serves, answers in a
 browser, and never touches the platform.
 
-Add this page to the selected documentation URLs for both subagents:
+Add these pages to the selected documentation URLs for the planning, implementation, and
+proof subagents:
 
 - https://docs.copilotkit.ai/premium/connect-your-runtime.md
+- https://docs.copilotkit.ai/backend/runtime-endpoints.md
+- https://docs.copilotkit.ai/premium/managed-intelligence-platform.md
 
-Fetch it together with the pages already selected rather than on its own.
+Fetch them together with the pages already selected rather than on their own.
 
 Spawn one planning subagent. Give it the full text of the planning brief at the end of this
 prompt, the repository findings, selected framework, frontend, model, credential variable
-names, and selected documentation URLs. Wait for the subagent to finish.
+names, selected documentation URLs, and documentation policy. 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.1 onboard read implementation/build-and-validate`.
+`npx --yes copilotkit@4.9.4 onboard read implementation/build-and-validate`.
 
 If no exact supported path or documentation URL exists, run
-`npx --yes copilotkit@4.9.1 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.4 onboard read unsupported/no-validated-path`.
 
 ## Planning subagent brief
 
@@ -155,20 +162,13 @@ Everything below the rule is the subagent's prompt. Give it verbatim.
 # Create the onboarding plan
 
 Use the selected framework, frontend, model, repository findings, and documentation URLs
-from the main coding agent. Fetch every selected URL in one step rather than one after
-another. 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. Report a
-documentation gap only after a second method also fails.
+from the main coding agent. Follow the documentation policy it gives you.
 
 Name the application the project asks for, and plan that application. Each documentation
 page teaches through one worked example, and that example carries a domain of its own.
-The domain belongs to the page. The project's purpose from the repository findings
-decides what gets built. Where the two differ, the project wins. Where the repository
-never states a purpose, say so in the plan and ask the developer before you adopt the
-domain of an example.
+The domain belongs to the page. Use the purpose from the repository findings, or the
+developer outcome if the repository purpose was unproved. Do not ask for it again. Where
+the documentation example differs from that purpose, the project wins.
 
 Read only inside the project directory. Answer an API question from the documentation
 URLs you were given, not from another checkout on this machine.
@@ -185,10 +185,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,11 +4,23 @@ 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.
 
+Keep `INTELLIGENCE_API_KEY` separate from every model-vendor credential. Do not read,
+show, store, or copy either credential.
+
+This documentation policy applies to every framework and frontend route below. Deduplicate
+the selected URL list and fetch each URL once. Fetch all selected URLs in one step. 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. Give this
+policy to every documentation subagent. A page that is still unavailable after the second
+method does not support the selection.
+
 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.
+the alternatives short. When the framework is unknown, use this rule: Ask one framework
+question that lists the recommendation and valid choices. Do not ask a yes-or-no question
+first. Do not ask about the frontend, model, or project in this step.
 
 These are the agent frameworks and their default vendors:
 
@@ -27,9 +39,9 @@ These are the agent frameworks and their default vendors:
 | LangGraph TypeScript               | OpenAI          |
 | LlamaIndex                         | OpenAI          |
 | Mastra                             | OpenAI          |
-| Microsoft Agent Framework (.NET)   | GitHub Models   |
+| Microsoft Agent Framework (.NET)   | OpenAI          |
 | Microsoft Agent Framework (Python) | OpenAI          |
-| MS Agent Harness (.NET)            | GitHub Models   |
+| MS Agent Harness (.NET)            | OpenAI          |
 | Pydantic AI                        | OpenAI          |
 | Strands Agents (Python)            | OpenAI          |
 | Strands Agents (TypeScript)        | OpenAI          |
@@ -51,26 +63,26 @@ another framework. Do not show the internal route.
 
 Use exactly one matching internal route:
 
-1. AG2: `npx --yes copilotkit@4.9.1 onboard read framework/ag2`
-2. Agno: `npx --yes copilotkit@4.9.1 onboard read framework/agno`
-3. Built-in CopilotKit agent: `npx --yes copilotkit@4.9.1 onboard read framework/built-in`
-4. Claude Agent SDK Python: `npx --yes copilotkit@4.9.1 onboard read framework/claude-sdk-python`
-5. Claude Agent SDK TypeScript: `npx --yes copilotkit@4.9.1 onboard read framework/claude-sdk-typescript`
-6. CrewAI Flows: `npx --yes copilotkit@4.9.1 onboard read framework/crewai-flows`
-7. Deep Agents: `npx --yes copilotkit@4.9.1 onboard read framework/deep-agents`
-8. LangGraph Python: `npx --yes copilotkit@4.9.1 onboard read framework/langgraph-python`
-9. LangGraph FastAPI: `npx --yes copilotkit@4.9.1 onboard read framework/langgraph-fastapi`
-10. LangGraph TypeScript: `npx --yes copilotkit@4.9.1 onboard read framework/langgraph-typescript`
-11. LlamaIndex: `npx --yes copilotkit@4.9.1 onboard read framework/llamaindex`
-12. ADK: `npx --yes copilotkit@4.9.1 onboard read framework/google-adk`
-13. Microsoft Agent Framework Python: `npx --yes copilotkit@4.9.1 onboard read framework/ms-agent-python`
-14. Microsoft Agent Framework .NET: `npx --yes copilotkit@4.9.1 onboard read framework/ms-agent-dotnet`
-15. Mastra: `npx --yes copilotkit@4.9.1 onboard read framework/mastra`
-16. MS Agent Harness .NET: `npx --yes copilotkit@4.9.1 onboard read framework/ms-agent-harness-dotnet`
-17. Pydantic AI: `npx --yes copilotkit@4.9.1 onboard read framework/pydantic-ai`
-18. Strands Agents Python: `npx --yes copilotkit@4.9.1 onboard read framework/strands-python`
-19. Strands Agents TypeScript: `npx --yes copilotkit@4.9.1 onboard read framework/strands-typescript`
+1. AG2: `npx --yes copilotkit@4.9.4 onboard read framework/ag2`
+2. Agno: `npx --yes copilotkit@4.9.4 onboard read framework/agno`
+3. Built-in CopilotKit agent: `npx --yes copilotkit@4.9.4 onboard read framework/built-in`
+4. Claude Agent SDK Python: `npx --yes copilotkit@4.9.4 onboard read framework/claude-sdk-python`
+5. Claude Agent SDK TypeScript: `npx --yes copilotkit@4.9.4 onboard read framework/claude-sdk-typescript`
+6. CrewAI Flows: `npx --yes copilotkit@4.9.4 onboard read framework/crewai-flows`
+7. Deep Agents: `npx --yes copilotkit@4.9.4 onboard read framework/deep-agents`
+8. LangGraph Python: `npx --yes copilotkit@4.9.4 onboard read framework/langgraph-python`
+9. LangGraph FastAPI: `npx --yes copilotkit@4.9.4 onboard read framework/langgraph-fastapi`
+10. LangGraph TypeScript: `npx --yes copilotkit@4.9.4 onboard read framework/langgraph-typescript`
+11. LlamaIndex: `npx --yes copilotkit@4.9.4 onboard read framework/llamaindex`
+12. ADK: `npx --yes copilotkit@4.9.4 onboard read framework/google-adk`
+13. Microsoft Agent Framework Python: `npx --yes copilotkit@4.9.4 onboard read framework/ms-agent-python`
+14. Microsoft Agent Framework .NET: `npx --yes copilotkit@4.9.4 onboard read framework/ms-agent-dotnet`
+15. Mastra: `npx --yes copilotkit@4.9.4 onboard read framework/mastra`
+16. MS Agent Harness .NET: `npx --yes copilotkit@4.9.4 onboard read framework/ms-agent-harness-dotnet`
+17. Pydantic AI: `npx --yes copilotkit@4.9.4 onboard read framework/pydantic-ai`
+18. Strands Agents Python: `npx --yes copilotkit@4.9.4 onboard read framework/strands-python`
+19. Strands Agents TypeScript: `npx --yes copilotkit@4.9.4 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.1 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.4 onboard read unsupported/no-validated-path`.

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

@@ -1,19 +1,25 @@
 # Build from the best available official documentation
 
-Tell the implementation subagent which plan steps lack direct documentation. Give it the
-approved plan, repository findings, and all official documentation that you found.
+Work only in the target project directory. Do not read, show, store, or request a secret
+value.
+
+Spawn one implementation subagent. Tell it which plan steps lack direct documentation.
+Give it the approved plan, repository findings, target project directory, and all official
+documentation that you fetched for the plan.
 
 Tell the subagent to preserve the existing project. It must not invent a CopilotKit API.
 It can combine compatible APIs from different official pages when one page omits the
 selected framework and frontend combination.
 
-Run the approved implementation and validation steps. Repair a failure in new work at most
-three times. Stop if the fix requires changes to the developer's existing agent or
-frontend.
+Tell the implementation subagent to run the approved implementation and validation steps.
+Send a failure in new work back to it at most three times. Stop if a fix requires changes
+to the developer's existing agent or frontend.
 
-After validation passes, prove the runtime, agent round trip, and real frontend path. Use
-the same proof rules from the approved plan. Keep the development servers running after
-proof.
+After validation passes, use this rule: Spawn one proof subagent. Give it the approved
+plan, validation evidence, target project directory, all official documentation that you
+fetched for the plan, and recorded browser or device control. Tell it to prove the runtime,
+agent round trip, and real frontend path with the same proof rules from the approved plan.
+Keep the development servers running after proof.
 
 Do not block core proof on CopilotKit Skills or MCP configuration. Try these tools after
 the application passes proof. Report each tool result separately.
@@ -21,16 +27,21 @@ 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.1 onboard complete`, carrying the
+When the proof is complete, run `npx --yes copilotkit@4.9.4 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.1 onboard complete --visual-check <outcome>
-npx --yes copilotkit@4.9.1 onboard complete --device-check <outcome>
+npx --yes copilotkit@4.9.4 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.9.4 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.
+
+If the proof passed and something after it still blocked this run, add
+`--blocked-by <cause>` to the same command, with one of `hosted-dashboard`, `inspector`,
+`plan-excluded-capability`, or `other`. It ends the run as blocked and names what the
+blocker leaves unverified.

package/onboarding/prompts/framework/ag2.md

@@ -6,9 +6,6 @@ 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/ag2/quickstart.md
@@ -16,8 +13,6 @@ store, or request a secret value.
 - https://docs.copilotkit.ai/ag2/generative-ui/a2ui/fixed-schema.md
 - https://docs.copilotkit.ai/ag2/readables.md
 
-Fetch all four pages in one step rather than one after another.
-
 The documentation scope is `ag2`. Use only the Python examples from these pages.
 Preserve the existing `AGUIStream` endpoint and its route. The quickstart uses a sample
 repository with `uv sync`. It does not name a dependency list for an existing project.
@@ -33,16 +28,10 @@ The Readables page includes the AG2 backend context path. Use its `ContextVariab
 framework's context setup.
 
 Record the selected framework, vendor, model, required credential variable names, these
-URLs, and the fixed-schema 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 fixed-schema documentation gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.1 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.4 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.1 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.4 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/agno.md

@@ -6,9 +6,6 @@ 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/agno/quickstart.md
@@ -16,8 +13,6 @@ store, or request a secret value.
 - https://docs.copilotkit.ai/agno/generative-ui/a2ui/fixed-schema.md
 - https://docs.copilotkit.ai/agno/shared-state/agent-readonly.md
 
-Fetch all four pages in one step rather than one after another.
-
 The documentation scope is `agno`. Use only the Python agent examples from these pages.
 When the repository already has an Agno agent, use the quickstart's
 `Use an existing agent` path. Use `Start from scratch` only when the repository needs a
@@ -33,16 +28,10 @@ Do not invent either missing backend setup. If the requested work needs one of t
 setups and the project does not already have it, run the unsupported route below.
 
 Record the selected framework, vendor, model, required credential variable names, these
-URLs, the documented dependencies and adapter, and both documentation 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.
+URLs, the documented dependencies and adapter, and both documentation gaps.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.1 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.4 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.1 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.4 onboard read unsupported/no-validated-path`.

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

@@ -6,9 +6,6 @@ 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.
-
 The built-in agent runs in the CopilotKit Runtime process.
 Do not create or start a separate agent server.
 Keep the agent, model choice, tools, and runtime endpoint in the project's existing
@@ -23,21 +20,14 @@ runtime setup.
 - https://docs.copilotkit.ai/model-selection.md
 - https://docs.copilotkit.ai/generative-ui/tool-based.md
 
-Fetch all six pages in one step rather than one after another.
-
 These pages use the root documentation scope. Do not add a framework path segment to
 their URLs. Use the tool-based generative UI page for this built-in route.
 
 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.
+these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.1 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.4 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.1 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.4 onboard read unsupported/no-validated-path`.

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

@@ -7,9 +7,6 @@ name its credential variables and setup steps.
 Name the model credential `ANTHROPIC_API_KEY`. The documented model variable is
 `ANTHROPIC_MODEL`.
 
-Keep `INTELLIGENCE_API_KEY` separate from model-vendor credentials. Do not read, show,
-store, or request a secret value.
-
 ## Documentation
 
 - https://docs.copilotkit.ai/claude-sdk-python/quickstart.md
@@ -17,8 +14,6 @@ store, or request a secret value.
 - https://docs.copilotkit.ai/claude-sdk-python/generative-ui/a2ui/fixed-schema.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 `claude-sdk-python`. For an existing agent, install the exact
 documented backend set with
 `uv add claude-agent-sdk ag-ui-claude-sdk ag-ui-protocol anthropic fastapi uvicorn python-dotenv`.
@@ -35,15 +30,10 @@ page above documents the frontend hook only. Do not invent the missing agent-sid
 setup. If the requested work needs that setup, run the unsupported route below.
 
 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 context and A2UI limits.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.1 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.4 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.1 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.4 onboard read unsupported/no-validated-path`.

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

@@ -7,9 +7,6 @@ name its credential variables and setup steps.
 Name the model credential `ANTHROPIC_API_KEY`. The documented model variable is
 `CLAUDE_MODEL`.
 
-Keep `INTELLIGENCE_API_KEY` separate from model-vendor credentials. Do not read, show,
-store, or request a secret value.
-
 ## Documentation
 
 - https://docs.copilotkit.ai/claude-sdk-typescript/quickstart.md
@@ -17,8 +14,6 @@ store, or request a secret value.
 - https://docs.copilotkit.ai/claude-sdk-typescript/generative-ui/a2ui/fixed-schema.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 `claude-sdk-typescript`. For an existing agent, install the
 documented packages, including `@anthropic-ai/claude-agent-sdk@^0.2.58`,
 `@anthropic-ai/sdk`, `@ag-ui/claude-agent-sdk`, `@ag-ui/core`, `@ag-ui/encoder`,
@@ -39,15 +34,10 @@ pinned adapter source before using this path. If the package no longer handles
 `input.context`, run the unsupported route below.
 
 Record the selected framework, vendor, model, required credential variable names, these
-URLs, and the adapter and context 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 adapter and context limits.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.1 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.4 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.1 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.4 onboard read unsupported/no-validated-path`.

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

@@ -1,12 +1,9 @@
 # Configure CrewAI Flows
 
-Preserve the project's existing CrewAI Flow, model, and deployment. The selected pages do
-not name a default model vendor or model credential variable. Do not choose a vendor or
-credential name for the developer. Ask only for a choice that the repository does not
-show and the documentation supports.
-
-Keep `INTELLIGENCE_API_KEY` separate from model-vendor credentials. Do not read, show,
-store, or request a secret value.
+Preserve the project's existing CrewAI Flow, provider, model, and deployment. The selected
+pages do not name a default model vendor or model credential variable. If neither the
+repository nor these pages prove a provider, run the unsupported route below. Do not
+choose a vendor or credential name for the developer.
 
 ## Documentation
 
@@ -15,16 +12,13 @@ store, or request a secret value.
 - https://docs.copilotkit.ai/crewai-crews/generative-ui/a2ui/fixed-schema.md
 - https://docs.copilotkit.ai/crewai-crews/shared-state/in-app-agent-read.md
 
-Fetch all four pages in one step rather than one after another.
-
 The public onboarding route ID is `crewai-flows`. The canonical documentation scope is
 `crewai-crews`. The quickstart and feature pages also contain older `/crewai-flows/`
 links. Use the canonical Markdown URLs above and keep the project's CrewAI Flow name.
 
 The quickstart offers `Use the CopilotKit CLI (NextJS only)` and `Code along`. It assumes
-an existing Flow. Preserve the vendor, model, and credential variable that the project
-already uses. The new quickstart example uses GitHub Models. An existing OpenAI Flow can
-keep OpenAI and `OPENAI_API_KEY`. Do not change vendors to match the example.
+an existing Flow. Preserve the provider, model, and credential variable that the project
+already uses. Do not change the provider to match an example.
 
 The current Python base adapter is `ag-ui-crewai==0.3.0`. Add the endpoint to the
 project's FastAPI app with
@@ -40,17 +34,11 @@ The shared-state page is not an agent-app-context guide. Do not use it to invent
 `useAgentContext` backend setup. If the requested work needs app context rather than the
 documented shared-state path, run the unsupported route below.
 
-Record the selected framework, project-defined vendor and model, repository-proven
-credential variable names, these URLs, the adapter, and both documentation 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.
+Record the selected framework, project-defined provider and model, repository-proven
+credential variable names, these URLs, the adapter, and both documentation limits.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.1 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.4 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.1 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.4 onboard read unsupported/no-validated-path`.

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

@@ -6,9 +6,6 @@ page must name 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/deepagents/quickstart.md
@@ -16,8 +13,6 @@ store, or request a secret value.
 - https://docs.copilotkit.ai/deepagents/generative-ui/a2ui/fixed-schema.md
 - https://docs.copilotkit.ai/deepagents/shared-state/agent-readonly.md
 
-Fetch all four pages in one step rather than one after another.
-
 The documentation scope is `deepagents`. Do not use `deep-agents` in a documentation URL.
 The quickstart has Python and TypeScript tabs. Preserve the project's current language.
 Preserve the project's existing deployment path. Choose the same `Deep Agent` or
@@ -30,16 +25,10 @@ agent-app-context setup. If the requested work needs either missing setup, run t
 unsupported route below.
 
 Record the selected framework, language, vendor, model, required credential variable
-names, these URLs, and each 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.
+names, these URLs, and each documentation gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.1 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.4 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.1 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.4 onboard read unsupported/no-validated-path`.

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

@@ -8,9 +8,6 @@ Name the model credential `GOOGLE_API_KEY`. This framework accepts more than one
 spelling, and a scaffold that reaches for a different one looks finished and reads no
 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/google-adk/quickstart.md
@@ -18,9 +15,6 @@ store, or request a secret value.
 - https://docs.copilotkit.ai/google-adk/generative-ui/a2ui/fixed-schema.md
 - https://docs.copilotkit.ai/reference/v2/hooks/useAgentContext.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 `google-adk`. A `/adk/` URL answers with a redirect stub
 whose body is the canonical path, so fetch the `google-adk` form.
 
@@ -32,15 +26,9 @@ agent and not for ADK.
 
 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.1 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.4 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.1 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, run
+`npx --yes copilotkit@4.9.4 onboard read unsupported/no-validated-path`.