copilotkit 4.16.0 → 4.17.0

package/README.md

@@ -280,8 +280,14 @@ and gives up after 10 minutes.
 
 Under `--json`, the first `authentication_url` record is the URL with the code
 in it, and it also carries `user_code` and `expires_at`. A sign-in that ends without a session writes a `failed`
-record with `reason: expired` or `reason: access_denied`. If the Ops service
-has no device routes, `login --json` falls back to the loopback flow.
+record with `reason: expired` or `reason: access_denied`, and with
+`retry: ask_developer`: a person must act before a new code can work. After 2
+codes in a row expire with nobody approving them, `login --json` refuses to
+request another. It writes a `failed` record with `reason: repeated_expiry` and
+exits non-zero. Run `copilotkit login --json --force` when someone is ready to
+approve. Any sign-in that succeeds resets the count, and the count lapses after
+a day. If the Ops service has no device routes, `login --json` falls back to the
+loopback flow.
 
 Approve a code only if your own terminal or coding agent showed it to you. If
 someone sent you a code, deny the request: approving it signs their CLI in as
@@ -334,7 +340,10 @@ 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
 frontend.
 Its first prompt records the coding agent with `onboard identify`, including when
-the entry command omitted `--coding-agent`. Channel setup stage events include
+the entry command omitted `--coding-agent`. The agent also passes `--model` with
+the exact model id its instructions name, and leaves it out when they name none.
+The event records a missing id as `unknown`, and the coding agent the environment
+shows as `detected_coding_agent`. Channel setup stage events include
 the existing `onboarding_run_id` when the command runs inside an onboarding run;
 standalone commands omit it. These events use the CLI's existing telemetry consent gate.
 
@@ -486,7 +495,16 @@ are supported. Configure source identity and access with the
 [`MASTRA_IMPORT_*` variables](../../libs/import-mastra/README.md); destination
 Intelligence credentials use the usual import options.
 
-Local access requires Node 22.13+. Use the same source namespace when switching
+Local access requires Node 22.13+ and npm. The CLI does not ship the LibSQL
+driver, so the first local import installs `@mastra/libsql@1.14.3` and
+`@mastra/core@1.48.0` into `~/.copilotkit/cache/mastra-driver/`
+(`$XDG_CACHE_HOME/copilotkit/mastra-driver/` when that variable is an absolute
+path) and reuses them after that. The install overrides the npm settings
+`legacy-peer-deps` and `omit=optional`, which would otherwise leave out a
+required peer or the native binary. If that install fails, the error prints the
+`npm install` command to run by hand. Server mode installs nothing.
+
+Use the same source namespace when switching
 between local and remote access so repeat imports deduplicate. Import while the
 source is idle. This reads existing history and pending data; it does not execute
 models, tools or native resume operations.
@@ -1016,6 +1034,24 @@ exits zero only when `/info` is valid, declares the agent named by `--agent`,
 reports no Intelligence entitlement, and `--round-trip` passes. Both `--round-trip` and
 `--agent` are required for an OSS pass.
 
+Without `--expect-runtime`, `verify` checks an app as open source on its own
+when nothing points at a hosted setup: no `.copilotkit/project.json`, no
+Intelligence key, and a runtime that answers `/info` without an Intelligence
+client. The report says so at the top, names the runtime URL it checked, and
+says when that URL was only assumed. `--json` reports
+`"expectRuntime": "oss"` with `"expectRuntimeSource": "detected"` (otherwise
+`"flag"` or `"default"`). The round trip still has to pass. It runs against the
+agent `--agent` names, with or without `--round-trip`. Without `--agent`, when
+the runtime declares exactly one agent, `verify` runs it and names it. With no
+agent or several, the run fails and names `--round-trip --agent <id>`. A runtime
+mounted `mode: "single-route"` cannot pass this way without a key, because
+`verify` reads a single-route answer from the Intelligence platform and an
+open-source runtime records nothing there. Mount it multi-route (the default)
+and point `--runtime-url` at that endpoint.
+Pass `--expect-runtime intelligence` to check the hosted setup instead. A
+recorded project, a key, or a runtime that does not answer keeps the hosted
+checks.
+
 ### Which runtime URL gets probed
 
 `verify` works the port out from the project rather than assuming one. In order:
@@ -1199,6 +1235,35 @@ started, and a starter that serves both halves from one script loses both when
 either one goes down. Restart what you started, with the command you started it
 with, and leave the rest running.
 
+### A model key has no credits or is rejected
+
+A key with no credits passes every static check. The first model call then
+fails inside the agent, and the round-trip proof reports only a timeout.
+
+Ask the vendor about one key before the build:
+
+```bash
+copilotkit onboard model-key --key OPENAI_API_KEY
+copilotkit onboard model-key --key ANTHROPIC_API_KEY --env-file agent/.env --json
+```
+
+The command reads the key from the env file (`.env` by default) and sends one
+request with a one-token answer to that vendor. The call costs a fraction of a
+cent. It knows `OPENAI_API_KEY`, `ANTHROPIC_API_KEY`, and `GOOGLE_API_KEY`.
+
+- `pass`: the vendor served a model call with the key.
+- `fail`: the vendor refused the key. The cause is `model_quota` (no credits) or
+  `model_auth` (a rejected key).
+- `missing`: the env file or the key is absent, or the value is a placeholder.
+- `unsupported` or `undetermined`: the check did not settle it. A rate limit, a
+  vendor outage, or a probe model the key may not use proves nothing about the
+  key, so none of them is a `fail`.
+
+It does not send the key when a base URL such as `OPENAI_BASE_URL` points the
+SDK at another endpoint, or when the shell exports a different value for the
+key. It never prints the key, and it never prints the vendor's error message,
+because a vendor can echo part of the key in it.
+
 ### A command, subcommand, or flag that should exist is rejected
 
 `npx` keys its cache on the spec string, so `copilotkit@latest` can keep serving

package/cli-build-info.json

@@ -2,20 +2,20 @@
   "schemaVersion": 1,
   "package": {
     "name": "copilotkit",
-    "version": "4.16.0"
+    "version": "4.17.0"
   },
   "intelligence": {
-    "commit": "9b0c17ef9b25db5614653a69190290fadaf9fe59"
+    "commit": "f6f91f8357a9058dcda3f2ef07a3283e23ddb9e8"
   },
   "copilotKit": {
-    "submittedInput": "a933af0b132e",
-    "commit": "a933af0b132e61d2d04be7ce0a8f55743af21ccc"
+    "submittedInput": "0c8647a7f4ec",
+    "commit": "0c8647a7f4ecf565e58405642539c9d9744f62c5"
   },
   "channel": "production",
   "triggeringActor": "BenTaylorDev",
   "workflow": {
-    "runId": "36051066331",
-    "runUrl": "https://github.com/CopilotKit/Intelligence/actions/runs/36051066331"
+    "runId": "36178536102",
+    "runUrl": "https://github.com/CopilotKit/Intelligence/actions/runs/36178536102"
   },
   "validationResult": "passed",
   "ag2": {
@@ -24,5 +24,5 @@
     "revision": "main",
     "pinned": false
   },
-  "builtAt": "2026-09-24T19:54:09Z"
+  "builtAt": "2026-09-25T19:17:42Z"
 }