copilotkit 4.8.4 → 4.9.1

package/README.md

@@ -44,6 +44,7 @@ answer up front and run anywhere:
 
 ```bash
 copilotkit project list --json                     # see the choices
+copilotkit project list --search support --json    # search name, slug, or id
 copilotkit project select --project <slug-or-id>   # pick an existing one
 copilotkit project select --create "My App" --json # create one and select it
 ```
@@ -57,12 +58,19 @@ slugs instead of recording a selection that points at nothing.
 ```json
 {
   "type": "completed",
+  "selected_project_slug": "my-app",
   "project": { "id": "220", "slug": "my-app", "organizationId": "org_123" },
   "config_path": "/work/my-repo/.copilotkit/project.json",
-  "api_key_provisioned": true
+  "project_file_written": true,
+  "api_key_provisioned": true,
+  "environment_file_written": true
 }
 ```
 
+The four top-level summary fields let a coding agent read the result without
+searching the nested object or reading either file. The payload never contains
+the API key.
+
 `config_path` is absolute, and it is not always under the directory you ran in.
 The project record is repository-scoped: it goes into an existing `.copilotkit/`
 at or above the current directory when there is one, and otherwise into the
@@ -75,11 +83,12 @@ directory you ran in, because that is the file the app process loads — so in a
 repository with a `web/` and an `agent/` half, run `project select` in the half
 that needs the key.
 
-**Check `api_key_provisioned`, not just the exit code.** Key provisioning is
+**Check all four summary fields, not just the exit code.** Key provisioning is
 deliberately non-fatal: if it fails, the selection is still persisted, a warning
 goes to stderr, and the command still exits 0 — leaving a scaffold with no
 `INTELLIGENCE_API_KEY`, whose first run fails with an opaque "Failed to
-initialize thread". That field is the only machine-readable signal of it.
+initialize thread". `api_key_provisioned` and `environment_file_written` are
+false in this state.
 Re-running `project select` is a valid recovery.
 
 Failures use the `login --json` shape, `{"error": "...", "type": "failed"}`, and
@@ -152,6 +161,30 @@ written in, and which init flags that framework supports — `-i`, `--mock`, and
 `--channel` are each accepted only for some. It answers from a catalog compiled into the
 binary, so it needs no API call, no authentication, and no TTY.
 
+### Scaffolding without a terminal
+
+`init` prompts for anything you do not name, and a prompt is a keypress handler,
+so a shell with no terminal has nobody to answer it. Name the answers up front
+and the run needs no terminal at all:
+
+```bash
+copilotkit login                                   # once, at a terminal
+copilotkit init -n my-agent -f langgraph-py \
+  --project <slug-or-id> --yes
+```
+
+- `--project <slug-or-id>` selects an existing hosted Intelligence project, and
+  `--create <name>` makes one. They are mutually exclusive, and they resolve the
+  same way `copilotkit project select` does: a typo fails with the available
+  slugs instead of creating something you did not ask for.
+- `-y`/`--yes` installs dependencies without asking; `--no-install` answers the
+  same question without installing. `--install` is a longhand for `--yes`.
+
+A run with no terminal is refused only for what it has not answered, and every
+missing flag is named at once. Sign-in is the one answer no flag supplies:
+signing in opens a browser and finishes back at the terminal, so run
+`copilotkit login` first rather than letting a scripted run reach it.
+
 `init` and `create` collect your starter choices, then connect project creation
 to your CopilotKit workspace through Ops/Clerk before scaffolding. If you
 already have a valid CLI session, the CLI reuses that workspace connection;
@@ -454,6 +487,7 @@ copilotkit verify
 copilotkit verify --json                                    # machine-readable output
 copilotkit verify --runtime-url http://localhost:8080/copilotkit
 copilotkit verify --round-trip                              # also run the agent
+copilotkit verify --expect-runtime oss --round-trip --agent incident_triage
 ```
 
 It checks that a hosted project is selected, that a project API key is present
@@ -485,6 +519,12 @@ a caller can branch on the command instead of parsing it. With `--json` the
 payload is the only thing on stdout and every diagnostic goes to stderr, so
 piping is safe.
 
+Use `--expect-runtime oss` to prove an open-source runtime instead. In this
+mode, hosted project, key, and thread-route checks do not apply. The command
+exits zero only when `/info` is valid, declares the agent named by `--agent`,
+omits `licenseStatus`, and `--round-trip` passes. Both `--round-trip` and
+`--agent` are required for an OSS pass.
+
 The runtime URL defaults to `http://localhost:3000/api/copilotkit` and the
 report always states which URL it probed, because a wrong default is the most
 likely reason for a runtime failure. Pass `--runtime-url` when the frontend
@@ -634,8 +674,9 @@ report `<version>-pre.<shortsha>` from `copilotkit --version`, so a tester's
 build is always identifiable. `copilotkit version` also reports the canonical
 Intelligence and first-party CopilotKit commits embedded in the artifact.
 
-Pushes and PRs continue to publish `CLI_ENV=local` builds automatically, as
-before.
+Pushes publish `CLI_ENV=local` builds automatically. Pull requests publish
+`CLI_ENV=production` builds under the separate `copilotkit-pr` package name so
+testers can use hosted login without confusing the artifact with a release.
 
 Note: `workflow_dispatch` only works against refs that contain the dispatch
 trigger — branches cut before this workflow landed need a merge from `main`

package/cli-build-info.json

@@ -2,20 +2,20 @@
   "schemaVersion": 1,
   "package": {
     "name": "copilotkit",
-    "version": "4.8.4"
+    "version": "4.9.1"
   },
   "intelligence": {
-    "commit": "6483664ecea767ad39fe52106d85b94731740150"
+    "commit": "0528d9de0d7915386d789deb676d44c4668842b1"
   },
   "copilotKit": {
-    "submittedInput": "47c5510b4909f6728288ecf28d7b14cd14922d33",
-    "commit": "47c5510b4909f6728288ecf28d7b14cd14922d33"
+    "submittedInput": "2ad03320fe1f0834b138113fffe791781e5b226e",
+    "commit": "2ad03320fe1f0834b138113fffe791781e5b226e"
   },
   "channel": "production",
   "triggeringActor": "MikeRyanDev",
   "workflow": {
-    "runId": "32806721876",
-    "runUrl": "https://github.com/CopilotKit/Intelligence/actions/runs/32806721876"
+    "runId": "32915219082",
+    "runUrl": "https://github.com/CopilotKit/Intelligence/actions/runs/32915219082"
   },
   "validationResult": "passed",
   "ag2": {
@@ -24,5 +24,5 @@
     "revision": "main",
     "pinned": false
   },
-  "builtAt": "2026-08-25T03:52:56Z"
+  "builtAt": "2026-08-26T00:29:57Z"
 }