copilotkit 4.14.0 → 4.15.0

package/README.md

@@ -327,8 +327,8 @@ npx --yes copilotkit@latest onboard start \
 | `add-voice`              | Add documented voice transcription to the existing composer |
 | `add-realtime-sync`      | Prove managed thread changes sync between active clients    |
 
-Run `copilotkit channels setup` to copy the same small `onboard start --run <id>`
-prompt as the website CTA. There is no `--intent add-channels`. The copied
+Run `copilotkit channels setup` to continue an unfinished Channels onboarding
+run, or copy the same onboarding URL prompt as the website CTA for a new run. There is no `--intent add-channels`. The copied
 prompt has no Channel sentence. When the project has no frontend, the root graph
 asks which frontend they want and offers Slack and Microsoft Teams there. If the
 copied prompt came from a Slack or Teams docs page, that page is the named
@@ -361,11 +361,13 @@ The developer can widen the scope the graph will not. The agent names one fix an
 asks. When the developer approves it, the agent makes that one fix and runs:
 
 ```bash
-npx --yes copilotkit@latest onboard resume
+npx --yes copilotkit@latest onboard resume --message "<the approved fix>"
 ```
 
-The approval goes to standard input, in one or two sentences and at most 500
-characters. The command puts the run back on the step that failed, keeps the same
+The approval goes in `--message`, in one or two sentences and at most 500
+characters. The command also reads the approval from standard input when
+`--message` is absent. A piped approval puts its text in the command that a Codex
+approval covers, so the next call needs a new approval. The command puts the run back on the step that failed, keeps the same
 run id, and records both the approval and the step it re-entered. So the repair
 and the second proof attempt belong to the run that stopped, rather than to
 nothing at all. The approval is guarded and sent under the same telemetry setting
@@ -508,6 +510,10 @@ Teams credentials in `.env` or the process environment keep the by-hand attach
 path. Pass `--no-provision` to choose that path yourself. Non-interactive runs
 stay on the by-hand path unless they pass `--provision`.
 
+If Microsoft sign-in fails, check the browser page for an `AADSTS` error code.
+The CLI shows a known code or `invalid_request` when Microsoft returns one in
+the terminal. It does not print the full Microsoft response.
+
 No flag accepts a credential value. Credentials are read from your project's
 `.env`, from a named environment variable, or from a JSON document on stdin; at a
 terminal the CLI offers a masked prompt instead.
@@ -523,7 +529,22 @@ copilotkit channels setup
 copilotkit channels setup --no-clipboard
 ```
 
-The command copies the small `onboard start --run <id>` prompt.
+If this project already has an unfinished Channels run, the command prints its
+existing ID and instructions to continue its route. It installs nothing, generates
+no ID, and leaves the clipboard unchanged. This includes paused runs and older
+bindings without timestamps; runs do not expire while waiting for you.
+
+Use `--run <id>` to name this project's unfinished run explicitly. Unknown,
+completed, or mismatched IDs are refused. Use `--new-run` instead to deliberately
+start another journey. The flags cannot be combined. A completed run or a run
+for another feature does not block a fresh Channels setup automatically.
+`copilotkit skills onboard --channels` honors the same run choices.
+If completion state cannot be saved, onboarding still completes and prints a
+warning. The next setup may require `--new-run` to start a fresh run.
+
+For a new run, the command copies an onboarding URL containing a fresh run ID.
+Before installing, it names the `channels-setup` skill, its
+`CopilotKit/CopilotKit/skills` source, and its project scope for all supported agents.
 It installs the `channels-setup` skill, then prints that prompt to paste
 into your coding agent and copies it to your clipboard. The prompt is always
 printed, so you can read it before handing it over. Pass `--no-clipboard` in a
@@ -565,6 +586,16 @@ those a project that never makes the call serves HTTP normally, reports no error
 and answers nothing. Mounts that own their process lifetime start on their own,
 and `status` distinguishes the two rather than warning about both.
 
+Managed API and realtime URLs have defaults; preflight needs the project API key,
+not an explicit WebSocket URL override. Runtime diagnostics refer to
+`CopilotRuntime`. Dynamic options and unresolved `channels` shorthand remain
+undetermined, while awaited optional chaining is recognized.
+
+If an onboarding run is already in progress, use `copilotkit onboard route` and
+`copilotkit onboard read <step>` to continue its current served step. Runtime
+wiring is covered by `feature/channels/implement`; paused runs must follow their
+stop instructions first. Outside a run, begin with `copilotkit channels setup`.
+
 `--json` emits a versioned envelope on stdout for agents and scripts, never
 prompts, and never opens a browser. See
 [Managed Channel CLI contracts](../../docs/channels-cli-contracts.md) for the
@@ -1244,6 +1275,7 @@ join one Container permanently. Already-bound threads are ineligible.
 
 ```bash
 copilotkit learning threads list support --binding all --json
+copilotkit learning threads list support --source slack --json
 copilotkit learning threads preview support --all --agent support-agent --from 2026-09-01 --to 2026-10-01 --json
 copilotkit learning threads commit support <operation-id> --yes --json
 copilotkit learning threads status support <operation-id> --json
@@ -1254,6 +1286,9 @@ repeated `--thread <id>` flags instead of `--all` to select specific threads.
 Filters apply to thread creation time. `--from` is inclusive and `--to` is
 exclusive; date-only values use UTC. `list` accepts `--cursor` for the next page.
 The binding filter accepts `all`, `unbound`, `this_container`, or `other_container`.
+The source filter accepts `all`, `app`, `slack`, or `teams`, where `app` means the
+thread arrived straight from the Runtime and the provider values select threads a
+Channel created.
 
 Read the preview before commit. `--yes` approves permanent assignment of that
 saved selection. Each operation accepts at most 10,000 threads. New matching

package/cli-build-info.json

@@ -2,20 +2,20 @@
   "schemaVersion": 1,
   "package": {
     "name": "copilotkit",
-    "version": "4.14.0"
+    "version": "4.15.0"
   },
   "intelligence": {
-    "commit": "0c02887906a99364b17fdbbca23ec4430741efcc"
+    "commit": "f6de0940e2aac5d2e323767f3d6431354715d2e6"
   },
   "copilotKit": {
-    "submittedInput": "2c42a41a7e",
-    "commit": "2c42a41a7e749c4473705769d1ae985d89718465"
+    "submittedInput": "33db9a81ccfd",
+    "commit": "33db9a81ccfd2d6e820defe3c1616594909439af"
   },
   "channel": "production",
-  "triggeringActor": "BenTaylorDev",
+  "triggeringActor": "AlemTuzlak",
   "workflow": {
-    "runId": "35927663284",
-    "runUrl": "https://github.com/CopilotKit/Intelligence/actions/runs/35927663284"
+    "runId": "36016174452",
+    "runUrl": "https://github.com/CopilotKit/Intelligence/actions/runs/36016174452"
   },
   "validationResult": "passed",
   "ag2": {
@@ -24,5 +24,5 @@
     "revision": "main",
     "pinned": false
   },
-  "builtAt": "2026-09-23T22:21:17Z"
+  "builtAt": "2026-09-24T14:55:57Z"
 }