copilotkit 4.26.0 → 4.28.0

package/onboarding/prompts/feature/rich-threads/start.md

@@ -9,7 +9,7 @@ implementation, and proof to separate subagents within the target project.
 Run this before anything else in this prompt:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
+npx --prefer-offline --yes copilotkit@4.28.0 onboard identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
 ```
 
 Report your product slug, such as `codex` or `claude-code`. The command needs no sign-in,
@@ -38,13 +38,13 @@ carry on. Keep a read-only assignment read-only. If no subagent works at all, re
 once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase delegation-unavailable
 ```
 
 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.28.0 onboard checkpoint --phase awaiting-developer
 ```
 
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
@@ -54,7 +54,7 @@ If you stop this run, send one short report before you stop. The friction comman
 the telemetry setting the developer already chose, so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.28.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -76,20 +76,20 @@ the current frontend-to-runtime-to-agent round trip and inspect `/info`.
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase research-returned
 ```
 
 If the inspection did not prove the baseline this intent extends, stop here without
 changing files:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/stop
 ```
 
 When the inspection proved what this intent needs, read the next prompt now, in this turn:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard read feature/rich-threads/plan
+npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/rich-threads/plan
 ```
 
 That prompt holds the plan, the developer's approval, and the paths the plan changes.

package/onboarding/prompts/feature/stop.md

@@ -20,7 +20,7 @@ a `start` with no `--run` reprints the id this stopped run already holds, and on
 covering both reads as one run that did two different things.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard start --run <new-12-character-id>
+npx --prefer-offline --yes copilotkit@4.28.0 onboard start --run <new-12-character-id>
 ```
 
 Do not read a generic onboarding node from this run. A feature run and a generic run are
@@ -48,13 +48,13 @@ put to them, stop here and send the report below.
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer
 ```
 
 If they approve it, make that one fix and nothing else. Then come back into this run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard resume --message "<approval>"
+npx --prefer-offline --yes copilotkit@4.28.0 onboard resume --message "<approval>"
 ```
 
 Put the developer's approval in `--message`, in one or two sentences: the fix they
@@ -75,7 +75,7 @@ Send one short report. The friction command follows the telemetry setting the de
 already chose, so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.28.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.

package/onboarding/prompts/feature/voice/implement.md

@@ -20,7 +20,7 @@ That result is a question for the developer. Name the file and why the work need
 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.28.0 onboard checkpoint --phase awaiting-developer
 ```
 
 Then end your turn and wait for the developer's answer. If they allow it, spawn a fresh
@@ -30,16 +30,16 @@ cannot ask, or the developer declines, take the feature stop route below.
 If the CLI prints `## Stop: this run deleted or moved the developer's work` instead of
 a step, show the developer the list it printed, and run what they choose:
 the `onboard restore` command the tripwire stop prints, which names each deleted file, or
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard tripwire --continue`. Then read the step again.
+`npx --prefer-offline --yes copilotkit@4.28.0 onboard tripwire --continue`. Then read the step again.
 
 To route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/stop
 ```
 
 If validation cannot pass, or this intent needs a prerequisite the app does not have, use
 the feature stop route above without further changes.
 
 Otherwise run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read feature/voice/proof`.
+`npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/voice/proof`.

package/onboarding/prompts/feature/voice/plan.md

@@ -12,7 +12,7 @@ The approval is a wait for the developer. Before you end your turn to wait, repo
 pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer
 ```
 
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
@@ -42,7 +42,7 @@ the repository proves its variable name is configured. Otherwise, explain the se
 take the feature stop route rather than writing a placeholder:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/stop
 ```
 
 Show a small plan for the documented transcription service, the existing composer, focused
@@ -51,7 +51,7 @@ tests, and a microphone/canned-transcript proof. Ask for approval as its own que
 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-plan-approval
+npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-plan-approval
 ```
 
 Ask the developer before you edit a file that has uncommitted changes. List those files in
@@ -59,4 +59,4 @@ the plan under `Uncommitted files`, each with one sentence explaining why, or wr
 `git status` names them. The CLI records no consent: the approved plan is the record. The
 plan must not delete, move, or rename one of those files.
 
-Then run `npx --prefer-offline --yes copilotkit@4.26.0 onboard read feature/voice/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/voice/implement`.

package/onboarding/prompts/feature/voice/proof.md

@@ -19,7 +19,7 @@ That result is a question for the developer. Name the file and why the fix needs
 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.28.0 onboard checkpoint --phase awaiting-developer
 ```
 
 Then end your turn and wait for the developer's answer. If they allow it, spawn a fresh
@@ -29,13 +29,13 @@ or the developer declines, take the feature stop route below.
 If the CLI prints `## Stop: this run deleted or moved the developer's work` instead of
 a step, show the developer the list it printed, and run what they choose:
 the `onboard restore` command the tripwire stop prints, which names each deleted file, or
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard tripwire --continue`. Then read the step again.
+`npx --prefer-offline --yes copilotkit@4.28.0 onboard tripwire --continue`. Then read the step again.
 
 Report the outcome of each attempt as it ends, before any repair. The command counts the
 attempts and the repairs:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.28.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Use `passed` only for proved voice input, `failed` for an attempted proof that failed, and
@@ -44,9 +44,9 @@ Use `passed` only for proved voice input, `failed` for an attempted proof that f
 To route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/stop
 ```
 
 When the proof is recorded, run
-`npx --prefer-offline --yes copilotkit@4.26.0 onboard read feature/complete` with the actual surface
+`npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/complete` with the actual surface
 outcome.

package/onboarding/prompts/feature/voice/start.md

@@ -8,7 +8,7 @@ read-only, implementation, and proof subagents, each restricted to the target pr
 Run this before anything else in this prompt:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
+npx --prefer-offline --yes copilotkit@4.28.0 onboard identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
 ```
 
 Report your product slug, such as `codex` or `claude-code`. The command needs no sign-in,
@@ -37,13 +37,13 @@ carry on. Keep a read-only assignment read-only. If no subagent works at all, re
 once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase delegation-unavailable
 ```
 
 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.28.0 onboard checkpoint --phase awaiting-developer
 ```
 
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
@@ -53,7 +53,7 @@ If you stop this run, send one short report before you stop. The friction comman
 the telemetry setting the developer already chose, so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.28.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -70,26 +70,28 @@ before a subagent or a project process runs.
 Before edits, inspect the runtime route, CopilotKit provider/chat composer, current agent,
 existing provider credential variable names (presence only), package versions, browser
 permissions approach, and test/dev commands. Prove the existing OSS baseline with `/info`,
-`npx --prefer-offline --yes copilotkit@4.26.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+`npx --prefer-offline --yes copilotkit@4.28.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
 and a real UI request when a browser is available.
+The `verify` report names the runtime URL it probed. If the dev server serves the
+runtime at another URL, add `--runtime-url <url>`.
 
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase research-returned
 ```
 
 If the inspection did not prove the baseline this intent extends, stop here without
 changing files:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/stop
 ```
 
 When the inspection proved what this intent needs, read the next prompt now, in this turn:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.26.0 onboard read feature/voice/plan
+npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/voice/plan
 ```
 
 That prompt holds the plan, the developer's approval, and the paths the plan changes.

package/onboarding/prompts/framework/ag2.md

@@ -1,9 +1,24 @@
 # Configure AG2
 
+First run `npx --prefer-offline --yes copilotkit@4.28.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 AG2 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.
+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`.
 
@@ -32,7 +47,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, and the A2UI documentation 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.28.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.28.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/agno.md

@@ -1,9 +1,24 @@
 # Configure Agno
 
+First run `npx --prefer-offline --yes copilotkit@4.28.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 Agno 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.
+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`.
 
@@ -23,19 +38,20 @@ new agent. For a new agent, install the documented Python dependencies
 `@ag-ui/agno` targets `/agui`. Do not replace that adapter with a generic agent or change
 the endpoint without repository evidence.
 
-The agent-readonly page does not bundle its Agno backend context setup. Do not invent it.
-If the requested work passes project data to the agent and the project does not already have that
-setup, run the unsupported route below. Otherwise, record the gap and continue.
+The agent receives `useAgentContext` entries on the AG-UI run input, in its `context`
+field, as https://docs.copilotkit.ai/agent-app-context.md shows. If the requested work
+passes project data to the agent, read `context` in the agent with this framework's own
+API, and pass it to the model. Name that code in the plan.
 
 A2UI is not on this path. If the developer asks for it, say first that its page has no Agno
 backend schema-loading, render-operations, or runtime setup snippet, so there is nothing to
 follow for the backend half.
 
 Record the selected framework, vendor, model, required credential variable names, these
-URLs, the documented dependencies and adapter, and the context documentation gap.
+URLs, the documented dependencies and adapter, 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.28.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.28.0 onboard read unsupported/no-validated-path`.

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

@@ -1,13 +1,28 @@
 # Configure the built-in CopilotKit agent
 
+First run `npx --prefer-offline --yes copilotkit@4.28.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 built-in agent 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. OpenAI, an OpenAI-compatible provider, Anthropic, and Google work. 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, name it
 `ANTHROPIC_API_KEY`. For Google, name it `GOOGLE_API_KEY`. Take the model id for the
-chosen vendor, in the `provider:model` form, from the model selection page.
+chosen vendor, in the `provider:model` form, from the model selection page. For a new
+agent, write that id to the app's env file as `COPILOTKIT_AGENT_MODEL`, and pass
+`process.env.COPILOTKIT_AGENT_MODEL` as the `BuiltInAgent` `model`, with the same id as
+the fallback when the variable is unset. The credential step then checks the app's own
+model. For a model id that holds a `/`, such as an OpenRouter id, write the
+`provider/model` form: `openai/meta-llama/llama-3.3-70b`. The runtime reads the first `/`
+as the separator, so the `provider:` form breaks that id.
 
 The built-in agent runs in the CopilotKit Runtime process.
 Do not create or start a separate agent server.
@@ -32,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.28.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.28.0 onboard read unsupported/no-validated-path`.

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

@@ -1,8 +1,14 @@
 # Configure Claude Agent SDK for Python
 
-Preserve an existing Claude Agent SDK model setup. Start with Anthropic 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.28.0 onboard setup-answers`. Its `vendor` is the
+vendor the framework step recorded, even after this conversation lost it.
+
+Preserve an existing Claude Agent SDK model setup. The Claude Agent SDK runs only
+Anthropic: the starter logs and ignores any other provider, and then runs Anthropic with no
+key. Offer no other vendor. For a new agent, use Anthropic when the record holds it, and
+only when the record and this conversation have no vendor. If the record holds another
+vendor, use Anthropic and name that change in the plan. Take every CopilotKit step from the
+pages below.
 
 Name the model credential `ANTHROPIC_API_KEY`. The documented model variable is
 `ANTHROPIC_MODEL`.
@@ -34,7 +40,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.28.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.28.0 onboard read unsupported/no-validated-path`.

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

@@ -1,8 +1,14 @@
 # Configure Claude Agent SDK for TypeScript
 
-Preserve an existing Claude Agent SDK model setup. Start with Anthropic 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.28.0 onboard setup-answers`. Its `vendor` is the
+vendor the framework step recorded, even after this conversation lost it.
+
+Preserve an existing Claude Agent SDK model setup. The Claude Agent SDK runs only
+Anthropic: the starter logs and ignores any other provider, and then runs Anthropic with no
+key. Offer no other vendor. For a new agent, use Anthropic when the record holds it, and
+only when the record and this conversation have no vendor. If the record holds another
+vendor, use Anthropic and name that change in the plan. Take every CopilotKit step from the
+pages below.
 
 Name the model credential `ANTHROPIC_API_KEY`. The documented model variable is
 `CLAUDE_MODEL`.
@@ -31,13 +37,14 @@ The adapter appends AG-UI `input.context` entries to the Claude system prompt. P
 backend path with the frontend hook from the reference page. Treat this as read-only app
 context. It does not provide an agent-to-frontend write-back path. Inspect the installed,
 pinned adapter source before using this path. If the package no longer handles
-`input.context`, run the unsupported route below.
+`input.context`, append those entries to the system prompt in the agent code, and name
+that change in the plan.
 
 Record the selected framework, vendor, model, required credential variable names, these
 URLs, and the context limit.
 
 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.28.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.28.0 onboard read unsupported/no-validated-path`.

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

@@ -1,5 +1,8 @@
 # Configure CrewAI Flows
 
+First run `npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers`. When it holds a `vendor`,
+the developer already chose it: keep it, and do not ask the vendor question below.
+
 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. Do not choose a
 vendor or credential name for the developer.
@@ -11,23 +14,34 @@ starter, tell the developer that the starter decides the vendor. If the frontend
 sends you to its Documentation section instead, ask the vendor question below at that
 point, before the plan.
 
+This release offers a new agent on CrewAI Flows OpenAI or an OpenAI-compatible provider
+only. When the run chooses the vendor, 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).
+
 When the repository shows a provider, keep it and ask nothing further about it. When
 neither the repository nor these pages show one, the developer decides, so ask. Ask one
-short question: which model vendor the CrewAI Flow will call. Say that the CopilotKit
-CrewAI pages name no vendor, so this release makes no recommendation here and will not
-pick one. If the developer names a vendor and no variable name, propose the variable name
-that vendor's own client reads and ask them to confirm it. A proposal the developer
-confirms is theirs. Ask for a variable name, never the value it holds. Do not combine this
-with a frontend, project, or plan-approval question.
+short question: OpenAI or an OpenAI-compatible provider, and for the latter its base URL
+and model id. Say that the CopilotKit CrewAI pages name no vendor, so this release makes no
+recommendation here. If the developer names a vendor and no variable name, propose the
+variable name that vendor's own client reads and ask them to confirm it. A proposal the
+developer confirms is theirs. Ask for a variable name, never the value it holds. Do not
+combine this with a frontend, project, or plan approval question.
 
 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.28.0 onboard checkpoint --phase awaiting-developer
 ```
 
 When the developer answers, record the answer as the project-defined provider, model, and
-credential variable name, and continue.
+credential variable name. Record the vendor in the CLI with
+`npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers --vendor <vendor> --vendor-choice developer`,
+with `openai` or `openai-compatible`, and `--base-url <url> --model-id <id>` for the
+latter. Then continue.
 
 A vendor nobody has chosen yet is not a missing supported path. This release supports
 CrewAI Flows. Do not run the unsupported route below because the project defines no
@@ -70,7 +84,7 @@ Record the selected framework, project-defined provider and model, the credentia
 variable names the repository proves or the developer named, these URLs, and the adapter.
 
 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.28.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.28.0 onboard read unsupported/no-validated-path`.