copilotkit 4.10.1 → 4.11.0

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

@@ -135,7 +135,7 @@ IPv6 only, so an IPv4 literal fails against the correct port.
 ## Step 4 -- Check the wiring
 
 With both running, check the wiring in one command before you open a browser:
-`npx --yes copilotkit@4.10.1 verify --json`. It reads the port from this project, so a
+`npx --yes copilotkit@4.11.0 verify --json`. It reads the port from this project, so a
 non-default port needs no flag. The payload reports `runtimeUrl` and `runtimeUrlSource`. A
 `runtimeUrlSource` of `default` means nothing in the project named a port, so pass
 `--runtime-url` with the URL from step 1 in that case. Read the individual checks rather than
@@ -150,7 +150,7 @@ used the Intelligence credential. `api_key_authenticates` proves only that the k
 will not read. `verify` searches upward for the credential and a framework's env loader
 does not, so a key at the repository root is invisible to an app in a subdirectory. The
 check names the file to write instead. Write the key there, or run
-`npx --yes copilotkit@4.10.1 project select` from the app directory. Do not link,
+`npx --yes copilotkit@4.11.0 project select` from the app directory. Do not link,
 copy, or symlink the file to work around it, and do not treat the credential as missing:
 the check above already reported that it exists.
 
@@ -168,7 +168,7 @@ named no port the CLI can read: keep step 2's URL, and rewrite its host as `loca
 before you use it.
 
 Then run the command once more with the URL you are about to open:
-`npx --yes copilotkit@4.10.1 verify --frontend-url <that url> --json`. The
+`npx --yes copilotkit@4.11.0 verify --frontend-url <that url> --json`. The
 `frontend_assets_served` check asks that server for its page and for one of the page's own
 assets, on that exact host. A `fail` there means the dev server refuses its own static
 assets on the host you were about to use, and the check names the URL to use instead. This
@@ -176,7 +176,7 @@ is the cheapest step that can save the most expensive one, so run it before the
 
 ## Step 5 -- Prove that the agent runs
 
-Run `npx --yes copilotkit@4.10.1 verify --round-trip --json`. It sends one request through
+Run `npx --yes copilotkit@4.11.0 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
@@ -189,7 +189,7 @@ Where this run settled a Learning Container, add the flag to the call above rath
 running a second round trip:
 
 ```text
-npx --yes copilotkit@4.10.1 verify --round-trip --expect-learning-container <container id> --json
+npx --yes copilotkit@4.11.0 verify --round-trip --expect-learning-container <container id> --json
 ```
 
 The check reads the thread that this run created, so a second round trip proves a second
@@ -285,7 +285,7 @@ For a recorded `both-oss` starting state, this step has no component to render.
 same request the baseline recorded, require the same kind of user-visible result the
 baseline produced, and require that the thread for that request is listed in the drawer.
 Where this journey's frontend framework ships no threads drawer -- React Native --, prove
-that thread with `npx --yes copilotkit@4.10.1 verify --round-trip`, which reads the
+that thread with `npx --yes copilotkit@4.11.0 verify --round-trip`, which reads the
 answer back off the thread and needs no browser. Record which of the two you proved.
 
 Use the surface control the main coding agent recorded for your environment. It either had
@@ -313,7 +313,7 @@ request never exercises. Drive it with the browser control step 6 named.
    the page to finish loading. Do not retype the host, and do not substitute a URL a tool
    offers you by default. Where the page loads but its styling is missing or the chat
    control is dead, run
-   `npx --yes copilotkit@4.10.1 verify --frontend-url <the url you opened> --json`
+   `npx --yes copilotkit@4.11.0 verify --frontend-url <the url you opened> --json`
    before you diagnose anything else. A dev server can serve its page and refuse every
    static chunk behind it, and on screen that is indistinguishable from a broken
    integration. The `frontend_assets_served` check tells the two apart.
@@ -337,8 +337,9 @@ request never exercises. Drive it with the browser control step 6 named.
 9. Record one line for the finished turn: the time, the page URL, the element you read
    the answer from, and what that element showed.
 
-Report exactly one of `performed`, `skipped-no-browser-tool`, or `failed` for a web
-frontend.
+Report exactly one of `performed`, `skipped-no-browser-tool`, `skipped-cloned-starter`, or
+`failed` for a web frontend. Report `skipped-cloned-starter` when this prompt told you to
+open no browser because the run cloned a starter.
 
 ### Step 6b -- React Native
 
@@ -363,7 +364,8 @@ An Android emulator reaches a runtime on the host machine at `10.0.2.2` rather t
 `localhost`. A request that fails against the runtime with nothing in the runtime's own
 log is that, rather than a broken runtime.
 
-Report exactly one of `performed`, `skipped-no-device`, or `failed` for React Native.
+Report exactly one of `performed`, `skipped-no-device`, `skipped-cloned-starter`, or
+`failed` for React Native.
 
 ## Step 7 -- Check the answer against the project's data
 
@@ -412,7 +414,7 @@ it, rather than reading the compatibility field as a pass.
 For every other starting state, record Step 8 as not applicable.
 
 The application edit ban ends only after Step 8 passes or is recorded as not applicable.
-Step 9 can write only the tool files named by its guide.
+Step 9 can write only the tool files named by its guide or by this step.
 
 ## Step 9 -- Set up the continued-development tools
 
@@ -423,12 +425,27 @@ Tell the developer what the skills install writes into this project before you r
 `.agents/skills` directory holding one folder per CopilotKit skill, linked into
 `.claude/skills`. Both sit in the working tree, so the install shows up in `git status`
 and can land in a commit. You cannot know whether this project keeps those directories in
-version control, so name them before you write them rather than after.
+version control, so name them before you write them rather than after. Say the same
+thing about the MCP registration below where it writes `.mcp.json`: that file lands in the
+working tree beside them, for the same reason and with the same consequence.
 
 Use it to install the project-scoped CopilotKit Skills.
-Use it to configure the CopilotKit documentation MCP server for the current coding agent.
-That registration goes in the coding agent's own configuration for this project, not in
-the working tree.
+Use it to configure the CopilotKit documentation MCP server for the coding-agent slug this
+run reported to `onboard identify`.
+
+Register it in this project wherever that agent reads a project-scoped file. For
+`claude-code` that is `claude mcp add --scope project`, which writes `.mcp.json` at the
+project root. Without that flag the command writes the agent's own configuration under the
+developer's home directory, outside this project, so pass it even where the command line
+you were given leaves it out. For `github-copilot` the project-scoped file is
+`.vscode/mcp.json`, and for `cursor` it is the project `mcp.json`.
+
+Where the agent reads no project-scoped file at all, do not run the registration. `codex`
+and `windsurf` write only under the home directory, and the desktop and web clients
+register through a settings screen this run cannot reach. Print the exact command or
+setting the guide gives for that agent, and tell the developer it is theirs to run. Record
+that as handed over rather than as failed: nothing went wrong, and this run is not allowed
+to edit configuration outside the project.
 
 Check whether each install succeeded and record what you found. Record the command result
 for each attempt. Report the Skills result and the MCP result separately from the proof

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

@@ -30,13 +30,13 @@ Before you show the best-effort plan, require this complete packet:
 - Give the ordered proof rules.
 
 After the developer approves the best-effort plan, run
-`npx --yes copilotkit@4.10.1 onboard read fallback/best-effort`.
+`npx --yes copilotkit@4.11.0 onboard read fallback/best-effort`.
 
-Send one short report. Run the friction command without another developer question. The
-CLI telemetry gate decides whether the report is sent.
+Send one short report. Run the friction command without another developer question. Do not
+ask the developer about telemetry: the command applies the setting they already have.
 
 ```text
-npx --yes copilotkit@4.10.1 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.11.0 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.

package/package.json

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

package/release/release-tool.js

@@ -14698,7 +14698,7 @@ import * as path4 from "node:path";
 
 // apps/cli/src/config.ts
 function getTemplateRef() {
-  return true ? "7e6964fc11092b685bbea62bc331d5d177b738c1" : "main";
+  return true ? "dc1238c0bd473e259c992b85026cb30fe6b3b726" : "main";
 }
 
 // apps/cli/src/services/agentcore-config.ts