copilotkit 4.23.0 → 4.24.0

package/onboarding/index.json

@@ -1,5 +1,5 @@
 {
-  "graphTree": "a92d5d4a1d73d583df5be10af020eeee9dc84ca9",
+  "graphTree": "29dcb290ab507cc1cc9d3f7263f9c39eafe4607b",
   "intentRoots": {
     "add-a2ui": "feature/a2ui/start",
     "add-chat-suggestions": "feature/chat-suggestions/start",
@@ -9,6 +9,7 @@
     "add-rich-threads": "feature/rich-threads/start",
     "add-voice": "feature/voice/start"
   },
+  "packageSpec": "copilotkit@4.24.0",
   "root": "authenticate/start",
   "prompts": [
     {

package/onboarding/prompts/authenticate/start.md

@@ -14,7 +14,7 @@ does is hidden from the developer.
 
 Run each CLI call exactly as written, as its own command: no pipe, `tee`, `&&`, redirect,
 or variable prefix. Every CLI call in this run matches the prefix rule
-`["npx", "--prefer-offline", "--yes", "copilotkit@4.23.0"]`. If a command can request
+`["npx", "--prefer-offline", "--yes", "copilotkit@4.24.0"]`. If a command can request
 escalation with a prefix rule, request this one on the `onboard identify` call. If your
 harness asks the developer to approve commands, tell them one approval of that prefix covers
 every CLI call. Say then that the install, the dev servers, `curl` to the local app, and
@@ -33,7 +33,7 @@ That refusal is a pause, not a stop.
 Run this before anything else in this prompt, including the welcome message below:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
+npx --prefer-offline --yes copilotkit@4.24.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`.
@@ -60,10 +60,10 @@ the whole run. Every later command reports against it.
 
 Every later command must run from the directory this run started in. Elsewhere, the
 command cannot find its run and refuses. Do not report that refusal as a stop. Run
-`npx --prefer-offline --yes copilotkit@4.23.0 onboard start --run <onboarding_run_id>` where you are
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard start --run <onboarding_run_id>` where you are
 standing, then run the refused command again.
 
-If you no longer hold the id, run `npx --prefer-offline --yes copilotkit@4.23.0 onboard start` in the
+If you no longer hold the id, run `npx --prefer-offline --yes copilotkit@4.24.0 onboard start` in the
 directory this run started in, with no `--run` and no `--intent`. It reprints the id of the
 run under way and starts nothing. An id this project does not already hold starts a second
 run, and the work already done stops counting toward the first.
@@ -120,7 +120,7 @@ A turn that ends while the run waits is a pause, not a stop, even when your harn
 A terminal that sends the report itself, or says to file none, overrides this.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.24.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -135,18 +135,21 @@ rule that stopped you says next: send the report, then stop.
 
 ## Choose where the app stores data
 
-Before sign-in, run `npx --prefer-offline --yes copilotkit@4.23.0 local --help`.
-If it lists candidate setup and no choice exists, offer managed service or local Docker
-evaluation. If it does not, keep the managed path. Existing local recovery still works.
+Before sign-in, run `npx --prefer-offline --yes copilotkit@4.24.0 local --help`.
+If it lists `setup` ("Configure model access and install or resume the local stack") and no
+choice exists, offer managed or local Docker evaluation. Otherwise keep managed. Existing
+local recovery still works.
+Record the path with
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard deployment --choice <managed|local>`.
 
 For a local choice, run
-`npx --prefer-offline --yes copilotkit@4.23.0 onboard read deployment/choose-local`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read deployment/choose-local`.
 It records the choice for new and existing apps, completes sign-in, and starts research.
 For managed service, continue with “Check sign-in”.
 
 ## Check sign-in
 
-Run `npx --prefer-offline --yes copilotkit@4.23.0 login --json` before any project work. This command
+Run `npx --prefer-offline --yes copilotkit@4.24.0 login --json` before any project work. This command
 checks the current session. It starts sign-in only as needed. Treat this as a long-lived
 streaming process. Do not wait for the command to exit before you read its standard output.
 
@@ -191,9 +194,9 @@ conversation.
 
 Research reads only this project and needs no account. Start it as soon as the session is
 valid or the developer has the sign-in page, and keep monitoring the login process while it
-runs: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read research/gather`. If this run already
+runs: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read research/gather`. If this run already
 started the research, do not start it again.
 
 If sign-in stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.23.0 onboard read stopped/run-failed`. It says nothing about
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read stopped/run-failed`. It says nothing about
 whether this project's stack is supported, which is not yet known at this point.

package/onboarding/prompts/conversion/plan.md

@@ -100,7 +100,7 @@ of this journey, and a drawer that lists nothing is not a reason to mint one. Li
 tokens stay a self-hosted concern.
 
 Where this journey's frontend framework ships no threads drawer -- React Native --, the
-fifth item is proved by `npx --prefer-offline --yes copilotkit@4.23.0 verify --round-trip`, which sends a
+fifth item is proved by `npx --prefer-offline --yes copilotkit@4.24.0 verify --round-trip`, which sends a
 real request and reads the answer back off the thread it landed on. The run says which of
 the two it proved. Do not send a run to the managed Intelligence dashboard to prove this.
 An authenticated browser session at a hosted dashboard is the one thing an agent-driven run
@@ -116,7 +116,7 @@ and passed -- so a run scored on either one was scored on the same fact. Every r
 resolves that condition from, while `licenseStatus` is a compatibility projection of it
 for older thread surfaces and outlives them only until those surfaces go.
 
-Then run `npx --prefer-offline --yes copilotkit@4.23.0 onboard read credentials/finalize-plan`.
+Then run `npx --prefer-offline --yes copilotkit@4.24.0 onboard read credentials/finalize-plan`.
 
 If a selected page does not load after the second method, run
-`npx --prefer-offline --yes copilotkit@4.23.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/credentials/finalize-plan.md

@@ -1,7 +1,7 @@
 # Select the Intelligence project
 
 For a recorded local choice, run
-`npx --prefer-offline --yes copilotkit@4.23.0 onboard read deployment/local-evaluation`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read deployment/local-evaluation`.
 That path obtains approval and connects the local project. Skip hosted selection.
 Keep the implementation and feature-proof requirements.
 
@@ -29,7 +29,7 @@ Choose the starting state from the repository findings:
 A run served `proof/oss-baseline` records one of the last two.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend>
+npx --prefer-offline --yes copilotkit@4.24.0 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend>
 ```
 
 If a value is refused, fix it from the choices the earlier prompts gave, and run the
@@ -42,7 +42,7 @@ runtime `.env` file, that directory is the target, not the repository root. Do n
 the developer to another terminal.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard credentials --json
+npx --prefer-offline --yes copilotkit@4.24.0 onboard credentials --json
 ```
 
 Every credential this run writes goes to the target's `.env`, the environment path. The
@@ -72,9 +72,9 @@ project from a listing without an answer that names it.
 `--runtime-url` is the URL port research settled, mount path included:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard credentials --create <name> \
+npx --prefer-offline --yes copilotkit@4.24.0 onboard credentials --create <name> \
   --runtime-url http://localhost:<port>/api/copilotkit --json
-npx --prefer-offline --yes copilotkit@4.23.0 onboard credentials --project <slug-or-id> \
+npx --prefer-offline --yes copilotkit@4.24.0 onboard credentials --project <slug-or-id> \
   --runtime-url http://localhost:<port>/api/copilotkit --json
 ```
 
@@ -84,8 +84,8 @@ command unless the developer asks to see their projects, or `notFound` is presen
 show only what they asked for, and do not order it by creation time:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 project list --json
-npx --prefer-offline --yes copilotkit@4.23.0 project list --search <query> --json
+npx --prefer-offline --yes copilotkit@4.24.0 project list --json
+npx --prefer-offline --yes copilotkit@4.24.0 project list --search <query> --json
 ```
 
 `app-directory` means that the key landed where no app reads it. Pick the directory in
@@ -100,4 +100,4 @@ the `--project` command from there with `project.slug`. Do not copy or link the
   reused. The round-trip proof later runs the authenticated Intelligence checks, so record
   the reused project credentials as unverified in the plan until those checks pass.
 
-Then run `npx --prefer-offline --yes copilotkit@4.23.0 onboard read credentials/settle-credentials`.
+Then run `npx --prefer-offline --yes copilotkit@4.24.0 onboard read credentials/settle-credentials`.

package/onboarding/prompts/credentials/plan.md

@@ -20,7 +20,7 @@ If the target directory holds no project and the copied prompt came from the Sla
 Microsoft Teams docs page, do not ask the framework question. The Channel starter brings
 its own agent, so an answer here decides nothing. Tell the developer that the Channel
 starter decides the agent, then run
-`npx --prefer-offline --yes copilotkit@4.23.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read frontend/plan`.
 
 ## Frameworks this machine cannot run yet
 
@@ -42,7 +42,7 @@ things in one message:
 2. That the coding agent's shell reads PATH when it starts, so it cannot see the new
    toolchain until the developer restarts the coding agent.
 3. That the run resumes after the restart with
-   `npx --prefer-offline --yes copilotkit@4.23.0 onboard start --run <onboarding_run_id>`.
+   `npx --prefer-offline --yes copilotkit@4.24.0 onboard start --run <onboarding_run_id>`.
 
 Then end your turn and wait for the developer. That restart is a step here, not an error.
 
@@ -111,27 +111,27 @@ developer's words instead.
 
 Use exactly one matching internal route:
 
-1. AG2: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/ag2`
-2. Agno: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/agno`
-3. Built-in CopilotKit agent: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/built-in`
-4. Claude Agent SDK Python: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/claude-sdk-python`
-5. Claude Agent SDK TypeScript: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/claude-sdk-typescript`
-6. CrewAI Flows: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/crewai-flows`
-7. Existing AG-UI agent: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/custom-ag-ui`
-8. Deep Agents: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/deep-agents`
-9. LangGraph Python: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/langgraph-python`
-10. LangGraph FastAPI: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/langgraph-fastapi`
-11. LangGraph TypeScript: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/langgraph-typescript`
-12. LlamaIndex: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/llamaindex`
-13. ADK: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/google-adk`
-14. Microsoft Agent Framework Python: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/ms-agent-python`
-15. Microsoft Agent Framework .NET: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/ms-agent-dotnet`
-16. Mastra: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/mastra`
-17. MS Agent Harness .NET: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/ms-agent-harness-dotnet`
-18. Pydantic AI: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/pydantic-ai`
-19. Strands Agents Python: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/strands-python`
-20. Strands Agents TypeScript: `npx --prefer-offline --yes copilotkit@4.23.0 onboard read framework/strands-typescript`
+1. AG2: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/ag2`
+2. Agno: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/agno`
+3. Built-in CopilotKit agent: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/built-in`
+4. Claude Agent SDK Python: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/claude-sdk-python`
+5. Claude Agent SDK TypeScript: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/claude-sdk-typescript`
+6. CrewAI Flows: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/crewai-flows`
+7. Existing AG-UI agent: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/custom-ag-ui`
+8. Deep Agents: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/deep-agents`
+9. LangGraph Python: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/langgraph-python`
+10. LangGraph FastAPI: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/langgraph-fastapi`
+11. LangGraph TypeScript: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/langgraph-typescript`
+12. LlamaIndex: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/llamaindex`
+13. ADK: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/google-adk`
+14. Microsoft Agent Framework Python: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/ms-agent-python`
+15. Microsoft Agent Framework .NET: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/ms-agent-dotnet`
+16. Mastra: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/mastra`
+17. MS Agent Harness .NET: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/ms-agent-harness-dotnet`
+18. Pydantic AI: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/pydantic-ai`
+19. Strands Agents Python: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/strands-python`
+20. Strands Agents TypeScript: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read framework/strands-typescript`
 
 If the project has an agent in another framework that does not speak AG-UI, or no
 listed framework fits, keep the developer's current agent and run
-`npx --prefer-offline --yes copilotkit@4.23.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/credentials/settle-credentials.md

@@ -21,7 +21,7 @@ The plan names the model credential variables. Run this from the directory that
 `environmentPath` in the project step's result, with one `--model-key` for each variable:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard credentials --model-key <variable> --json
+npx --prefer-offline --yes copilotkit@4.24.0 onboard credentials --model-key <variable> --json
 ```
 
 When the framework node names another env file for the credential, add
@@ -38,9 +38,18 @@ never prints a value. When every key settles, it protects the credential paths.
   itself. By default, plan to copy the key into the app's env file, which git ignores.
   This command protects that env file, and the copy is a file the run writes itself, so
   list the copy under `Files the run writes itself`, not under `Authorization requested`.
-  The developer's approval of the plan is their consent to the copy. Copy the key without
-  printing it. Then record the copy with
-  `npx --prefer-offline --yes copilotkit@4.23.0 onboard protect --accept-credential --path <env file>`. If the developer declines the copy, the plan has the app read the key from an
+  The developer's approval of the plan is their consent to the copy. After the approval,
+  copy the key with the command that `next` names. It has this form:
+  `npx --prefer-offline --yes copilotkit@4.24.0 onboard credentials --model-key <variable> --env-path <file> --copy-to <env file> --json`.
+  It writes the key without printing it and protects the env file. Do not copy the key
+  yourself, and do not write a `sed`, `grep`, or `cat` command for it. If you cannot run
+  the command, for example because a sandbox refuses the path, ask the developer to run it.
+  Give them exactly this one line, with `<app directory>` as the directory that holds
+  `environmentPath`:
+  `! cd <app directory> && npx --prefer-offline --yes copilotkit@4.24.0 onboard credentials --model-key <variable> --env-path <file> --copy-to <env file>`.
+  The command needs no input. Without `!`, they run the same command in a terminal.
+  When they reply, run the same command with `--json` and read `copiedKeys`.
+  If the developer declines the copy, the plan has the app read the key from an
   environment variable that the developer sets. The plan then says how to set it. Never
   write the outside path into a project file, not even in a config file such as
   `langgraph.json`. A committed file that names a folder in the developer's home directory
@@ -69,4 +78,4 @@ Never read a file outside the project directory to find a credential: a key foun
 bills another project. Asking for a path is not requesting a secret. A path the developer
 names is theirs to give, including one outside the project. A path this run finds is not.
 
-Then run `npx --prefer-offline --yes copilotkit@4.23.0 onboard read credentials/write-plan`.
+Then run `npx --prefer-offline --yes copilotkit@4.24.0 onboard read credentials/write-plan`.

package/onboarding/prompts/credentials/write-plan.md

@@ -11,7 +11,7 @@ friction command follows the telemetry setting the developer already chose, so i
 separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.24.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -72,7 +72,7 @@ page is selected yet, add the one for the frontend selected above to the same li
    Native, so the planner proves the thread with `verify --round-trip` instead.
 
 Spawn one planning subagent. Tell it to run
-`npx --prefer-offline --yes copilotkit@4.23.0 onboard read subagent/create-plan` first and follow the prompt
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read subagent/create-plan` 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, selected framework, frontend, model, credential
@@ -86,7 +86,7 @@ Wait for the subagent to finish.
 Continue only if the planning result starts with `Status: passed`. For `Status: failed`,
 send the result back to the planning subagent for repair, up to three attempts. For
 `Status: blocked`, or a third failed result, run
-`npx --prefer-offline --yes copilotkit@4.23.0 onboard read stopped/run-failed`. A plan this run cannot
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read stopped/run-failed`. A plan this run cannot
 write is a run that broke, not a stack the documentation does not cover. The exception is
 a blocked result that names `unsupported/no-validated-path`: the planning subagent found
 that no page supports the plan, so take the no-supported-path route at the end of this
@@ -132,11 +132,11 @@ Before you end your turn to wait for the answer, report the pause, each time you
 plan:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard checkpoint --phase awaiting-plan-approval
+npx --prefer-offline --yes copilotkit@4.24.0 onboard checkpoint --phase awaiting-plan-approval
 ```
 
 If the developer approves the plan, run
-`npx --prefer-offline --yes copilotkit@4.23.0 onboard read implementation/build-and-validate`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read implementation/build-and-validate`.
 
 If no exact supported path or documentation URL exists, run
-`npx --prefer-offline --yes copilotkit@4.23.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/deployment/choose-local.md

@@ -16,31 +16,42 @@ Explain these conditions before sign-in:
   separate settings, or remain configuration incomplete until settings are supplied.
 - Slack and Teams need internet access and a developer-provided public HTTPS endpoint.
 
-Collect a path to the published candidate manifest. There is no selected default.
-Do not substitute an arbitrary chart tag or a checkout build. If no manifest exists,
-report that candidate publication is needed and take the failure path below.
+The CLI selects the latest stable release by itself. Do not ask for a release or a
+candidate manifest. If the developer gives a candidate manifest path for release
+testing, record it for setup. Do not substitute a chart tag or a checkout build.
 Never ask the developer to paste credentials into the conversation.
 
-Collect the model choice. For reuse, have the developer place their compatible app
-model settings in a private JSON file with `model`, `provider`, and any needed
-`baseUrl` and `apiKey` fields. Use that file with `--model-config`. Separate settings
-use the same private file format. Deferral uses `--defer-model`.
-
-Record the candidate path and model choice in the plan, but no secret values.
+Collect the model choice for Learning. The first proof does not need a Learning model,
+and Learning starts its first run only after 15 conversations. Offer these choices:
+
+1. Configure later, the default. Install with `--defer-model`. In the closing report, write
+   "Learning configuration incomplete". Name the command that adds the model later:
+   `npx --prefer-offline --yes copilotkit@4.24.0 local setup`, run in a terminal in the app directory.
+2. Guided setup. If the developer named Learning as a goal, offer it first. Install
+   the stack with `--defer-model`. After the stack is ready, the developer runs
+   `npx --prefer-offline --yes copilotkit@4.24.0 local setup` in their own terminal window, in the app
+   directory. Never give it as a `!` line: its guided prompt needs a terminal, and a coding
+   agent's shell has none. The prompt asks for the model and its key, and it saves them
+   privately. On a running stack, it restarts only Learning. Do not ask the developer to
+   write a file.
+3. A private model file that the developer has already. Pass its path with
+   `--model-config <file>`. Do not read or print the file.
+
+Record the model choice, and any candidate path, in the plan, but no secret values.
 Create no cluster and change no app files at this step. The developer can still decline sign-in.
 If declined, take the failure path below.
 
-Run `npx --prefer-offline --yes copilotkit@4.23.0 login --json`. Follow the streaming sign-in
+Run `npx --prefer-offline --yes copilotkit@4.24.0 login --json`. Follow the streaming sign-in
 protocol from “Check sign-in” in the start prompt: open the first authentication URL
 once, keep the same process running, and continue only after its completed record.
 Explain that this sign-in obtains the evaluation license, not the local dashboard login.
 On failed or declined sign-in, take the failure path below.
 
 After sign-in completes, continue with
-`npx --prefer-offline --yes copilotkit@4.23.0 onboard read research/gather`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read research/gather`.
 Keep the local choice and collected paths in the run's plan and worker context.
 
 ## Failure path
 
-If the candidate is missing or sign-in fails or is declined, stop before cluster creation.
-Run `npx --prefer-offline --yes copilotkit@4.23.0 onboard read stopped/run-failed`.
+If sign-in fails or is declined, stop before cluster creation.
+Run `npx --prefer-offline --yes copilotkit@4.24.0 onboard read stopped/run-failed`.

package/onboarding/prompts/deployment/local-evaluation.md

@@ -24,24 +24,28 @@ does not authorize replacing an existing app's connection.
 
 ## Run the shared installer
 
-From the exact app directory, use the collected candidate and model choice:
+From the exact app directory, use the collected model choice:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 local setup --candidate <manifest.json> --defer-model --json
+npx --prefer-offline --yes copilotkit@4.24.0 local setup --defer-model --json
 ```
 
 For supplied model access, replace `--defer-model` with `--model-config <private-file>`.
+The CLI selects the latest stable release. Add `--candidate <manifest.json>` only when the
+developer gave a candidate manifest for release testing.
 Do not print or read the model file into the conversation. Do not install or manage Docker.
 The CLI supplies its pinned Helm and k3d tools and checks the available Docker budget.
 
-On a retry, run `local setup --json` with no new candidate. It uses saved inputs.
+On a retry, run the same command with the same model flag, `--defer-model` or
+`--model-config <private-file>`, and no new candidate. Setup resumes from its saved inputs.
+A Docker failure stops setup before it saves any input, so the model flag is required.
 Read blockers and the recorded failed step. Do not delete or recreate a failed stack.
 A copied app needs explicit `--share-stack`. Do not infer sharing from a copied reference.
 
 After setup reports the stack ready, run the approved connection step from that directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 local connect --approve-connection --json
+npx --prefer-offline --yes copilotkit@4.24.0 local connect --approve-connection --json
 ```
 
 Read the local `.copilotkit/project.json` for its project ID and slug. Do not run hosted
@@ -55,8 +59,28 @@ Use the existing Threads round-trip proof against this local project. Verify a r
 message, reply, and saved conversation. Installation readiness alone is not that proof.
 
 Learning needs valid model settings for this installation. A previous local installation
-proves nothing about these settings. If deferred, report “Learning configuration
-incomplete.” No Learning run is required to finish onboarding configuration.
+proves nothing about these settings. If the developer chose guided setup, wait until the
+stack is ready. Then:
+
+Ask the developer to run this command in their own terminal window, in the app directory:
+
+```text
+npx --prefer-offline --yes copilotkit@4.24.0 local setup
+```
+
+Do not give it as a `!` line, and do not run it yourself. Its guided model prompt needs a
+terminal, and a coding agent's shell has none. Without a terminal, the command stops and
+changes nothing. The prompt asks for the model and its key, and it saves them privately.
+On a running stack, it restarts only Learning. Do not ask for a model file.
+
+Say that the run continues when they reply or resume this session. Report the pause with
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard checkpoint --phase awaiting-model-credential`, end your
+turn, and wait. When the developer replies, run
+`npx --prefer-offline --yes copilotkit@4.24.0 local status --json` and read `learning.configuration`.
+
+If the model is still missing or was deferred, report “Learning configuration incomplete”
+and name the same command, run in a terminal window. No Learning run is required to finish
+onboarding configuration.
 
 Channels remain incomplete until the existing proof observes a useful reply to a real mention.
 Use the existing approved HTTPS tunnel instructions when inbound traffic needs a public URL.
@@ -66,6 +90,6 @@ must not block Threads, the dashboard, or later Learning configuration.
 If the developer cancels the connection, run `local cancel --json` from the app directory.
 Report conflict names only. Keep the stack unless deletion is separately confirmed.
 
-Continue with `npx --prefer-offline --yes copilotkit@4.23.0 onboard read credentials/settle-credentials`.
+Continue with `npx --prefer-offline --yes copilotkit@4.24.0 onboard read credentials/settle-credentials`.
 For this local route, skip the hosted selection-result checks and use the local project
 record. Continue the existing implementation and proof paths against local endpoints.

package/onboarding/prompts/fallback/best-effort.md

@@ -16,7 +16,7 @@ you stop. The friction command follows the telemetry setting the developer alrea
 so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.24.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -62,19 +62,19 @@ or frontend, stop onboarding.
 
 Use these rules for every protected-path check in this fallback:
 
-- Run `npx --prefer-offline --yes copilotkit@4.23.0 onboard audit` from the target app directory.
+- Run `npx --prefer-offline --yes copilotkit@4.24.0 onboard audit` from the target app directory.
 - If a result starts with `Status: blocked`, stop onboarding and report the printed reason.
   It proved nothing changed, so do not report a preservation failure.
 - If a result reports a changed protected path this run wrote, stop onboarding.
 - If a result reports a changed env file, this rule replaces the one above, even when this
   run wrote the file. This run asked the developer to place a
   credential there, so take the credential route rather than the external one. Accept it
-  with `npx --prefer-offline --yes copilotkit@4.23.0 onboard protect --accept-credential --path <path>`,
+  with `npx --prefer-offline --yes copilotkit@4.24.0 onboard protect --accept-credential --path <path>`,
   run the audit again, and name it in the closing report. If the command refuses because
   it names a lost variable, stop onboarding.
 - Before any proof subagent runs, a changed path that no Files changed section from this
   run names came from outside the run. Accept it by name with
-  `npx --prefer-offline --yes copilotkit@4.23.0 onboard protect --accept-external --path <path>`, run the
+  `npx --prefer-offline --yes copilotkit@4.24.0 onboard protect --accept-external --path <path>`, run the
   audit again, and name it in the closing report.
 - After a proof subagent runs, a changed path that no Files changed section from this run
   names is unsettled rather than outside the run, because the proof subagent here returns
@@ -133,16 +133,16 @@ that the selected documentation proved an inferred step.
 Record what the proof returned before you complete:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.24.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
-When the proof is complete, run `npx --prefer-offline --yes copilotkit@4.23.0 onboard complete`, carrying the
+When the proof is complete, run `npx --prefer-offline --yes copilotkit@4.24.0 onboard complete`, carrying the
 surface-check result the proof subagent returned. Pass exactly one of `--visual-check` or
 `--device-check`, matching this journey's surface:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard complete --visual-check <outcome>
-npx --prefer-offline --yes copilotkit@4.23.0 onboard complete --device-check <outcome>
+npx --prefer-offline --yes copilotkit@4.24.0 onboard complete --visual-check <outcome>
+npx --prefer-offline --yes copilotkit@4.24.0 onboard complete --device-check <outcome>
 ```
 
 `--visual-check` is for a web frontend and takes `performed`, `skipped-no-browser-tool`, or

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

@@ -18,7 +18,7 @@ without exposing secrets.
 Before you spawn the implementation subagent, take the authorized list from the CLI:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.24.0 onboard audit
 ```
 
 From its result, copy the paths under `Authorized to modify:`. A passed or failed audit with
@@ -37,7 +37,7 @@ still go on the record. Name the file and why the work needs it, then end your t
 for the developer's answer. If they allow it, record their answer before any edit:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.24.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Continue only when the result starts with `Status: passed`. Run the audit again, take the
@@ -49,7 +49,7 @@ feature stop route below.
 After validation and each repair, run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.24.0 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to modify:` is
@@ -60,7 +60,7 @@ with the implementation subagent's `Files changed` section. If that section does
 the path, accept the developer's external change:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard protect --accept-external --path <path>
+npx --prefer-offline --yes copilotkit@4.24.0 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -73,11 +73,11 @@ Run the audit again after each accepted change. If it still fails, or starts
 with `Status: blocked`, route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.24.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.23.0 onboard read feature/a2ui/proof`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read feature/a2ui/proof`.

package/onboarding/prompts/feature/a2ui/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.23.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.24.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.
@@ -33,7 +33,7 @@ you plan. Run `onboard protect` again from the target app directory: on the same
 prints the baseline the run already holds.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard protect
+npx --prefer-offline --yes copilotkit@4.24.0 onboard protect
 ```
 
 Then have one read-only subagent repeat the inspection for the findings above, and wait
@@ -62,11 +62,11 @@ one.
 After approval, record each approved path before implementation:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --prefer-offline --yes copilotkit@4.24.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
 ```
 
 If an approved path changed after capture and no implementation step has run, add
 `--with-prior-change`. Continue only when every result starts with `Status: passed`. Do not
 authorize a path the approved plan did not list.
 
-Then run `npx --prefer-offline --yes copilotkit@4.23.0 onboard read feature/a2ui/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.24.0 onboard read feature/a2ui/implement`.

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

@@ -27,7 +27,7 @@ still go on the record. Name the file and why the fix needs it, then end your tu
 for the developer's answer. If they allow it, record their answer before any edit:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.24.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Continue only when the result starts with `Status: passed`. Run the audit again, take the
@@ -40,11 +40,11 @@ Report the outcome of each attempt as it ends, before any repair. The command co
 attempts and the repairs:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.24.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Use `passed` only for a proved A2UI surface, `failed` for an attempted proof that failed,
-and `skipped` when the proof could not run. Then run `npx --prefer-offline --yes copilotkit@4.23.0 onboard audit`.
+and `skipped` when the proof could not run. Then run `npx --prefer-offline --yes copilotkit@4.24.0 onboard audit`.
 Continue only when it starts with `Status: passed`.
 
 If the audit fails, never repair, reset, or revert a protected path. Compare each named path
@@ -59,9 +59,9 @@ the path and the change the audit reports. Run the audit again after each accept
 If the audit still fails, or starts with `Status: blocked`, route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.24.0 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --prefer-offline --yes copilotkit@4.23.0 onboard read feature/complete` with the actual browser-proof
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read feature/complete` with the actual browser-proof
 outcome.