copilotkit 4.8.3 → 4.8.4

package/onboarding/prompts/subagent/create-plan.md

@@ -1,14 +1,69 @@
 # Create the onboarding plan
 
 Use the selected framework, frontend, model, repository findings, and documentation URLs
-from the main coding agent. Fetch each selected URL. Do not use remembered CopilotKit
-instructions.
+from the main coding agent. Fetch every selected URL in one step rather than one after
+another. Do not use remembered CopilotKit instructions.
+
+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.
+
+Read only inside the project directory. Answer an API question from the documentation
+URLs you were given, not from another checkout on this machine.
 
 List the required credential variable names. Do not read or return credential values.
 Preserve each agent or frontend that already exists.
 
+Plan the runtime to consume the Intelligence credential. The runtime takes an
+`intelligence` option holding a client built from the project key. A runtime given a
+`runner` option instead is the SSE runtime. It never reads the key, threads are not
+durable, and the Inspector reads the project as locked. The two options cannot be
+combined. Take the constructor from the connect-your-runtime page. Where a framework
+quickstart shows a `runner` option instead, the connect-your-runtime page wins.
+
+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
+production requires instead. Do not stop onboarding to ask the developer for it.
+
+Check whether the existing agent performs unattended side effects, such as paging, sending
+notifications, writing to an external system, or creating tickets. If it does, the new
+conversational surface must not trigger them. Wrap only the reasoning steps, or require an
+explicit developer confirmation before the side effect can run. Name each side effect you
+found and state how the plan avoids it.
+
+If the value of the journey depends on data the project already holds, name that data,
+name where it lives, and name how it reaches the agent. Rendering a list in the DOM does
+not give the agent access to it. An agent wired without the page's data answers from
+entities it invents, and the answer looks correct. Take the frontend-context step from
+the selected documentation. Where no selected page documents it for this framework or
+frontend, record that as a documentation gap rather than guessing the API.
+
+Where that data exists, name the entities the proof compares against: the ids, names, or
+records the project holds and the answer has to reference. Where the outcome references
+no project data, say so in the plan, so that the proof asks for evidence this journey can
+produce.
+
 Create one plan for implementation, validation, and proof. Name each file or area that can
 change. Name the commands that can validate the result.
+Name the commands or user path that prove a real generative-UI round trip.
+
+Keep a production build out of the validation commands. A type check plus the real round
+trip is the proof, and the round trip runs in development mode. Name the production build
+as a follow-up for the developer instead. Never raise a bundle budget or relax a lint rule
+to make a build pass during onboarding.
+
+The type check runs against the project's own configuration. If the project has no
+type-check command, add one that uses the configuration the project already has.
+Do not add compiler strictness the project did not have. Nothing later in the run is
+allowed to weaken type safety, so a stricter gate named here is one the run cannot get
+back out of.
+
+Gather what you need in as few commands as possible. Combine independent reads into one
+command rather than running them one at a time. Split a command only when its result decides
+what you run next.
 
 Return the plan, the URLs that you read, and each documentation gap. Stop after you return
 the findings to the main coding agent.

package/onboarding/prompts/subagent/implement-and-validate.md

@@ -1,13 +1,48 @@
 # Implement and validate the approved plan
 
-Use only the approved plan and the selected documentation URLs. Fetch each URL before you
-change the project. Do not use remembered CopilotKit instructions.
+Use only the approved plan and the selected documentation URLs. Fetch every URL in one
+step, before you change the project, rather than one after another.
+Do not use remembered CopilotKit instructions.
+
+Add only the props, options, and imports that appear in the fetched documentation. A
+remembered API from an earlier CopilotKit version will fail type checking against this
+release, so do not decorate a documented example with anything it does not show.
+
+The documentation supplies the wiring. The project supplies the application. That rule
+governs props, options, and imports, and it stops there. A documentation example names a
+domain of its own to make itself readable. Build what the plan names, in the project's
+own domain, from the wiring the page shows. Do not carry the page's example domain into
+the project: not its agent name, not its tools, not its data.
 
 Preserve each agent or frontend that already exists. Add only the missing parts and the
-CopilotKit connection. Do not read, show, store, or return secret values.
+CopilotKit connection. Do not read, show, store, or return secret values. Do not read a
+file outside the project directory: not for a credential, and not for an API question the
+fetched documentation answers. A missing credential is the main coding agent's to ask
+for.
+
+When the documentation creates the frontend with the framework's own scaffolder,
+run that scaffolder rather than hand-authoring what it emits.
+Do not re-declare a compiler option it set. Every real project of that framework
+inherits those defaults, so a hand-written replacement measures a configuration no
+developer has. Where the plan needs configuration the scaffolder did not write,
+extend the scaffolder's file and set only what you add.
+
+Where the plan names data the project already holds, share that data with the agent
+through the context API the selected documentation names for this frontend. Then write the agent's instructions to
+refuse to answer about entities the shared context does not carry, and to name what is
+missing instead. An agent with no context and no refusal invents plausible entities, and
+no part of the run errors.
 
 Run the validation commands from the approved plan. Record the changed files, command
 results, and each error. Do not claim that the real user journey works in this phase.
 
+Report the runtime constructor you wrote. Name whether it passes `intelligence` or
+`runner`. A runtime built with `runner` is the SSE runtime and never reads the credential,
+whatever the browser shows.
+
+Gather what you need in as few commands as possible. Combine independent reads into one
+command rather than running them one at a time. Split a command only when its result decides
+what you run next.
+
 Return the implementation result and validation evidence to the main coding agent. Stop
 after you return the result.

package/onboarding/prompts/subagent/inspect-repository.md

@@ -2,13 +2,23 @@
 
 Inspect the repository without changing it. Find evidence for:
 
+- what the project is for, in the project's own words
 - any existing agent framework
 - any existing frontend
 - current CopilotKit packages and configuration
 - authentication boundaries
 - names of required credential variables, without reading their values
-- the commands or user path that can prove a real generative-UI round trip
+
+A project states what it is for in its `README.md`, in its package description, or in
+the prompt of an agent it already has. Quote that statement rather than rewriting it. An
+empty project carries it in the README alone, and that makes the README the whole of the
+evidence. State the purpose as unproved when the project never says.
+
+Gather what you need in as few commands as possible. Combine independent reads into one
+command rather than running them one at a time. Split a command only when its result decides
+what you run next.
 
 Return the file paths and a short finding for each item. State each absent or unproved item.
-Do not read, print, or return secret values. Do not run or return another
-onboarding command. Stop after returning the findings to the main coding agent.
+Do not read, print, or return secret values. Do not read a file outside the project
+directory. Do not run or return another onboarding command. Stop after returning the
+findings to the main coding agent.

package/onboarding/prompts/subagent/prove-round-trip.md

@@ -1,20 +1,114 @@
 # Prove the complete round trip
 
-Use the proof steps and documentation URLs from the approved plan. Fetch each selected URL
-before you start. Do not use remembered CopilotKit instructions.
+Use the proof steps and documentation URLs from the approved plan. Fetch every selected
+URL in one step before you start, rather than one after another.
+Do not use remembered CopilotKit instructions.
 
-Start the agent and the selected frontend. Send one real request through the frontend.
-Make sure that the request passes through CopilotKit and reaches the selected agent.
+Read the port the developer's agent already serves from this project's own
+configuration. Do not assume a default, and do not start a second copy of an agent this
+project is already running. Before you bind any new server, check that the port is free
+and pick another one if it is not. Record every port you used.
 
-Make sure that the frontend receives working generative UI from the agent. Record the input,
-visible result, relevant process status, and evidence locations. Do not return secret values.
+Start the agent and the selected frontend.
 
-After the round trip works, fetch the continued-development guide from the main coding agent.
+With both running, check the wiring in one command before you open a browser:
+`npx copilotkit@4.8.4 verify --json`. Add `--runtime-url` when the runtime is not at
+`http://localhost:3000/api/copilotkit`. Read the individual checks rather than the summary
+alone: a check reported `undetermined` did not run, and that is not a pass. Fix anything
+that is not a pass before the browser, because a browser failure stacked on broken wiring
+costs a round of debugging to reach an answer this command already gave.
+
+Treat `intelligence_consumed` as the check that matters most here. A journey that finishes
+with the Intelligence credential never read looks complete and proves nothing about the
+paid surface. `api_key_authenticates` passing beside it says the key is real and the
+runtime never used it.
+
+`intelligence_thread_routes` fails when the runtime reports a license but serves no
+thread routes, which means saved Threads cannot load in a browser. The usual cause is a
+handler mounted `mode: "single-route"`: remove that option so the handler serves its full
+route set, and mount it at a catch-all route. If instead that check is `undetermined`
+because the runtime reports no thread-endpoint state, the runtime predates the field.
+Record that and move on — there is nothing to repair.
+
+Then prove that the agent actually runs, which is the gate for this node:
+`npx copilotkit@4.8.4 verify --round-trip --json`. It sends one request through the
+runtime and reads the answer back from the thread, so it separates an agent that is
+configured from an agent that works. Use `--agent <id>` when the runtime declares more
+than one. If it reports `user-not-identified`, this project's `identifyUser` reads a
+session the CLI does not carry: pass what it reads with `--header "Name: value"` and run
+it again, because an auth-gated app refusing an unauthenticated caller is that app
+working. Do not continue until this passes, and never report a round trip proven without
+it.
+
+Then send one real request through the frontend. Make sure that the request passes through
+CopilotKit and reaches the selected agent.
+
+Before you trust the agent, confirm that the process answering is the one in this
+repository. `verify` reports which agents the runtime declares and has nothing to compare
+them against, and `--round-trip` proves an agent answers under the declared id without
+proving which deployment did, so this comparison is yours. A health endpoint that returns success proves only that something listens on
+that port. An agent from earlier work often still holds it, and a stale process answers
+as though it were the new one. Ask the running agent which graph or agent id it serves
+and compare that with the id declared in this project.
+
+If they do not match, find out whose process it is before you signal anything.
+`lsof -ti :<port> -sTCP:LISTEN` gives the process id, and `lsof -a -p <pid> -d cwd` gives
+the directory it runs in. Stop it only when that directory is inside this project, and
+stop its children before the parent so nothing survives by reparenting. A holder outside
+this project belongs to other work: leave it running, report it, and bind to another port.
+Never stop a process because its command line matches a name. One `pkill` pattern reaches
+every project on the machine and takes down work that has nothing to do with this run.
+Never continue against a process you cannot identify, and never report a round trip proven
+by one.
+
+Address a local agent by host name rather than by an IP literal. Some local agents bind
+IPv6 only, so an IPv4 literal fails against the correct port.
+
+Drive the real UI in a browser whenever your environment can, and make sure that the
+frontend receives working generative UI from the agent. Prefer this: it is the only step
+that covers realtime delivery to a browser, browser-origin CORS and CSP, the frontend
+provider being wired to this runtime, and a generative UI component actually rendering,
+and no command-line check reaches any of them.
+
+Use a browser MCP server already configured for the coding agent you are running as, the
+same way the CopilotKit documentation MCP server below is configured. Do not add a browser
+driver to this project: a devDependency and a browser download land in the diff and tax a
+repository that never asked for one. If nothing in your environment can drive a
+browser, skip this step rather than installing one, and never report a visual result you
+did not see.
+
+Report exactly one of `performed`, `skipped-no-browser-tool`, or `failed` for this step.
+
+Record the input, visible result, relevant process status, and evidence locations. Do not
+return secret values.
+
+Where the answer is meant to be about data the project holds, check it against that data.
+Read the entities the project holds -- the ids, names, or records the answer claims to
+describe -- and confirm the answer names those and no others. Record the entities you
+compared. Where the outcome of this journey references no project data, record that
+instead, and do not invent a comparison to pass this step.
+
+An answer that renders correctly over entities the project does not hold looks the same as
+a correct one in a browser, in a screenshot, and in a video, so this comparison is the only
+stage that separates them. An answer that names an entity the project does not hold is a
+failed proof, not a passing one. Find which of these it is before you change anything: the
+project's data never reaches the agent, the agent receives it and its instructions ignore
+it, the page loads its data after the context was registered, or the run wired a different
+source than the page renders. Fix that cause, then prove again.
+
+Install the continued-development tools while you drive the round trip, not after it. The
+two are independent, so running them one after the other adds minutes to the journey for
+no reason. Fetch the continued-development guide from the main coding agent at the same
+time as the proof documentation.
 Use it to install the project-scoped CopilotKit Skills.
 Use it to configure the CopilotKit documentation MCP server for the current coding agent.
 
 Record the installed Skills and the configured MCP server. If either tool step fails, return
 the exact documentation gap or error.
 
-Return the proof or the exact failed step to the main coding agent. Stop after you return the
-result.
+Gather what you need in as few commands as possible. Combine independent reads into one
+command rather than running them one at a time. Split a command only when its result decides
+what you run next.
+
+Return the proof or the exact failed step to the main coding agent, together with the
+visual-check outcome. Stop after you return the result.

package/onboarding/prompts/unsupported/no-validated-path.md

@@ -7,11 +7,16 @@ Explain the exact step that failed. State whether authentication, project select
 credentials, the journey, a documentation URL, implementation, validation, or proof caused
 the stop. Do not invent an adapter or claim that an untested path works.
 
-If useful, send one short report without secrets, source code, logs, or command output:
+If useful, send one short report:
 
 ```text
-npx copilotkit@4.8.3 onboard feedback
+npx copilotkit@4.8.4 onboard feedback
 ```
 
-Write the feedback message to the command's standard input. Stop after the explanation or
-optional feedback. This unsupported outcome does not complete onboarding.
+Write the feedback message to the command's standard input, in at most four lines.
+Send no secrets, source code, logs, or command output. The command refuses a report
+that carries any of those, prints the reason, and exits zero. A refused report is not
+a failed step. Reword it and send it again, or stop without a report. The command
+prints what it sent. This is the channel for a stop. Report friction only from a run that
+finished, never from here. Stop after the explanation or optional feedback. This
+unsupported outcome does not complete onboarding.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "copilotkit",
-  "version": "4.8.3",
+  "version": "4.8.4",
   "type": "module",
   "repository": {
     "type": "git",

package/release/release-tool.js

@@ -91,6 +91,9 @@ var STARTER_SOURCE_CATALOG = {
   adk: copilotKitStarter("examples/integrations/adk"),
   "adk-angular": copilotKitStarter("examples/integrations/adk-angular"),
   "aws-strands-py": copilotKitStarter("examples/integrations/strands-python"),
+  "aws-strands-ts": copilotKitStarter(
+    "examples/integrations/strands-typescript"
+  ),
   a2a: copilotKitStarter("examples/integrations/a2a-middleware"),
   "microsoft-agent-framework-dotnet": copilotKitStarter(
     "examples/integrations/ms-agent-framework-dotnet"
@@ -13900,6 +13903,15 @@ config(en_default());
 // apps/cli/src/release/release-schemas.ts
 var import_starter_source_policy2 = __toESM(require_starter_source_policy(), 1);
 var CLI_BUILD_INFO_FILENAME = "cli-build-info.json";
+var PROVENANCE_CHANNELS = [
+  "production",
+  "dev",
+  "staging",
+  "preview",
+  "push",
+  "pull-request",
+  "validation"
+];
 var canonicalCommitSchema = external_exports.string().regex(/^[0-9a-f]{40}$/);
 var instantSchema = external_exports.iso.datetime({ offset: true });
 var packageVersionSchema = external_exports.string().regex(/^\d+\.\d+\.\d+(?:-[0-9A-Za-z.-]+)?(?:\+[0-9A-Za-z.-]+)?$/);
@@ -13921,7 +13933,7 @@ var buildInfoSchema = external_exports.object({
     submittedInput: external_exports.string().min(1),
     commit: canonicalCommitSchema
   }).strict(),
-  channel: external_exports.enum(["production", "dev", "staging", "preview", "validation"]),
+  channel: external_exports.enum(PROVENANCE_CHANNELS),
   triggeringActor: external_exports.string().min(1),
   workflow: external_exports.object({
     runId: external_exports.string().min(1),
@@ -14683,7 +14695,7 @@ import * as path4 from "node:path";
 
 // apps/cli/src/config.ts
 function getTemplateRef() {
-  return true ? "e0a2f00cca326c76739217e8ca40902e609539a4" : "main";
+  return true ? "47c5510b4909f6728288ecf28d7b14cd14922d33" : "main";
 }
 
 // apps/cli/src/services/agentcore-config.ts
@@ -14860,6 +14872,12 @@ var TELEMETRY_ERROR_CODES = {
   USER_ABORTED: "USER_ABORTED",
   NON_INTERACTIVE: "NON_INTERACTIVE",
   FILESYSTEM_WRITE_FAILED: "FILESYSTEM_WRITE_FAILED",
+  /**
+   * `project select --project` named a project the active organization does
+   * not have. Distinct from a generic validation failure so the funnel can
+   * tell "the caller guessed a slug" from a malformed request.
+   */
+  PROJECT_NOT_FOUND: "PROJECT_NOT_FOUND",
   CLI_PRODUCT_BINARY_TOO_LARGE: "CLI_PRODUCT_BINARY_TOO_LARGE",
   LEARNING_CONTAINER_ID_INVALID: "LEARNING_CONTAINER_ID_INVALID",
   LEARNING_PROJECT_ID_INVALID: "LEARNING_PROJECT_ID_INVALID",
@@ -14891,6 +14909,7 @@ var FRAMEWORK_EMOJI = {
   "adk-angular": "\u{1F53A}",
   a2a: "\u{1F916}",
   "aws-strands-py": "\u{1F9EC}",
+  "aws-strands-ts": "\u{1F9EC}",
   "microsoft-agent-framework-dotnet": "\u{1F7E6}",
   "microsoft-agent-framework-py": "\u{1F7E6}",
   "mcp-apps": "\u{1F9E9}",
@@ -14925,6 +14944,10 @@ var FRAMEWORK_CHOICES = [
     label: `${FRAMEWORK_EMOJI["aws-strands-py"]} AWS Strands (Python)`,
     value: "aws-strands-py"
   },
+  {
+    label: `${FRAMEWORK_EMOJI["aws-strands-ts"]} AWS Strands (TypeScript)`,
+    value: "aws-strands-ts"
+  },
   { label: `${FRAMEWORK_EMOJI.adk} ADK`, value: "adk" },
   {
     label: `${FRAMEWORK_EMOJI["adk-angular"]} Angular + ADK`,
@@ -15099,6 +15122,11 @@ var FRAMEWORK_TEMPLATES = {
     TEMPLATE_REPOS["aws-strands-py"],
     `\u{1FA81}\u{1F91D}${FRAMEWORK_EMOJI["aws-strands-py"]}`
   ),
+  "aws-strands-ts": standardTemplate(
+    "aws-strands-ts",
+    TEMPLATE_REPOS["aws-strands-ts"],
+    `\u{1FA81}\u{1F91D}${FRAMEWORK_EMOJI["aws-strands-ts"]}`
+  ),
   a2a: {
     ...standardTemplate(
       "a2a",
@@ -15438,7 +15466,7 @@ async function scaffoldStarterForSmoke(input, scaffold = scaffoldProject) {
   }
 }
 async function executeStarterSmokeChild(command) {
-  return new Promise((resolve3, reject) => {
+  return new Promise((resolve4, reject) => {
     execFile(
       command.executable,
       [...command.args],
@@ -15452,7 +15480,7 @@ async function executeStarterSmokeChild(command) {
           reject(error48);
           return;
         }
-        resolve3(stdout);
+        resolve4(stdout);
       }
     );
   });

package/onboarding/prompts/framework/ag2.md

@@ -1,22 +0,0 @@
-# Configure AG2
-
-If the repository uses AG2, preserve it. Do not recommend it for a new agent. Its starter
-tracks third-party code from a moving branch. Preserve its model vendor and model setup.
-
-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
-- https://docs.copilotkit.ai/ag2/inspector.md
-- https://docs.copilotkit.ai/ag2/generative-ui/a2ui/fixed-schema.md
-
-Fetch all three pages. Record the selected framework, vendor, model, required credential
-variable names, and these URLs. Do not use remembered CopilotKit instructions.
-
-If the pages support the selection, run
-`npx copilotkit@4.8.3 onboard read frontend/plan`.
-
-If a page does not load or support the selection, run
-`npx copilotkit@4.8.3 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/agno.md

@@ -1,23 +0,0 @@
-# Configure Agno
-
-Preserve an existing Agno model setup. Start with OpenAI for a new agent. Offer another
-vendor only after the selected CopilotKit Markdown pages document it. The pages must name
-its credential variables and setup steps.
-
-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
-- https://docs.copilotkit.ai/agno/inspector.md
-- https://docs.copilotkit.ai/agno/generative-ui/a2ui/fixed-schema.md
-
-Fetch all three pages. Record the selected framework, vendor, model, required credential
-variable names, and these URLs. Do not use remembered CopilotKit instructions.
-
-If the pages support the selection, run
-`npx copilotkit@4.8.3 onboard read frontend/plan`.
-
-If a page does not load or support the selection, run
-`npx copilotkit@4.8.3 onboard read unsupported/no-validated-path`.

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

@@ -1,21 +0,0 @@
-# Configure CopilotKit built-in agent
-
-Preserve an existing built-in agent and its model setup. For a new agent, follow the setup page. Ask the developer to choose the documented model vendor and model. Record the required credential variable names.
-
-Keep `INTELLIGENCE_API_KEY` separate from model-vendor credentials. Do not read, show,
-store, or request a secret value.
-
-## Documentation
-
-- https://docs.copilotkit.ai/quickstart.md
-- https://docs.copilotkit.ai/inspector.md
-- https://docs.copilotkit.ai/generative-ui/a2ui/fixed-schema.md
-
-Fetch all three pages. Record the selected framework, vendor, model, required credential
-variable names, and these URLs. Do not use remembered CopilotKit instructions.
-
-If the pages support the selection, run
-`npx copilotkit@4.8.3 onboard read frontend/plan`.
-
-If a page does not load or support the selection, run
-`npx copilotkit@4.8.3 onboard read unsupported/no-validated-path`.

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

@@ -1,21 +0,0 @@
-# Configure Claude Agent SDK Python
-
-Preserve an existing Claude Agent SDK Python setup. This onboarding path supports Anthropic only. Ask the developer to choose the Anthropic model. Record the required credential variable names.
-
-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
-- https://docs.copilotkit.ai/claude-sdk-python/inspector.md
-- https://docs.copilotkit.ai/claude-sdk-python/generative-ui/a2ui/fixed-schema.md
-
-Fetch all three pages. Record the selected framework, vendor, model, required credential
-variable names, and these URLs. Do not use remembered CopilotKit instructions.
-
-If the pages support the selection, run
-`npx copilotkit@4.8.3 onboard read frontend/plan`.
-
-If a page does not load or support the selection, run
-`npx copilotkit@4.8.3 onboard read unsupported/no-validated-path`.

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

@@ -1,21 +0,0 @@
-# Configure Claude Agent SDK TypeScript
-
-Preserve an existing Claude Agent SDK TypeScript setup. This onboarding path supports Anthropic only. Ask the developer to choose the Anthropic model. Record the required credential variable names.
-
-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
-- https://docs.copilotkit.ai/claude-sdk-typescript/inspector.md
-- https://docs.copilotkit.ai/claude-sdk-typescript/generative-ui/a2ui/fixed-schema.md
-
-Fetch all three pages. Record the selected framework, vendor, model, required credential
-variable names, and these URLs. Do not use remembered CopilotKit instructions.
-
-If the pages support the selection, run
-`npx copilotkit@4.8.3 onboard read frontend/plan`.
-
-If a page does not load or support the selection, run
-`npx copilotkit@4.8.3 onboard read unsupported/no-validated-path`.

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

@@ -1,22 +0,0 @@
-# Configure CrewAI Flows
-
-If the repository uses a CrewAI Enterprise agent, preserve CrewAI Flows. Do not recommend
-it for a new agent. Preserve its remote model setup. Record its credential variable names.
-
-Keep `INTELLIGENCE_API_KEY` separate from model-vendor credentials. Do not read, show,
-store, or request a secret value.
-
-## Documentation
-
-- https://docs.copilotkit.ai/crewai-crews/quickstart.md
-- https://docs.copilotkit.ai/crewai-crews/inspector.md
-- https://docs.copilotkit.ai/crewai-crews/generative-ui/a2ui/fixed-schema.md
-
-Fetch all three pages. Record the selected framework, vendor, model, required credential
-variable names, and these URLs. Do not use remembered CopilotKit instructions.
-
-If the pages support the selection, run
-`npx copilotkit@4.8.3 onboard read frontend/plan`.
-
-If a page does not load or support the selection, run
-`npx copilotkit@4.8.3 onboard read unsupported/no-validated-path`.

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

@@ -1,21 +0,0 @@
-# Configure Deep Agents
-
-Preserve an existing Deep Agents setup. Ask the developer to confirm its model vendor and model. Use the documented default for a new setup. Record the required credential variable names.
-
-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
-- https://docs.copilotkit.ai/deepagents/inspector.md
-- https://docs.copilotkit.ai/deepagents/generative-ui/a2ui/fixed-schema.md
-
-Fetch all three pages. Record the selected framework, vendor, model, required credential
-variable names, and these URLs. Do not use remembered CopilotKit instructions.
-
-If the pages support the selection, run
-`npx copilotkit@4.8.3 onboard read frontend/plan`.
-
-If a page does not load or support the selection, run
-`npx copilotkit@4.8.3 onboard read unsupported/no-validated-path`.

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

@@ -1,23 +0,0 @@
-# Configure LangGraph FastAPI
-
-Preserve an existing LangGraph FastAPI model setup. Start with OpenAI 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.
-
-Keep `INTELLIGENCE_API_KEY` separate from model-vendor credentials. Do not read, show,
-store, or request a secret value.
-
-## Documentation
-
-- https://docs.copilotkit.ai/langgraph-fastapi/quickstart.md
-- https://docs.copilotkit.ai/langgraph-fastapi/inspector.md
-- https://docs.copilotkit.ai/langgraph-fastapi/generative-ui/a2ui/fixed-schema.md
-
-Fetch all three pages. Record the selected framework, vendor, model, required credential
-variable names, and these URLs. Do not use remembered CopilotKit instructions.
-
-If the pages support the selection, run
-`npx copilotkit@4.8.3 onboard read frontend/plan`.
-
-If a page does not load or support the selection, run
-`npx copilotkit@4.8.3 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/llamaindex.md

@@ -1,23 +0,0 @@
-# Configure LlamaIndex
-
-Preserve an existing LlamaIndex model setup. Start with OpenAI for a new agent. Offer
-another vendor only after the selected CopilotKit Markdown pages document it. The pages must
-name its credential variables and setup steps.
-
-Keep `INTELLIGENCE_API_KEY` separate from model-vendor credentials. Do not read, show,
-store, or request a secret value.
-
-## Documentation
-
-- https://docs.copilotkit.ai/llamaindex/quickstart.md
-- https://docs.copilotkit.ai/llamaindex/inspector.md
-- https://docs.copilotkit.ai/llamaindex/generative-ui/a2ui/fixed-schema.md
-
-Fetch all three pages. Record the selected framework, vendor, model, required credential
-variable names, and these URLs. Do not use remembered CopilotKit instructions.
-
-If the pages support the selection, run
-`npx copilotkit@4.8.3 onboard read frontend/plan`.
-
-If a page does not load or support the selection, run
-`npx copilotkit@4.8.3 onboard read unsupported/no-validated-path`.

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

@@ -1,22 +0,0 @@
-# Configure Microsoft Agent Framework Harness .NET
-
-If the repository uses this framework, preserve it. Preserve its model vendor and model
-setup. Record the required credential variable names from the selected CopilotKit pages.
-
-Keep `INTELLIGENCE_API_KEY` separate from model-vendor credentials. Do not read, show,
-store, or request a secret value.
-
-## Documentation
-
-- https://docs.copilotkit.ai/ms-agent-harness-dotnet/quickstart.md
-- https://docs.copilotkit.ai/ms-agent-harness-dotnet/inspector.md
-- https://docs.copilotkit.ai/ms-agent-harness-dotnet/generative-ui/a2ui/fixed-schema.md
-
-Fetch all three pages. Record the selected framework, vendor, model, required credential
-variable names, and these URLs. Do not use remembered CopilotKit instructions.
-
-If the pages support the selection, run
-`npx copilotkit@4.8.3 onboard read frontend/plan`.
-
-If a page does not load or support the selection, run
-`npx copilotkit@4.8.3 onboard read unsupported/no-validated-path`.