copilotkit 4.26.0 → 4.27.0

package/onboarding/prompts/framework/custom-ag-ui.md

@@ -1,20 +1,51 @@
-# Connect an existing AG-UI agent
+# Connect a custom agent
+
+This route is for any agent that is none of the listed frameworks. It has three cases:
+
+1. The project has an agent that speaks AG-UI, such as an `AbstractAgent` subclass that
+   the project wrote, or a service that streams AG-UI events through AG-UI middleware.
+   Connect it as it is.
+2. The project has an agent that does not speak AG-UI. Write an adapter around it: an
+   `AbstractAgent` subclass that calls the agent's existing entry point, such as its
+   function or its HTTP route, and emits AG-UI events, as the `backend/ag-ui.md` page
+   below shows. The adapter is new code. The agent's own code does not change.
+3. The developer wants a new agent on a framework that is not listed. `onboard
+   setup-answers` prints its name as `frameworkName`. The plan builds it with that
+   framework's own documentation and the vendor that `setup/questions` recorded, then
+   connects it as case 1 or case 2. For case 3, the default vendor is
+   OpenAI.
+
+In cases 1 and 2, do not port the agent to a listed framework, and do not rewrite its
+tools, model, or prompts. Preserve its model setup and the credential variable names that
+the repository already uses. An existing agent has no default vendor on this route.
+
+This release offers a new agent on this route OpenAI or an OpenAI-compatible provider
+only. For a new agent, if the developer names Anthropic or Google, say that this release
+supports OpenAI or an OpenAI-compatible provider on this route, that Anthropic and Google
+come in a later release, and offer the built-in CopilotKit agent if they need Anthropic or
+Google now. An existing agent keeps its vendor and model. If it runs on Anthropic or
+Google, add one line to the plan: the page context that CopilotKit sends can fail with
+that vendor until a CopilotKit SDK release fixes it (PE-728).
+
+The research findings name the case and cite the file. Either of these proves case 1:
 
-This route is for an agent that the project already has, that speaks AG-UI, and that is
-none of the listed frameworks. For example, an `AbstractAgent` subclass that the project
-wrote, or a service that streams AG-UI events through AG-UI middleware.
-
-Do not port the agent to a listed framework. Do not rewrite its tools, model, or prompts.
-Preserve its model setup and the credential variable names that the repository already
-uses. This route has no default vendor.
+- a class that extends `AbstractAgent` from `@ag-ui/client` and implements `run`,
+- an endpoint that the project serves and that streams AG-UI events: its response is
+  `text/event-stream`, with events such as `RUN_STARTED` and `TEXT_MESSAGE_CONTENT`.
 
-The research findings must prove that the agent speaks AG-UI. Either of these is proof:
+A package that names AG-UI is not proof. Read the entry point before you choose case 2.
+Case 2 applies only to an entry point that takes a user message and returns the agent's
+answer, from a model or from rules, as a function the runtime can import or as an HTTP
+route. An entry point that
+streams AG-UI events is case 1. If no entry point fits, such as an agent in another
+language with no HTTP route, or code that is not an agent, ask the developer how the agent
+runs, and do not write an adapter yet.
 
-- a class that extends `AbstractAgent` from `@ag-ui/client` and implements `run`,
-- an endpoint that the project serves and that streams AG-UI events.
+Before you end your turn to wait for the developer, report the pause:
 
-A package that names AG-UI is not proof. If the findings prove neither, run the
-unsupported route below.
+```text
+npx --prefer-offline --yes copilotkit@4.27.0 onboard checkpoint --phase awaiting-developer
+```
 
 ## Documentation
 
@@ -63,7 +94,7 @@ it.
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.27.0 onboard checkpoint --phase awaiting-developer
 ```
 
 ## Keep the agent working on a clone
@@ -76,32 +107,35 @@ fields, so this applies only to a subclass.
 
 Read the subclass before you plan. If `run` reads a field that the subclass sets, and
 the subclass does not override `clone()`, the plan adds an override. The override calls
-`super.clone()` and copies those fields. This is the only change that this route makes to
-the agent's code. Name it in the plan.
+`super.clone()` and copies those fields. Name it in the plan.
 
 ## Project data
 
 The agent receives `useAgentContext` entries on the AG-UI run input, in its `context`
-field. No page documents how a custom agent gives them to its model, because that is the
-agent's own code. If the requested work passes project data to the agent, and the
-agent's code does not already read `context`, run the unsupported route below. Otherwise,
-record the gap and continue.
+field. If the requested work passes project data to the agent, and the agent's code does
+not already read `context`, pass the entries on. In case 2, the adapter passes them to the
+agent's entry point, for example as part of its input. In case 1, the project's own
+`AbstractAgent` subclass passes them to its model, and a service behind `HttpAgent` that
+ignores `context` reads it in its own code. These changes and the `clone()` override are
+the only changes this route makes to the agent's code. Name each one in the plan.
 
-A2UI is not on this path. If the developer asks for it, say first that no page documents
-A2UI for a custom agent.
+If the developer asks for A2UI, https://docs.copilotkit.ai/generative-ui/a2ui.md has its
+steps.
 
 ## Record the selection
 
-The Copilot Runtime that this route adds runs on Node. The agent keeps running the way
-the project runs it now.
+The Copilot Runtime that this route adds runs on Node, and so does an adapter. The agent
+keeps running the way the project runs it now. An adapter for an agent in another language
+calls it through its HTTP route.
 
-Record the selected framework `custom-ag-ui` and the agent id. Record how the agent
+Record the selected framework `custom-ag-ui`, the case, and the agent id. Record how the agent
 connects: in the runtime process, or through `HttpAgent` and its URL. Record the
 credential variable names that the agent already uses, the `clone()` finding, and these
-URLs.
+URLs. For case 3, record the credential variable of the recorded vendor, such as
+`OPENAI_API_KEY`.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

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

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

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

@@ -1,8 +1,21 @@
 # Configure ADK
 
-Preserve an existing ADK model setup. Start with Google for a new agent. Offer another
-vendor only after an exact CopilotKit Markdown page names it. The page must name its
-credential variables and setup steps.
+First run `npx --prefer-offline --yes copilotkit@4.27.0 onboard setup-answers`. Its `vendor` is the
+vendor the framework step recorded, even after this conversation lost it, with
+`vendor.baseUrl` and `vendor.modelId` for an OpenAI-compatible provider.
+
+Preserve an existing ADK model setup. For a new agent, use the recorded vendor. Use Google
+only when the record and this conversation have no vendor. This release runs ADK on
+Google, OpenAI, or an OpenAI-compatible provider. For a new agent, if the developer names
+Anthropic, say that this release supports Google, OpenAI, or an OpenAI-compatible provider
+on ADK, that Anthropic comes in a later release, and offer the built-in CopilotKit agent
+if they need Anthropic now. An existing agent keeps its vendor and model. Take that
+vendor's package, class, and credential variable names from the framework's own
+documentation, and use a model id that the vendor serves to a new key today. For an
+OpenAI-compatible provider, keep `OPENAI_API_KEY`, use the model id that `setup/questions`
+recorded, and write the base URL that `setup/questions` recorded as `OPENAI_BASE_URL` in
+the app's env file. The key can stay in its own file. Where the framework does not read
+that variable, also pass it in code. Take every CopilotKit step from the pages below.
 
 Name the 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
@@ -30,7 +43,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

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

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

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

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

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

@@ -1,9 +1,25 @@
 # Configure LangGraph TypeScript
 
+First run `npx --prefer-offline --yes copilotkit@4.27.0 onboard setup-answers`. Its `vendor` is the
+vendor the framework step recorded, even after this conversation lost it, with
+`vendor.baseUrl` and `vendor.modelId` for an OpenAI-compatible provider.
+
 Preserve an existing LangGraph TypeScript model setup. For a new agent, use the vendor
-that the framework step recorded. If it recorded none, use OpenAI. Offer another vendor
-only after an exact CopilotKit Markdown page names it. The page must name its credential
-variables and setup steps.
+that the framework step recorded. Use OpenAI only when the record and this conversation
+have no vendor. This release offers a new agent on this framework OpenAI or an
+OpenAI-compatible provider only. For a new agent, if the developer names Anthropic or
+Google, say that this release supports OpenAI or an OpenAI-compatible provider on this
+framework, that Anthropic and Google come in a later release, and offer the built-in
+CopilotKit agent if they need Anthropic or Google now. An existing agent keeps its vendor
+and model. If it runs on Anthropic or Google, add one line to the plan: the page context
+that CopilotKit sends can fail with that vendor until a CopilotKit SDK release fixes it
+(PE-728). Take that vendor's package, class, and credential variable names from the
+framework's own documentation, and use a model id that the vendor serves to a new key
+today. For an OpenAI-compatible provider, keep `OPENAI_API_KEY`, use the model id that
+`setup/questions` recorded, and write the base URL that `setup/questions` recorded as
+`OPENAI_BASE_URL` in the app's env file. The key can stay in its own file. Where the
+framework does not read that variable, also pass it in code. Take every CopilotKit step
+from the pages below.
 
 Name the default model credential `OPENAI_API_KEY`.
 
@@ -18,11 +34,15 @@ Connect the Copilot Runtime with `LangGraphAgent` from `@copilotkit/runtime/lang
 on the LangSmith path, or `HttpAgent` from `@ag-ui/client` on the FastAPI path.
 `LangGraphHttpAgent` is deprecated. Do not use it.
 
-Record the selected framework, vendor, model, required credential variable names, and
-these URLs.
+A package script that starts a new LangGraph TypeScript agent runs
+`npx @langchain/langgraph-cli dev`. The JavaScript CLI installs its binary as `langgraphjs`.
+`langgraph` is the Python CLI, and a JavaScript project does not have it.
+
+Record the selected framework, vendor, model, required credential variable names, this
+start command, and these URLs.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/llamaindex.md

@@ -1,9 +1,24 @@
 # Configure LlamaIndex
 
+First run `npx --prefer-offline --yes copilotkit@4.27.0 onboard setup-answers`. Its `vendor` is the
+vendor the framework step recorded, even after this conversation lost it, with
+`vendor.baseUrl` and `vendor.modelId` for an OpenAI-compatible provider.
+
 Preserve an existing LlamaIndex model setup. For a new agent, use the vendor that the
-framework step recorded. If it recorded none, use OpenAI. Offer another vendor only after
-an exact CopilotKit Markdown page names it. The page must name its credential variables
-and setup steps.
+framework step recorded. Use OpenAI only when the record and this conversation have no
+vendor. This release offers a new agent on this framework OpenAI or an OpenAI-compatible
+provider only. For a new agent, if the developer names Anthropic or Google, say that this
+release supports OpenAI or an OpenAI-compatible provider on this framework, that Anthropic
+and Google come in a later release, and offer the built-in CopilotKit agent if they need
+Anthropic or Google now. An existing agent keeps its vendor and model. If it runs on
+Anthropic or Google, add one line to the plan: the page context that CopilotKit sends can
+fail with that vendor until a CopilotKit SDK release fixes it (PE-728). Take that vendor's
+package, class, and credential variable names from the framework's own documentation, and
+use a model id that the vendor serves to a new key today. For an OpenAI-compatible
+provider, keep `OPENAI_API_KEY`, use the model id that `setup/questions` recorded, and
+write the base URL that `setup/questions` recorded as `OPENAI_BASE_URL` in the app's env
+file. The key can stay in its own file. Where the framework does not read that variable,
+also pass it in code. Take every CopilotKit step from the pages below.
 
 Name the default model credential `OPENAI_API_KEY`.
 
@@ -27,15 +42,16 @@ A2UI is not on this path. If the developer asks for it, say first that its page
 LlamaIndex backend code but does not bundle its runtime setup, so it only works on top of
 the quickstart runtime it extends.
 
-The shared-state page is not an agent-app-context guide. Do not use it to invent a
-`useAgentContext` backend setup. If the requested work passes project data to the agent, run the
-unsupported route below. Otherwise, record the gap and continue.
+The agent receives `useAgentContext` entries on the AG-UI run input, in its `context`
+field, as https://docs.copilotkit.ai/agent-app-context.md shows. If the requested work
+passes project data to the agent, read `context` in the agent with this framework's own
+API, and pass it to the model. Name that code in the plan.
 
 Record the selected framework, vendor, model, required credential variable names, these
 URLs, the documented dependencies and adapter, and both documentation limits.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/mastra.md

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

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

@@ -1,7 +1,25 @@
 # Configure Microsoft Agent Framework for .NET
 
-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.
+First run `npx --prefer-offline --yes copilotkit@4.27.0 onboard setup-answers`. Its `vendor` is the
+vendor the framework step recorded, even after this conversation lost it, with
+`vendor.baseUrl` and `vendor.modelId` for an OpenAI-compatible provider.
+
+Preserve an existing Microsoft Agent Framework model setup. For a new agent, use the
+vendor that the framework step recorded. Use direct OpenAI only when the record and this
+conversation have no vendor, and name its credential `OPENAI_API_KEY`. This release offers
+a new agent on this framework OpenAI or an OpenAI-compatible provider only. For a new
+agent, if the developer names Anthropic or Google, say that this release supports OpenAI
+or an OpenAI-compatible provider on this framework, that Anthropic and Google come in a
+later release, and offer the built-in CopilotKit agent if they need Anthropic or Google
+now. An existing agent keeps its vendor and model. If it runs on Anthropic or Google, add
+one line to the plan: the page context that CopilotKit sends can fail with that vendor
+until a CopilotKit SDK release fixes it (PE-728). Take that vendor's package, class, and
+credential variable names from the framework's own documentation, and use a model id that
+the vendor serves to a new key today. For an OpenAI-compatible provider, keep
+`OPENAI_API_KEY`, use the model id that `setup/questions` recorded, and write the base URL
+that `setup/questions` recorded as `OPENAI_BASE_URL` in the app's env file. The key can
+stay in its own file. Where the framework does not read that variable, also pass it in
+code. Take every CopilotKit step from the pages below. Do not change an existing provider.
 
 .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
@@ -15,13 +33,13 @@ Run `dotnet --version` before you change the project. If it fails, no .NET SDK i
 shell's PATH. Do not change the project, and do not install the SDK yourself. Tell the
 developer to install the .NET SDK from https://dotnet.microsoft.com/download. Say that the
 coding agent's shell cannot see a new install until the developer restarts the coding
-agent. Give them `npx --prefer-offline --yes copilotkit@4.26.0 onboard start --run <onboarding_run_id>`
+agent. Give them `npx --prefer-offline --yes copilotkit@4.27.0 onboard start --run <onboarding_run_id>`
 to resume the run after the restart.
 
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.27.0 onboard checkpoint --phase awaiting-developer
 ```
 
 Then end your turn and wait for the developer.
@@ -49,7 +67,7 @@ Record the selected framework, provider, model, required credential variable nam
 these URLs.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

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

@@ -1,7 +1,26 @@
 # Configure MS Agent Harness for .NET
 
+First run `npx --prefer-offline --yes copilotkit@4.27.0 onboard setup-answers`. Its `vendor` is the
+vendor the framework step recorded, even after this conversation lost it, with
+`vendor.baseUrl` and `vendor.modelId` for an OpenAI-compatible provider.
+
 Preserve an existing MS Agent Harness model, provider, credential name, and host setup.
-Use direct OpenAI for a new setup. Name its credential `OPENAI_API_KEY`.
+For a new setup, use the vendor that the framework step recorded. Use direct OpenAI only
+when the record and this conversation have no vendor, and name its credential
+`OPENAI_API_KEY`. This release offers a new agent on this framework OpenAI or an
+OpenAI-compatible provider only. For a new agent, if the developer names Anthropic or
+Google, say that this release supports OpenAI or an OpenAI-compatible provider on this
+framework, that Anthropic and Google come in a later release, and offer the built-in
+CopilotKit agent if they need Anthropic or Google now. An existing agent keeps its vendor
+and model. If it runs on Anthropic or Google, add one line to the plan: the page context
+that CopilotKit sends can fail with that vendor until a CopilotKit SDK release fixes it
+(PE-728). Take that vendor's package, class, and credential variable names from the
+framework's own documentation, and use a model id that the vendor serves to a new key
+today. For an OpenAI-compatible provider, keep `OPENAI_API_KEY`, use the model id that
+`setup/questions` recorded, and write the base URL that `setup/questions` recorded as
+`OPENAI_BASE_URL` in the app's env file. The key can stay in its own file. Where the
+framework does not read that variable, also pass it in code. Take every CopilotKit step
+from the pages below.
 
 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
@@ -9,13 +28,13 @@ you change the project. If it fails, no .NET SDK is on this shell's PATH. Do not
 the project, and do not install the SDK yourself. Tell the developer to install the .NET
 SDK from https://dotnet.microsoft.com/download. Say that the coding agent's shell cannot
 see a new install until the developer restarts the coding agent. Give them
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard start --run <onboarding_run_id>` to resume the run
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard start --run <onboarding_run_id>` to resume the run
 after the restart.
 
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.27.0 onboard checkpoint --phase awaiting-developer
 ```
 
 Then end your turn and wait for the developer.
@@ -57,7 +76,7 @@ Record the selected framework, provider, model, required credential variable nam
 URLs, and the quickstart gap.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.27.0 onboard read unsupported/no-validated-path`.

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

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