copilotkit 4.28.0 → 4.29.0

package/onboarding/index.json

@@ -1,5 +1,5 @@
 {
-  "graphTree": "7638f7b001415b1dbd5bdd5204b9c296810439f7",
+  "graphTree": "097fa21703ca2deadf60b9e0f0ce9e895160c2ea",
   "intentRoots": {
     "add-a2ui": "feature/a2ui/start",
     "add-chat-suggestions": "feature/chat-suggestions/start",
@@ -9,7 +9,7 @@
     "add-rich-threads": "feature/rich-threads/start",
     "add-voice": "feature/voice/start"
   },
-  "packageSpec": "copilotkit@4.28.0",
+  "packageSpec": "copilotkit@4.29.0",
   "root": "authenticate/start",
   "prompts": [
     {

package/onboarding/prompts/authenticate/start.md

@@ -6,15 +6,16 @@ This run executes the CopilotKit CLI through `npx`.
 It spawns read-only inspection subagents inside the target project. It sends checkpoints
 and optional friction reports to CopilotKit under the developer's telemetry setting. It
 reads nothing outside the project
-directory. It changes files only after writing the plan, and asks before any change the
-plan says needs the developer's approval. CopilotKit
+directory. In an existing project, it changes files only after writing the plan, and asks
+before any change the plan says needs the developer's approval. An empty folder gets a
+new app. CopilotKit
 Intelligence has a free Developer plan, and this run needs no paid subscription.
 
 ## Command approvals
 
 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.28.0"]`.
+`["npx", "--prefer-offline", "--yes", "copilotkit@4.29.0"]`.
 
 <!-- sandboxed-harness -->
 
@@ -30,8 +31,18 @@ prefix covers every CLI call. Say then that the install, the dev servers, `curl`
 Never add or edit a permission rule or a settings file yourself. That choice belongs to
 the developer.
 
+<!-- antigravity-harness -->
+
+Antigravity's "always allow" saves only the one full command, so it does not cover the
+next CLI call. Tell the developer that one entry covers every CLI call, and that the
+choice is theirs. The entry goes in `/permissions`, or in `permissions.allow` in
+`~/.gemini/antigravity-cli/settings.json`:
+`command(npx --prefer-offline --yes copilotkit@4.29.0)`.
+
+<!-- /antigravity-harness -->
+
 If your harness refuses a CLI call without asking the developer, do not retry it or run it
-another way. Report the pause: `npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer`.
+another way. Report the pause: `npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about harness-permission`.
 Name the refused command, ask the developer to approve it or to switch to a
 mode that asks them, and end your turn. When they answer, run it once more.
 That refusal is a pause, not a stop.
@@ -45,7 +56,7 @@ does not see your tool output, and the welcome comes later, with the setup messa
 Then run this:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
+npx --prefer-offline --yes copilotkit@4.29.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`.
@@ -79,11 +90,11 @@ tool output.
 If you stop this run at any point, send one short report before you stop. This includes
 unexpected stops and stops caused by your harness.
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
-Report the pause: `npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer`.
+Report the pause as the prompt that asks the question says.
 A terminal that sends the report itself, or says to file none, overrides this.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.29.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -101,15 +112,15 @@ rule that stopped you says next: send the report, then stop.
 Take the local route only when the developer already asked to run CopilotKit locally,
 with Docker, or self-hosted: in their request, the copied prompt, or a later reply, or
 when this run already recorded local. Then run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read deployment/choose-local` instead.
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read deployment/choose-local` instead.
 
 Otherwise keep managed. Do not ask the developer to choose. Run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard deployment --choice managed`, then continue with
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard deployment --choice managed`, then continue with
 “Check sign-in”. If it refuses because of a local stack, take the local route.
 
 ## Check sign-in
 
-Run `npx --prefer-offline --yes copilotkit@4.28.0 login --json --onboarding` before any project work. It checks the
+Run `npx --prefer-offline --yes copilotkit@4.29.0 login --json --onboarding` before any project work. It checks the
 session and 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.
 
@@ -119,17 +130,18 @@ Read each JSON Lines record as it arrives:
    existing session is valid.
 2. If the process emits `authentication_url`, the developer must sign in. The process is
    still running.
-3. The CLI does not open the page. The first `action_required` record carries a `message`:
-   why to sign in, then the link and the code. Write that `message` in your own reply, word
-   for word, and add nothing else. The developer does not see your tool output. Do not open
-   the page yourself: the developer opens it from your message. Then report the pause with
-   `npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer` and end your
+3. When it can, the CLI opens the sign-in page in the default browser. The first
+   `action_required` record carries a `message`: why to sign in, whether the page opened,
+   then the link and the code. Write that `message` in your own reply, word for word, and add
+   nothing else. The developer does not see your tool output. Do not open the page yourself.
+   Then report the pause with
+   `npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about sign-in` and end your
    turn. Until the developer says they signed in, send them nothing more. When the research or
    another helper returns, record what it found and end your turn without a message. Your own
    built-in browser does not carry the session the developer already signed in with,
    so do not use it.
    A later `authentication_url` record with `"renewed": true` means the earlier code expired.
-   Write its `message` the same way.
+   The CLI opens its page too, when it can. Write its `message` the same way.
 4. Keep monitoring the same login process. Do not start a second login command.
 5. Go past the research only after that same process emits `type: completed`.
 6. On `type: failed` with `reason: expired` or `reason: renewal_failed`, ask once whether to
@@ -138,11 +150,11 @@ Read each JSON Lines record as it arrives:
 7. If that process emits `type: failed`, report the error and stop onboarding. On
    `reason: repeated_expiry`, rerun `login` with `--force` only if the developer asks.
 
-On `type: completed`, run `npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase sign-in-settled`
+On `type: completed`, run `npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase sign-in-settled`
 before you continue.
 
 If your harness ends the login process or your turn before the process emits
-`type: completed` or `type: failed`, that is a pause, not a failed sign-in. Report the pause: `npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer`.
+`type: completed` or `type: failed`, that is a pause, not a failed sign-in. Report the pause: `npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about sign-in`.
 If the process
 still runs, end your turn and wait for the developer to say they signed in, then read the
 same process. If the process ended without emitting `type: failed`, run
@@ -154,9 +166,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.28.0 onboard read research/gather`. If this run already
+runs: `npx --prefer-offline --yes copilotkit@4.29.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.28.0 onboard read stopped/run-failed`. It does not judge
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read stopped/run-failed`. It does not judge
 this project's stack.

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.28.0 verify --round-trip`, which sends a
+fifth item is proved by `npx --prefer-offline --yes copilotkit@4.29.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.28.0 onboard read credentials/finalize-plan`.
+Then run `npx --prefer-offline --yes copilotkit@4.29.0 onboard read credentials/finalize-plan`.
 
 If a selected page does not load after the second method, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read unsupported/no-validated-path`.

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

@@ -1,14 +1,14 @@
 # Select the Intelligence project
 
 For a recorded local choice, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read deployment/local-evaluation`.
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read deployment/local-evaluation`.
 That path connects the local project with the approval the setup message took.
 Skip hosted selection.
 Keep the implementation and feature-proof requirements.
 
 Use the selected framework, frontend, model vendor, model, documentation URLs, and
 repository findings. When the framework, frontend or vendor is not in your context, read it
-from `npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers`, and do not ask again. On a conversion, use the values the conversion prompt recorded, and
+from `npx --prefer-offline --yes copilotkit@4.29.0 onboard setup-answers`, and do not ask again. On a conversion, use the values the conversion prompt recorded, and
 ask no framework or frontend question. Do not change application code in this phase. Do
 not read, show, store, or request a secret value.
 
@@ -20,7 +20,7 @@ reason only when it names something in the developer's own project. Do not ask a
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about setup-answers
 ```
 
 ## Record the audit cell
@@ -38,7 +38,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.28.0 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend> --model-vendor <model-vendor> --model-vendor-choice <model-vendor-choice>
+npx --prefer-offline --yes copilotkit@4.29.0 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend> --model-vendor <model-vendor> --model-vendor-choice <model-vendor-choice>
 ```
 
 `<model-vendor>` is `openai`, `anthropic`, `google`, `openai-compatible`, or `other`.
@@ -55,7 +55,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.28.0 onboard credentials --json
+npx --prefer-offline --yes copilotkit@4.29.0 onboard credentials --json
 ```
 
 Every credential this run writes goes to the environment path: the target's `.env`, or
@@ -80,7 +80,7 @@ the CLI kept: run `--create` with `question.recorded.create`, or `--project` wit
 project answer `setup/questions` gave you. A new project with no recorded name takes
 `suggestedName`. Ask the developer only when `question.taken` or `question.notFound` is
 present, or when no answer was recorded. When they then give another project, record it
-with `npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers --create <name>` or
+with `npx --prefer-offline --yes copilotkit@4.29.0 onboard setup-answers --create <name>` or
 `--project <slug>`.
 
 `project-name` means that no project is bound here, so creating a project for this
@@ -93,7 +93,7 @@ unless the developer says that it is this app's.
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about project-name
 ```
 
 If no developer answers, create with the derived name in `suggestedName`. Never select a
@@ -102,9 +102,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.28.0 onboard credentials --create <name> \
+npx --prefer-offline --yes copilotkit@4.29.0 onboard credentials --create <name> \
   --runtime-url http://localhost:<port>/api/copilotkit --json
-npx --prefer-offline --yes copilotkit@4.28.0 onboard credentials --project <slug-or-id> \
+npx --prefer-offline --yes copilotkit@4.29.0 onboard credentials --project <slug-or-id> \
   --runtime-url http://localhost:<port>/api/copilotkit --json
 ```
 
@@ -116,12 +116,12 @@ show only what they asked for, and do not order it by creation time:
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about which-project
 ```
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 project list --json
-npx --prefer-offline --yes copilotkit@4.28.0 project list --search <query> --json
+npx --prefer-offline --yes copilotkit@4.29.0 project list --json
+npx --prefer-offline --yes copilotkit@4.29.0 project list --search <query> --json
 ```
 
 `app-directory` means that the key landed where no app reads it. Pick the directory in
@@ -130,7 +130,7 @@ the `--project` command from there with `project.slug`. Do not copy or link the
 
 `env-file-exposed` means that git tracks the env file the key goes into, or does not
 ignore it. So nothing was written. Read `envFile` from
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers`, which keeps the developer's answer to
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard setup-answers`, which keeps the developer's answer to
 that line in the setup message: `approved` approves the change the line asks for,
 `alternative` chose `question.alternative`, and `declined` declined both. Act on it without
 asking again. An accepting reply to the setup message never approves a line with
@@ -144,7 +144,7 @@ run the same command again with `question.alternative.rerun` added. The CLI adds
 If they approve the untrack, add
 `question.ignoreLine` to `question.ignoreFile`. If `question.untrack` is present, run it
 too. Or the developer does both. Report the pause with
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer`, end your
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about env-file-tracked`, end your
 turn, and wait for the answer. Then run the same command again. Write the key only to
 `question.file`, or to `question.alternative.file` by rerunning with
 `question.alternative.rerun`.
@@ -160,4 +160,4 @@ turn, and wait for the answer. Then run the same command again. Write the key on
   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.28.0 onboard read credentials/settle-credentials`.
+Then run `npx --prefer-offline --yes copilotkit@4.29.0 onboard read credentials/settle-credentials`.

package/onboarding/prompts/credentials/plan.md

@@ -1,6 +1,6 @@
 # Select the agent framework
 
-First run `npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers`. It prints the answers that
+First run `npx --prefer-offline --yes copilotkit@4.29.0 onboard setup-answers`. It prints the answers that
 `setup/questions` recorded, even after this conversation lost them. Use its `framework` and
 its `vendor`, with `vendor.choice`, `vendor.baseUrl` and `vendor.modelId`. That node asked
 the developer, so ask nothing here. A run that proved its existing agent, frontend, and
@@ -25,7 +25,7 @@ and Google come in a later release, and offer the Built-in CopilotKit agent if t
 them now. Record the answers with
 `onboard setup-answers --framework <name> --vendor <vendor> --vendor-choice <choice>`.
 Report the pause with
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer`, then end your
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about stack-choice`, then end your
 turn and wait for the answer. A route that records no framework or vendor on purpose is not
 this case: an empty project with Slack or Microsoft Teams, a "Project-defined" vendor, or
 "The agent's own" vendor.
@@ -49,7 +49,7 @@ Microsoft Teams docs page, do not ask the framework question. So does an empty p
 whose frontend `setup/questions` recorded as Slack or Microsoft Teams: it recorded no
 framework. 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.28.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read frontend/plan`.
 
 ## Route on the recorded framework
 
@@ -58,28 +58,28 @@ chosen: `developer`, `default`, or `existing`. The framework route uses this ven
 
 Use exactly one matching internal route:
 
-1. AG2: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/ag2`
-2. Agno: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/agno`
-3. Built-in CopilotKit agent: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/built-in`
-4. Claude Agent SDK Python: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/claude-sdk-python`
-5. Claude Agent SDK TypeScript: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/claude-sdk-typescript`
-6. CrewAI Flows: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/crewai-flows`
-7. Custom agent: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/custom-ag-ui`
-8. Deep Agents: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/deep-agents`
-9. LangGraph Python: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/langgraph-python`
-10. LangGraph FastAPI: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/langgraph-fastapi`
-11. LangGraph TypeScript: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/langgraph-typescript`
-12. LlamaIndex: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/llamaindex`
-13. ADK: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/google-adk`
-14. Microsoft Agent Framework Python: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/ms-agent-python`
-15. Microsoft Agent Framework .NET: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/ms-agent-dotnet`
-16. Mastra: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/mastra`
-17. MS Agent Harness .NET: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/ms-agent-harness-dotnet`
-18. Pydantic AI: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/pydantic-ai`
-19. Strands Agents Python: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/strands-python`
-20. Strands Agents TypeScript: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/strands-typescript`
+1. AG2: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/ag2`
+2. Agno: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/agno`
+3. Built-in CopilotKit agent: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/built-in`
+4. Claude Agent SDK Python: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/claude-sdk-python`
+5. Claude Agent SDK TypeScript: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/claude-sdk-typescript`
+6. CrewAI Flows: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/crewai-flows`
+7. Custom agent: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/custom-ag-ui`
+8. Deep Agents: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/deep-agents`
+9. LangGraph Python: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/langgraph-python`
+10. LangGraph FastAPI: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/langgraph-fastapi`
+11. LangGraph TypeScript: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/langgraph-typescript`
+12. LlamaIndex: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/llamaindex`
+13. ADK: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/google-adk`
+14. Microsoft Agent Framework Python: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/ms-agent-python`
+15. Microsoft Agent Framework .NET: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/ms-agent-dotnet`
+16. Mastra: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/mastra`
+17. MS Agent Harness .NET: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/ms-agent-harness-dotnet`
+18. Pydantic AI: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/pydantic-ai`
+19. Strands Agents Python: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/strands-python`
+20. Strands Agents TypeScript: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read framework/strands-typescript`
 
 An agent in any other framework takes route 7, whether or not it speaks AG-UI. So does a
 new agent on a framework that is not listed. If the developer declines route 7 and every
 listed framework, keep their current agent and run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read unsupported/no-validated-path`.

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

@@ -21,10 +21,10 @@ 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.28.0 onboard credentials --model-key <variable> --json
+npx --prefer-offline --yes copilotkit@4.29.0 onboard credentials --model-key <variable> --json
 ```
 
-Run `npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers` for the key answer the setup
+Run `npx --prefer-offline --yes copilotkit@4.29.0 onboard setup-answers` for the key answer the setup
 message recorded. If it holds `key.file`, add `--env-path <key.file>` to the first check.
 When the framework node names another env file for the credential, add
 `--env-path <file>`. When the agent runs as its own service, such as a remote AG-UI agent,
@@ -41,17 +41,17 @@ never prints a value. Read `status`:
   `Files the run writes itself`.
   The developer's answer to the key file line in the setup questions is their consent to
   the copy. After the run shows the plan, copy the key with the command that `next` names. It has this form:
-  `npx --prefer-offline --yes copilotkit@4.28.0 onboard credentials --model-key <variable> --env-path <file> --copy-to <env file> --json`.
+  `npx --prefer-offline --yes copilotkit@4.29.0 onboard credentials --model-key <variable> --env-path <file> --copy-to <env file> --json`.
   `<env file>` is `environmentPath`, never the tracked `.env` of a run that chose
   `question.alternative.file`. It writes the key without printing it. 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.28.0 onboard credentials --model-key <variable> --env-path <file> --copy-to <env file>`.
+  `! cd <app directory> && npx --prefer-offline --yes copilotkit@4.29.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.
   Report the pause with
-  `npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-model-credential`,
+  `npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-model-credential`,
   end your turn, and wait. 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
@@ -69,7 +69,7 @@ never prints a value. Read `status`:
   The `reason` `compatible-base-url-missing` or `key-not-openai` means that the key belongs
   to an OpenAI-compatible provider, but no file names its base URL, so nothing was sent.
   Ask the developer for the provider's base URL, record it with
-  `npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers --vendor openai-compatible --base-url <url> --model-id <id>`,
+  `npx --prefer-offline --yes copilotkit@4.29.0 onboard setup-answers --vendor openai-compatible --base-url <url> --model-id <id>`,
   and run this step again.
 - `needs-developer` with `question.reason` `local-endpoint-no-key`: the base URL is a local
   server that needs no key, such as Ollama or LM Studio. The OpenAI SDKs refuse an empty
@@ -113,4 +113,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.28.0 onboard read credentials/write-plan`.
+Then run `npx --prefer-offline --yes copilotkit@4.29.0 onboard read credentials/write-plan`.

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

@@ -6,12 +6,10 @@ answer only when the plan makes a change that needs approval or still needs the
 
 ## If you stop in this phase
 
-Name the exact file, value, or check that stopped you, then send one short report. The
-friction command follows the telemetry setting the developer already chose, so it needs no
-separate question.
+Name the exact file, value, or check that stopped you, then send one short report.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.29.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -38,11 +36,10 @@ so either mount works. Keep the mount the project already has, together with its
 setting: `mode: "single-route"` with `useSingleEndpoint` true or unset, or the full route
 subtree with `useSingleEndpoint={false}`. For a new mount, use the full route subtree below.
 
-Below 1.73.1, mount the runtime on the full route subtree. An Intelligence runtime serves
-its runs over two REST paths: `/agent/<id>/run` and `/agent/<id>/connect`, and the
-Intelligence client of those versions addresses them for every transport the provider
-selects. A runtime mounted with `mode: "single-route"` answers every other call. It
-returns not found for every run and every thread reopen. The other fix is an upgrade of
+Below 1.73.1, mount the runtime on the full route subtree. The Intelligence client of those
+versions calls `/agent/<id>/run` and `/agent/<id>/connect` for every transport, so a
+runtime mounted with `mode: "single-route"` returns not found for every run and every
+thread reopen. The other fix is an upgrade of
 the CopilotKit packages to 1.73.1 or later, which the plan can name as its dependency
 upgrade. The round-trip check passes with either mount, so nothing later in this run
 catches the mistake.
@@ -58,7 +55,7 @@ proof subagents:
 - https://docs.copilotkit.ai/backend/runtime-endpoints.md
 - https://docs.copilotkit.ai/intelligence/managed-intelligence-platform.md
 
-Fetch them together with the pages already selected rather than on their own.
+Fetch them with the pages already selected, not on their own.
 
 The planning subagent adds a threads drawer from the selected drawer page. If no drawer
 page is selected yet, add the one for the frontend selected above to the same list:
@@ -73,25 +70,37 @@ When you start a subagent in the background, tell the developer in one sentence
 does. Then send nothing more until it returns.
 
 Spawn one planning subagent. Tell it to run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read subagent/create-plan` first and follow the
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read subagent/create-plan` first and follow the
 prompt it returns. Tell it to return at once, and say so, if that read is refused or fails,
-and not to wait for an approval. If it returns that way, stop that subagent. Run the same
-command yourself, then spawn a fresh subagent with the returned prompt and the same handoff.
+and not to wait for an approval.
 Give it the repository findings, selected framework, frontend, model, credential variable
 names, selected documentation URLs, and documentation policy. Give it each finding that the
 framework route told you to record, such as how the agent connects or a `clone()` finding.
-Some of those rules, such as the `clone()` override, are on no documentation page. On a
+On a
 conversion, also give it the frozen criterion. Give the planning subagent the paths that
 had uncommitted changes when the run started, from the repository findings, and the
 `backup` result from `onboard credentials`. Also give it the JSON that
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers` prints, so the plan does not ask again
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard setup-answers` prints, so the plan does not ask again
 for a change the setup message settled. Wait for the subagent to finish.
 
+If only its closing `subagent-returned` checkpoint was refused, the subagent finished.
+Record no `refused` return and spawn nothing: run that checkpoint yourself, with the result
+the subagent returned.
+
+If the subagent returns because its harness refused any other command, record that return:
+
+```text
+npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase subagent-returned --brief create-plan --result refused
+```
+
+Then run that command yourself, from the directory the subagent named. Spawn at most one
+fresh subagent for each refused command, with the same handoff and that command's result.
+If the fresh subagent is refused a command too, spawn no other. Follow the brief yourself.
+
 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.28.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
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read stopped/run-failed`. 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
 prompt instead. Do not show a
@@ -150,8 +159,7 @@ What I will change:
 `onboard restore` puts back what the backup holds.
 ```
 
-An upgrade to a working install is the developer's call. Do not upgrade a dependency the
-plan does not name.
+Do not upgrade a dependency the plan does not name.
 
 ## Go on, or wait for one answer
 
@@ -170,7 +178,7 @@ approval or something blocks you. Before you end your turn to
 wait for the answer, report the pause, each time you show the plan:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-plan-approval --reason <reasons>
+npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-plan-approval --reason <reasons>
 ```
 
 `--reason` names why the plan stopped, one reason for each kind of line that needs approval, separated
@@ -196,18 +204,18 @@ If the plan carries a missing model key, the run cannot build without it, so wai
 even when `Changes that need your approval` says `none`. Name the variable and its file in the plan message,
 and ask the developer to add the key. Ask the approval question in the same message, if
 there is one. When the plan has no change that needs approval, report the pause with
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-model-credential`
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-model-credential`
 instead. When the developer answers, run the same `onboard credentials --model-key` check
 again. On `ready`, continue. If the key is still missing, ask the developer `question.ask`
 in those words. Report the pause with
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-model-credential`, end
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-model-credential`, end
 your turn, and run the check again when they answer.
 
 When the plan needs no answer, or after the developer answers, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read implementation/build-and-validate`.
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read implementation/build-and-validate`.
 
 If no exact supported path or documentation URL exists, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read unsupported/no-validated-path`.
 
 ## If the developer replies **stop**
 
@@ -217,10 +225,10 @@ run added stay, and that the restore also undoes any edit the developer made to
 during the run. Before you end your turn to wait for the answer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about restore-files
 ```
 
-If they say yes, run `npx --prefer-offline --yes copilotkit@4.28.0 onboard restore --force`. The run has
+If they say yes, run `npx --prefer-offline --yes copilotkit@4.29.0 onboard restore --force`. The run has
 not ended yet, so without `--force` the restore cannot tell the run's edits from the
 developer's and skips every changed file. Show the developer what it restored and what it
 skipped. If they say no, change nothing. Then send the stop report from the start of this

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

@@ -9,15 +9,15 @@ A local request can arrive after this run created a hosted project: `init --crea
 Tell the developer that this run already created a hosted project, so it stays managed.
 Return to the step you were on.
 
-First run `npx --prefer-offline --yes copilotkit@4.28.0 local --help`. If it does not list `setup`
+First run `npx --prefer-offline --yes copilotkit@4.29.0 local --help`. If it does not list `setup`
 ("Configure model access and install or resume the local stack"), this release has no
 local evaluation. Tell the developer so, and keep managed. If this run has not recorded
-managed yet, run `npx --prefer-offline --yes copilotkit@4.28.0 onboard deployment --choice managed`.
+managed yet, run `npx --prefer-offline --yes copilotkit@4.29.0 onboard deployment --choice managed`.
 Then return to “Check sign-in” in the start prompt. If a login process from it still
 runs, keep reading that process and start no second one. Otherwise record the choice:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard deployment --choice local
+npx --prefer-offline --yes copilotkit@4.29.0 onboard deployment --choice local
 ```
 
 Explain these conditions before sign-in:
@@ -48,10 +48,10 @@ 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.28.0 local setup`, run in a terminal in the app directory.
+   `npx --prefer-offline --yes copilotkit@4.29.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.28.0 local setup` in their own terminal window, in the app
+   `npx --prefer-offline --yes copilotkit@4.29.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
@@ -71,7 +71,7 @@ If the managed sign-in message was already sent, send this once and no other sig
 message: “You asked to run it locally, so this project gets no managed CopilotKit project.
 Signing in only gets the renewable evaluation license.”
 
-Otherwise run `npx --prefer-offline --yes copilotkit@4.28.0 login --json`. Follow the streaming sign-in
+Otherwise run `npx --prefer-offline --yes copilotkit@4.29.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.
 When the first authentication URL arrives, send this message in place of the managed
@@ -79,9 +79,9 @@ sign-in message: “Sign in to get the renewable evaluation license. Your local
 will use CLI approval.”
 On failed or declined sign-in, take the failure path below.
 
-After sign-in completes, report it: `npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase sign-in-settled`.
+After sign-in completes, report it: `npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase sign-in-settled`.
 Then continue with
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read research/gather`, unless research already started.
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read research/gather`, unless research already started.
 If it already started, return to the step you were on. `starter/clone` and
 `credentials/finalize-plan` each have a branch for a recorded local choice.
 Keep the local choice and collected paths in the run's plan and worker context.
@@ -89,4 +89,4 @@ Keep the local choice and collected paths in the run's plan and worker context.
 ## Failure path
 
 If sign-in fails or is declined, stop before cluster creation.
-Run `npx --prefer-offline --yes copilotkit@4.28.0 onboard read stopped/run-failed`.
+Run `npx --prefer-offline --yes copilotkit@4.29.0 onboard read stopped/run-failed`.