copilotkit 4.22.0 → 4.23.1

package/onboarding/prompts/feature/rich-threads/implement.md

@@ -2,7 +2,7 @@
 
 Delegate implementation to one subagent with the approved plan and fetched official guides.
 If repository evidence does not prove an existing valid Intelligence selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 login --json` and follow its single streaming session. Then
+`npx --prefer-offline --yes copilotkit@4.23.1 login --json` and follow its single streaming session. Then
 list projects, show the developer the current/recent choices, and select or create one only
 after they choose. Require the secret-safe selection summary to confirm the project file,
 environment file, and key provisioning; never display a key. If existing configuration is
@@ -20,14 +20,14 @@ non-zero on an app that is working. Pass what `identifyUser` reads with a repeat
 It is not a defect to repair.
 
 Run focused type/test commands, then start the app and run
-`npx --prefer-offline --yes copilotkit@4.22.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
+`npx --prefer-offline --yes copilotkit@4.23.1 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
 Repair changed-file failures before continuing. Record changed paths and secret-safe
 validation evidence.
 
 Before you spawn the implementation subagent, take the authorized list from the CLI:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.23.1 onboard audit
 ```
 
 From its result, copy the paths under `Authorized to modify:`. A passed or failed audit with
@@ -46,7 +46,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.22.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.23.1 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
@@ -58,7 +58,7 @@ feature stop route below.
 After validation and each repair, run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.23.1 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to modify:` is
@@ -69,7 +69,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.22.0 onboard protect --accept-external --path <path>
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -82,11 +82,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.22.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard read feature/rich-threads/proof`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/rich-threads/proof`.

package/onboarding/prompts/feature/rich-threads/plan.md

@@ -0,0 +1,77 @@
+# Plan Rich Threads with the developer
+
+The inspection in `feature/rich-threads/start` came back and proved what this intent
+needs. This prompt turns it into a plan, asks the developer to approve it, and records the
+protected paths the plan changes. Do not change project files in this prompt.
+
+## Waits and stops
+
+The rules in `feature/rich-threads/start` still hold here.
+
+The approval is a wait for the developer. Before you end your turn to wait, report the
+pause:
+
+```text
+npx --prefer-offline --yes copilotkit@4.23.1 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.
+When the answer arrives, continue from the step that paused. If the developer asks for a
+change, show the changed plan and ask again.
+
+## What this prompt takes from the start
+
+Keep these from `feature/rich-threads/start`, and give them to every subagent:
+
+- the protected path list that `onboard protect` printed, and
+- the paths and findings the inspection returned: the runtime route, CopilotKit provider
+  and chat, agent id, current thread UI or headless API, authentication boundary,
+  server-side user identity source, project configuration (presence only), test and dev
+  commands, and the round trip.
+
+If you do not hold them, as after `onboard resume` in a new session, get them back before
+you plan. Run `onboard protect` again from the target app directory: on the same run it
+prints the baseline the run already holds.
+
+```text
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect
+```
+
+Then have one read-only subagent repeat the inspection for the findings above, and wait
+for it. It changes no files.
+
+## Plan the change
+
+Fetch the current official guides before planning:
+https://docs.copilotkit.ai/threads.md
+https://docs.copilotkit.ai/threads-lifecycle.md
+https://docs.copilotkit.ai/intelligence/quickstart.md
+https://docs.copilotkit.ai/auth.md
+https://docs.copilotkit.ai/prebuilt-components/copilot-threads-drawer.md
+Retry unavailable pages a second way. Do not infer an identity from a browser display name or
+use a client-supplied identifier as the server-side user identity. `identifyUser` names an
+already-authenticated caller. It is not the authentication gate, and the auth page lists the
+thread routes that do not resolve the caller through it and must be guarded separately.
+
+Re-use a valid existing Intelligence project and credential when repository evidence proves
+one. If Intelligence is missing, do not create a project or sign in yet: show a plan first.
+The plan must name the documented Intelligence runtime wiring, server-side `identifyUser`,
+catch-all thread routes, the selected UI (drawer or existing headless UI), preserved behavior,
+tests, and a reload/reopen proof. Ask for approval as its own question.
+
+The plan must list every protected path it needs to change under `Authorization requested`,
+with one sentence explaining why. Write `None` when it needs none. Authorization covers
+changing a protected path, not removing it, so the plan must not delete, move, or rename
+one.
+
+After approval, record each approved path before implementation:
+
+```text
+npx --prefer-offline --yes copilotkit@4.23.1 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.1 onboard read feature/rich-threads/implement`.

package/onboarding/prompts/feature/rich-threads/proof.md

@@ -22,7 +22,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.22.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.23.1 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
@@ -35,12 +35,12 @@ 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.22.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.23.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Use `passed` only for proved persistence and reopen, `failed` for an attempted proof that
 failed, and `skipped` when the proof could not run. Then run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard audit`. Continue only when it starts with
+`npx --prefer-offline --yes copilotkit@4.23.1 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
@@ -55,9 +55,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.22.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read feature/complete` with the actual browser
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/complete` with the actual browser
 outcome.

package/onboarding/prompts/feature/rich-threads/start.md

@@ -20,13 +20,13 @@ carry on. Keep a read-only assignment read-only. If no subagent works at all, re
 once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.23.1 onboard checkpoint --phase delegation-unavailable
 ```
 
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.23.1 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.
@@ -36,7 +36,7 @@ If you stop this run, send one short report before you stop. The friction comman
 the telemetry setting the developer already chose, so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.23.1 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -50,7 +50,7 @@ one scoped fix, and sends the report itself when no fix is approved.
 Before any subagent or project process runs, capture the developer's existing work:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard protect
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -65,46 +65,21 @@ the current frontend-to-runtime-to-agent round trip and inspect `/info`.
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.23.1 onboard checkpoint --phase research-returned
 ```
 
 If the inspection did not prove the baseline this intent extends, stop here without
 changing files:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/stop
 ```
 
-Fetch the current official guides before planning:
-https://docs.copilotkit.ai/threads.md
-https://docs.copilotkit.ai/threads-lifecycle.md
-https://docs.copilotkit.ai/intelligence/quickstart.md
-https://docs.copilotkit.ai/auth.md
-https://docs.copilotkit.ai/prebuilt-components/copilot-threads-drawer.md
-Retry unavailable pages a second way. Do not infer an identity from a browser display name or
-use a client-supplied identifier as the server-side user identity. `identifyUser` names an
-already-authenticated caller; it is not the authentication gate, and the auth page lists the
-thread routes that do not resolve the caller through it and must be guarded separately.
-
-Re-use a valid existing Intelligence project and credential when repository evidence proves
-one. If Intelligence is missing, do not create a project or sign in yet: show a plan first.
-The plan must name the documented Intelligence runtime wiring, server-side `identifyUser`,
-catch-all thread routes, the selected UI (drawer or existing headless UI), preserved behavior,
-tests, and a reload/reopen proof. Ask for approval separately.
-
-The plan must list every protected path it needs to change under `Authorization requested`,
-with one sentence explaining why. Write `None` when it needs none. Authorization covers
-changing a protected path, not removing it, so the plan must not delete, move, or rename
-one.
-
-After approval, record each approved path before implementation:
+When the inspection proved what this intent needs, read the next prompt now, in this turn:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/rich-threads/plan
 ```
 
-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.22.0 onboard read feature/rich-threads/implement`.
+That prompt holds the plan, the developer's approval, and the paths the plan changes.
+Do not write the plan or change project files in this prompt.

package/onboarding/prompts/feature/stop.md

@@ -20,7 +20,7 @@ a `start` with no `--run` reprints the id this stopped run already holds, and on
 covering both reads as one run that did two different things.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard start --run <new-12-character-id>
+npx --prefer-offline --yes copilotkit@4.23.1 onboard start --run <new-12-character-id>
 ```
 
 Do not read a generic onboarding node from this run. A feature run and a generic run are
@@ -48,7 +48,7 @@ put to them, stop here and send the report below.
 If they approve it, make that one fix and nothing else. Then come back into this run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard resume --message "<approval>"
+npx --prefer-offline --yes copilotkit@4.23.1 onboard resume --message "<approval>"
 ```
 
 Put the developer's approval in `--message`, in one or two sentences: the fix they
@@ -69,7 +69,7 @@ Send one short report. The friction command follows the telemetry setting the de
 already chose, so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.23.1 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.

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

@@ -14,7 +14,7 @@ voice proof. Record changed paths and validation results.
 Before you spawn the implementation subagent, take the authorized list from the CLI:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.23.1 onboard audit
 ```
 
 From its result, copy the paths under `Authorized to modify:`. A passed or failed audit with
@@ -33,7 +33,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.22.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.23.1 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
@@ -45,7 +45,7 @@ feature stop route below.
 After validation and each repair, run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.23.1 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to modify:` is
@@ -56,7 +56,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.22.0 onboard protect --accept-external --path <path>
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -69,11 +69,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.22.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard read feature/voice/proof`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/voice/proof`.

package/onboarding/prompts/feature/voice/plan.md

@@ -0,0 +1,74 @@
+# Plan voice input with the developer
+
+The inspection in `feature/voice/start` came back and proved what this intent needs. This
+prompt turns it into a plan, asks the developer to approve it, and records the protected
+paths the plan changes. Do not change project files in this prompt.
+
+## Waits and stops
+
+The rules in `feature/voice/start` still hold here.
+
+The approval is a wait for the developer. Before you end your turn to wait, report the
+pause:
+
+```text
+npx --prefer-offline --yes copilotkit@4.23.1 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.
+When the answer arrives, continue from the step that paused. If the developer asks for a
+change, show the changed plan and ask again.
+
+## What this prompt takes from the start
+
+Keep these from `feature/voice/start`, and give them to every subagent:
+
+- the protected path list that `onboard protect` printed, and
+- the paths and findings the inspection returned: the runtime route, provider and chat
+  composer, current agent, provider credential variable names (presence only), package
+  versions, browser permissions approach, test and dev commands, and the round trip that
+  `verify` proved.
+
+If you do not hold them, as after `onboard resume` in a new session, get them back before
+you plan. Run `onboard protect` again from the target app directory: on the same run it
+prints the baseline the run already holds.
+
+```text
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect
+```
+
+Then have one read-only subagent repeat the inspection for the findings above, and wait
+for it. It changes no files.
+
+## Plan the change
+
+Do not run login, select Intelligence, create a credential, read a credential value, or
+replace the existing chat/runtime. Fetch the official voice guide before planning:
+https://docs.copilotkit.ai/voice.md
+Retry it a second way if needed. Use an existing user-owned provider credential only when
+the repository proves its variable name is configured. Otherwise, explain the setup gate and
+take the feature stop route rather than writing a placeholder:
+
+```text
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/stop
+```
+
+Show a small plan for the documented transcription service, the existing composer, focused
+tests, and a microphone/canned-transcript proof. Ask for approval as its own question.
+
+The plan must list every protected path it needs to change under `Authorization requested`,
+with one sentence explaining why. Write `None` when it needs none. Authorization covers
+changing a protected path, not removing it, so the plan must not delete, move, or rename
+one.
+
+After approval, record each approved path before implementation:
+
+```text
+npx --prefer-offline --yes copilotkit@4.23.1 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.1 onboard read feature/voice/implement`.

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

@@ -21,7 +21,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.22.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.23.1 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
@@ -34,11 +34,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.22.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.23.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Use `passed` only for proved voice input, `failed` for an attempted proof that failed, and
-`skipped` when the proof could not run. Then run `npx --prefer-offline --yes copilotkit@4.22.0 onboard audit`.
+`skipped` when the proof could not run. Then run `npx --prefer-offline --yes copilotkit@4.23.1 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
@@ -53,9 +53,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.22.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read feature/complete` with the actual surface
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/complete` with the actual surface
 outcome.

package/onboarding/prompts/feature/voice/start.md

@@ -19,13 +19,13 @@ carry on. Keep a read-only assignment read-only. If no subagent works at all, re
 once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.23.1 onboard checkpoint --phase delegation-unavailable
 ```
 
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.23.1 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.
@@ -35,7 +35,7 @@ If you stop this run, send one short report before you stop. The friction comman
 the telemetry setting the developer already chose, so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.23.1 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -49,7 +49,7 @@ one scoped fix, and sends the report itself when no fix is approved.
 Before any subagent or project process runs, capture the developer's existing work:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard protect
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -59,45 +59,27 @@ approved authorization before implementation.
 Before edits, inspect the runtime route, CopilotKit provider/chat composer, current agent,
 existing provider credential variable names (presence only), package versions, browser
 permissions approach, and test/dev commands. Prove the existing OSS baseline with `/info`,
-`npx --prefer-offline --yes copilotkit@4.22.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+`npx --prefer-offline --yes copilotkit@4.23.1 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
 and a real UI request when a browser is available.
 
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.23.1 onboard checkpoint --phase research-returned
 ```
 
 If the inspection did not prove the baseline this intent extends, stop here without
 changing files:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/stop
 ```
 
-Do not run login, select Intelligence, create a credential, read a credential value, or
-replace the existing chat/runtime. Fetch the official voice guide before planning:
-https://docs.copilotkit.ai/voice.md
-Retry it a second way if needed. Use an existing user-owned provider credential only when
-the repository proves its variable name is configured; otherwise explain the setup gate and
-take the feature stop route above rather than writing a placeholder.
-
-Show a small plan for the documented transcription service, the existing composer, focused
-tests, and a microphone/canned-transcript proof. Ask for approval separately.
-
-The plan must list every protected path it needs to change under `Authorization requested`,
-with one sentence explaining why. Write `None` when it needs none. Authorization covers
-changing a protected path, not removing it, so the plan must not delete, move, or rename
-one.
-
-After approval, record each approved path before implementation:
+When the inspection proved what this intent needs, read the next prompt now, in this turn:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/voice/plan
 ```
 
-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.22.0 onboard read feature/voice/implement`.
+That prompt holds the plan, the developer's approval, and the paths the plan changes.
+Do not write the plan or change project files in this prompt.

package/onboarding/prompts/framework/ag2.md

@@ -31,7 +31,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, and the A2UI documentation gap.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/agno.md

@@ -34,7 +34,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, the documented dependencies and adapter, and the context documentation gap.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.

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

@@ -29,7 +29,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.

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

@@ -34,7 +34,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.

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

@@ -37,7 +37,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, and the context limit.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.

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

@@ -62,7 +62,7 @@ Record the selected framework, project-defined provider and model, the credentia
 variable names the repository proves or the developer named, these URLs, and the adapter.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/custom-ag-ui.md

@@ -37,6 +37,9 @@ Register the agent in the `agents` map of the Copilot Runtime from
   instance of the project's own class.
 - Connect an agent that runs as its own service with `HttpAgent` from `@ag-ui/client`. Its
   `url` is the service's own AG-UI endpoint, not the runtime's `/api/copilotkit` path.
+  That service reads its own environment, not the app's env file. When the credential
+  step settles the model key, pass `--copy-to <service directory>/.env`, so the key goes
+  into the env file that the service loads.
 
 Do not use `selfManagedAgents` or `agents__unsafe_dev_only`. Those provider options send
 requests past the runtime, so the Intelligence features that this run adds never reach
@@ -92,7 +95,7 @@ credential variable names that the agent already uses, the `clone()` finding, an
 URLs.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.

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

@@ -33,7 +33,7 @@ Record the selected framework, language, vendor, model, required credential vari
 names, these URLs, and each documentation gap.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.