copilotkit 4.9.37 → 4.9.47

package/onboarding/prompts/frontend/vue.md

@@ -16,7 +16,7 @@ page above. Vue has its own `useComponent`, which is not the React package. Take
 that reference page rather than from a Vue generative-UI guide, which is not published.
 
 If the pages support the selection, record Vue 3 and these URLs. Then run
-`npx --yes copilotkit@4.9.37 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.47 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.37 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/implementation/build-and-validate.md

@@ -7,7 +7,7 @@ Do not implement the plan yourself. Use the step order in the approved plan.
 Run the audit from the target app directory:
 
 ```text
-npx --yes copilotkit@4.9.37 onboard audit
+npx --yes copilotkit@4.9.47 onboard audit
 ```
 
 It compares every protected path with the digest the CLI captured for it. Its result starts
@@ -29,7 +29,7 @@ A path that no Files changed section names changed outside the run, and it is th
 developer's own file. Accept it by name:
 
 ```text
-npx --yes copilotkit@4.9.37 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.9.47 onboard protect --accept-external --path <path>
 ```
 
 Pass one `--path` for each path you accept. Accept only a path the audit named, and only
@@ -48,11 +48,11 @@ acceptance clears it, or route out. Do not send an audit result to a repair work
 Report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.9.37 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.9.47 onboard checkpoint --phase plan-written
 ```
 
 Spawn one implementation subagent. Tell it to run
-`npx --yes copilotkit@4.9.37 onboard read subagent/implement-and-validate` first and follow
+`npx --yes copilotkit@4.9.47 onboard read subagent/implement-and-validate` first and follow
 the prompt it returns. If that read fails because the subagent cannot use the shell, stop that
 subagent. Run the same command yourself, then spawn a fresh subagent with the returned prompt
 and the same handoff. Give it the plan, selected framework, frontend, model, exact target app
@@ -72,11 +72,11 @@ returned. Continue to proof only when that audit passes.
 After the selected implementation path passes, report it:
 
 ```text
-npx --yes copilotkit@4.9.37 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.9.47 onboard checkpoint --phase build-validated
 ```
 
 Then run
-`npx --yes copilotkit@4.9.37 onboard read proof/round-trip`.
+`npx --yes copilotkit@4.9.47 onboard read proof/round-trip`.
 
 ## Repair rules
 
@@ -94,4 +94,4 @@ Route out for `Status: blocked`. Route out only when the failure is not yours to
 failure is in code this run did not write, the fix requires changing the developer's existing
 agent or frontend, the same command still fails after three repair attempts, or the
 documentation does not support the plan. In those cases run
-`npx --yes copilotkit@4.9.37 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/proof/complete.md

@@ -64,7 +64,7 @@ Name the debugging surface this journey's frontend can reach, rather than the on
 of the documentation leads with. For a web frontend it is the CopilotKit Inspector. For
 React Native there is no Inspector: it is a browser overlay built on a DOM custom element,
 and `@copilotkit/react-native` does not ship it. Give a mobile developer
-`npx --yes copilotkit@4.9.37 verify --round-trip`, the runtime's own log, the AG-UI
+`npx --yes copilotkit@4.9.47 verify --round-trip`, the runtime's own log, the AG-UI
 Event Inspector in the CopilotKit VS Code extension, and the Intelligence thread view
 instead. Naming the Inspector to a developer who cannot open it costs them the time it
 takes to conclude their own wiring is broken.
@@ -76,7 +76,7 @@ the friction commands without another developer question. The CLI telemetry gate
 whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.9.37 onboard friction --category <slug> --cost-seconds <seconds>
+npx --yes copilotkit@4.9.47 onboard friction --category <slug> --cost-seconds <seconds>
 ```
 
 Write one or two sentences on the command's standard input. Pick one category from
@@ -88,7 +88,7 @@ Pass --docs-path only for a docs-missing or docs-wrong report, naming the page t
 is about:
 
 ```text
-npx --yes copilotkit@4.9.37 onboard friction --category docs-wrong --cost-seconds 300 --docs-path /docs/threads/drawer
+npx --yes copilotkit@4.9.47 onboard friction --category docs-wrong --cost-seconds 300 --docs-path /docs/threads/drawer
 ```
 
 Give the page's site-relative path or its full URL, with no spaces, query string, or
@@ -105,14 +105,14 @@ Tell the developer when you send a friction report. Do not quote or summarize th
 unless the developer asks. If the CLI says that telemetry is disabled or unavailable,
 state that the report was not sent and continue without another question.
 
-When the evidence is gathered, run `npx --yes copilotkit@4.9.37 onboard complete`, carrying
+When the evidence is gathered, run `npx --yes copilotkit@4.9.47 onboard complete`, carrying
 the surface-check outcome the proof subagent returned. Pass exactly one flag, and pass the
 one that matches this journey's surface.
 
 For a web frontend -- React SPA, Next.js, Angular, Vue:
 
 ```text
-npx --yes copilotkit@4.9.37 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.9.47 onboard complete --visual-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-browser-tool`, or `failed`.
@@ -120,7 +120,7 @@ The outcome is one of `performed`, `skipped-no-browser-tool`, or `failed`.
 For React Native:
 
 ```text
-npx --yes copilotkit@4.9.37 onboard complete --device-check <outcome>
+npx --yes copilotkit@4.9.47 onboard complete --device-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-device`, or `failed`.
@@ -129,6 +129,19 @@ The two flags are not interchangeable and neither takes the other's outcomes. A
 proves nothing about a React Native view tree, and a device capture proves nothing about
 browser-origin CORS, so the flag you pass is how this run states which surface it proved.
 
+For a web frontend, also pass the URL the browser opened:
+
+```text
+npx --yes copilotkit@4.9.47 onboard complete --visual-check <outcome> \
+  --frontend-url <the url you opened>
+```
+
+Pass the URL from the proof subagent's record, unchanged. Only the kind of host is
+recorded -- a loopback hostname, a loopback IP literal, another IP literal, or another
+name -- and never the host itself. A run that opened the loopback IP literal loses every
+static chunk to a refusal, and the field is how that stops being invisible. Leave the flag
+off for React Native, which opens no URL.
+
 Pass the outcome you were given rather than the one you wanted. Anything but `performed`
 prints what the missing check leaves unverified and ends this run as blocked. That output
 is the developer's finding, so carry it into the summary rather than restating it as a
@@ -138,7 +151,7 @@ If the round trip proved and something after it still blocked this run, add `--b
 to the same command:
 
 ```text
-npx --yes copilotkit@4.9.37 onboard complete --visual-check performed --blocked-by <cause>
+npx --yes copilotkit@4.9.47 onboard complete --visual-check performed --blocked-by <cause>
 ```
 
 The cause is one of `inspector` for a debugging surface that did not open,

package/onboarding/prompts/proof/oss-baseline.md

@@ -1,7 +1,7 @@
 # Prove the existing OSS baseline
 
 Do not prove the baseline yourself. Spawn one proof subagent. Tell it to run
-`npx --yes copilotkit@4.9.37 onboard read subagent/prove-oss-baseline` first and follow the
+`npx --yes copilotkit@4.9.47 onboard read subagent/prove-oss-baseline` first and follow the
 prompt it returns. If that read fails because the subagent cannot use the shell, stop that
 subagent. Run the same command yourself, then spawn a fresh subagent with the returned prompt
 and the same handoff. Give it the repository findings and exact CLI package spec.
@@ -17,7 +17,7 @@ Wait for the subagent to finish.
 Record what that proof returned before you route on it:
 
 ```text
-npx --yes copilotkit@4.9.37 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
+npx --yes copilotkit@4.9.47 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
 ```
 
 Report the gate whatever it returned. Pass `passed` when the subagent proved a predicate,
@@ -35,14 +35,14 @@ Do not change project files before this proof ends. Starting existing developmen
 processes and their ignored runtime files is allowed.
 
 If the subagent proves the `both-oss` predicate, keep its evidence with the plan and run
-`npx --yes copilotkit@4.9.37 onboard read conversion/plan`. That project already works.
+`npx --yes copilotkit@4.9.47 onboard read conversion/plan`. That project already works.
 What it needs is the conversion, not a build.
 
 If it proves another supported starting state, record that state and run
-`npx --yes copilotkit@4.9.37 onboard read credentials/plan`. This prompt is served
+`npx --yes copilotkit@4.9.47 onboard read credentials/plan`. This prompt is served
 whenever a project looks like an OSS integration, so a baseline that did not prove is an
 ordinary starting state rather than a failure.
 
 If it cannot identify the running process safely, exposes a secret, or finds a baseline
 failure that cannot be classified, run
-`npx --yes copilotkit@4.9.37 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/proof/round-trip.md

@@ -1,7 +1,7 @@
 # Prove the user journey
 
 Do not do the proof work yourself. Spawn one proof subagent. Tell it to run
-`npx --yes copilotkit@4.9.37 onboard read subagent/prove-round-trip` first and follow the
+`npx --yes copilotkit@4.9.47 onboard read subagent/prove-round-trip` first and follow the
 prompt it returns. If that read fails because the subagent cannot use the shell, stop that
 subagent. Run the same command yourself, then spawn a fresh subagent with the returned prompt
 and the same handoff. Give it the selected framework, frontend, model, approved plan, selected
@@ -23,13 +23,13 @@ pass the time.
 Report each attempt at the journey as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.37 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.9.47 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Record what that proof returned before you route on it:
 
 ```text
-npx --yes copilotkit@4.9.37 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.9.47 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Report the gate whatever it returned. A proof that never ran is `skipped`, not failed. The
@@ -37,7 +37,7 @@ command prints one line and sends nothing else. Where a repair cycle runs the pr
 record each attempt as it ends.
 
 For every protected-path audit in this prompt, run
-`npx --yes copilotkit@4.9.37 onboard audit` from the target app directory. If its result
+`npx --yes copilotkit@4.9.47 onboard audit` from the target app directory. If its result
 starts with `Status: blocked`, report the printed reason and use the route-out rules below.
 A blocked audit proved nothing changed and is not a preservation failure. If a
 protected-path audit reports a changed path, decide it the way the implementation prompt
@@ -46,13 +46,13 @@ returns none, so a finding with no Files changed section to test against routes
 path one of those sections names is this run's own change and routes out too. Accept a
 path only when a section this run collected covers the step that wrote it and does not
 name it:
-`npx --yes copilotkit@4.9.37 onboard protect --accept-external --path <path>`. Then run
+`npx --yes copilotkit@4.9.47 onboard protect --accept-external --path <path>`. Then run
 the audit again and name the path in the closing summary. Never repair, reset, or revert a
 protected path.
 
 If the proof result starts with `Status: passed`, run the protected-path audit. Continue to
 `proof/complete` only if that audit passes. After the audit passes, run
-`npx --yes copilotkit@4.9.37 onboard read proof/complete`. A performed surface outcome with
+`npx --yes copilotkit@4.9.47 onboard read proof/complete`. A performed surface outcome with
 the full round trip is core success even if a continued-development tool fails. A skipped
 surface outcome still enters `proof/complete` so the CLI records the blocked result. Do not
 describe a skipped surface as proved. Keep the Skills and MCP results separate from the proof
@@ -108,7 +108,7 @@ Restart each project-owned process changed by the repair. Report the cycle, coun
 one:
 
 ```text
-npx --yes copilotkit@4.9.37 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.9.47 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 Then spawn a fresh proof subagent
@@ -126,7 +126,7 @@ and proof cycles.
 
 Route out only when the failure is not yours to fix, when the same proof still fails after
 three attempts, or when no evidence of the round trip can be produced. In those cases run
-`npx --yes copilotkit@4.9.37 onboard read unsupported/no-validated-path`. All three are
+`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`. All three are
 about the round trip itself. A round trip that proved is not one of them, whatever failed
 after it.
 
@@ -136,7 +136,7 @@ Run the feedback command without another developer question. The CLI telemetry g
 whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.9.37 onboard feedback
+npx --yes copilotkit@4.9.47 onboard feedback
 ```
 
 Write at most four lines to standard input: the step you stopped at and what stopped it.

package/onboarding/prompts/starter/clone.md

@@ -43,7 +43,7 @@ the derived name.
 Only if the developer asks for an existing project, or asks to see the projects they have,
 read the choices:
 
-`npx --yes copilotkit@4.9.37 project list --json`
+`npx --yes copilotkit@4.9.47 project list --json`
 
 Then ask which one to use. Do not order the projects by creation time. If the developer
 already gave this answer, do not ask again. Do not read a secret value. Do not show or
@@ -53,7 +53,7 @@ Run the command from the parent directory. Do not inspect another entry in the p
 directory. Replace each placeholder with the recorded value. Do not run a placeholder as
 a shell argument.
 
-`npx --yes copilotkit@4.9.37 init --name <project-name> --framework <framework-id> --channel none --no-banner --create <name> --install`
+`npx --yes copilotkit@4.9.47 init --name <project-name> --framework <framework-id> --channel none --no-banner --create <name> --install`
 
 Pass the confirmed name to both `--name` and `--create`: the app directory and its
 Intelligence project take the same name here. If the developer names an existing project,
@@ -69,14 +69,14 @@ account. The command does not need terminal input.
 If the command succeeds, do not rebuild the starter by hand. Report the clone first:
 
 ```text
-npx --yes copilotkit@4.9.37 onboard checkpoint --phase starter-cloned
+npx --yes copilotkit@4.9.47 onboard checkpoint --phase starter-cloned
 ```
 
 Then inspect only the generated
 paths inside the target directory. Record the files, install result, project connection,
 and validation commands. Then run
-`npx --yes copilotkit@4.9.37 onboard read proof/round-trip`.
+`npx --yes copilotkit@4.9.47 onboard read proof/round-trip`.
 
 If the command fails, report its exact error and do not claim that the starter is ready.
 Then run
-`npx --yes copilotkit@4.9.37 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.

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

@@ -122,7 +122,7 @@ here is work the developer did not ask for.
 Plan the threads drawer itself: add it from the selected drawer page, where this frontend
 does not already render one. Where this journey's frontend framework ships no threads
 drawer -- React Native --, plan that the thread is proved by
-`npx --yes copilotkit@4.9.37 verify --round-trip`, which needs no browser. Do not plan a
+`npx --yes copilotkit@4.9.47 verify --round-trip`, which needs no browser. Do not plan a
 step that opens the managed Intelligence dashboard.
 
 ## Order the plan into steps

package/onboarding/prompts/subagent/prove-oss-baseline.md

@@ -19,7 +19,7 @@ Prove the live runtime in this order:
 4. Confirm from project files that the runtime constructor passes a `runner` option rather
    than an `intelligence` option. A package, import, project file, or key is not use proof.
 5. Run
-   `npx --yes copilotkit@4.9.37 verify --expect-runtime oss --round-trip --agent <expected-agent-id> --json`,
+   `npx --yes copilotkit@4.9.47 verify --expect-runtime oss --round-trip --agent <expected-agent-id> --json`,
    with the runtime URL or auth header options that this project needs. Require exit zero
    and the JSON `ok` field to be `true`.
 6. Drive one real request through the existing frontend, CopilotKit runtime, and expected

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

@@ -90,8 +90,11 @@ A server that never answered has written the reason to its own output, and readi
 output is faster than starting it again.
 
 Leave the agent and frontend servers running after proof. Record each process ID and a
-safe command that stops that process. Record the frontend URL, written with `localhost`
-rather than an IP literal, and the commands that start both servers again.
+safe command that stops that process. Record the commands that start both servers again.
+
+Record the frontend URL the server you started reports, and treat it as provisional. Step 4
+replaces it with the URL the CLI resolves. Do not compose one of your own from a port you
+read here.
 
 ## Step 3 -- Identify the process that answered
 
@@ -120,7 +123,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.9.37 verify --json`. It reads the port from this project, so a
+`npx --yes copilotkit@4.9.47 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
@@ -135,7 +138,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.9.37 project select` from the app directory. Do not link,
+`npx --yes copilotkit@4.9.47 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.
 
@@ -144,9 +147,21 @@ mounted `mode: "single-route"` is the usual cause. Return it for implementation
 option and use a catch-all route. Do not edit it. If the check is `undetermined` because no
 thread-endpoint state exists, the runtime predates the field. Record that and continue.
 
+Take the frontend URL from the payload's `frontendUrl`. It replaces whatever step 2
+recorded, and every later step uses it unchanged. Where the field is absent, the project
+named no port the CLI can read: keep step 2's URL, and rewrite its host as `localhost`
+before you use it.
+
+Then run the command once more with the URL you are about to open:
+`npx --yes copilotkit@4.9.47 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
+is the cheapest step that can save the most expensive one, so run it before the browser.
+
 ## Step 5 -- Prove that the agent runs
 
-Run `npx --yes copilotkit@4.9.37 verify --round-trip --json`. It sends one request through
+Run `npx --yes copilotkit@4.9.47 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
@@ -223,7 +238,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.9.37 verify --round-trip`, which reads the
+that thread with `npx --yes copilotkit@4.9.47 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
@@ -247,11 +262,14 @@ under a name that says what it was.
 The surface is a browser, and it also covers browser-origin CORS and CSP, which a CLI
 request never exercises. Drive it with the browser control step 6 named.
 
-1. Open the frontend URL from step 2 and wait for the page to finish loading.
-   Address it as `localhost` rather than an IP literal, for the reason step 3 gives
-   for the agent. A dev server reached on the IP literal can refuse its own static
-   assets, and a page that loads without them leaves the chat control dead. That
-   reads as a broken integration rather than as the host name you used.
+1. Open the frontend URL step 4 resolved, exactly as that step recorded it, and wait for
+   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.9.47 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.
 2. Take one page snapshot. Record whether the CopilotKit surface is on the page. A page
    that renders without it is a wiring failure rather than a proof to retry.
 3. Read the browser console before you type anything, and record every error already

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.9.37 onboard read fallback/best-effort`.
+`npx --yes copilotkit@4.9.47 onboard read fallback/best-effort`.
 
 Send one short report. Run the feedback command without another developer question. The
 CLI telemetry gate decides whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.9.37 onboard feedback
+npx --yes copilotkit@4.9.47 onboard feedback
 ```
 
 Write the feedback message to the command's standard input, in at most four lines.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "copilotkit",
-  "version": "4.9.37",
+  "version": "4.9.47",
   "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 ? "aec312634129f97f90154bb416a07e8cc0c13a2a" : "main";
+  return true ? "380ad1220a7bc78104baedc469c4d086c8910494" : "main";
 }
 
 // apps/cli/src/services/agentcore-config.ts