davidmckayv · Nov 5, 2026 · Nov 5, 2026
@@ -15,6 +15,10 @@ Newest first. `Unreleased` is what is on `main` and not yet tagged.
   Bot picker. An installation an earlier app connected to a hosted Intelligence starts at the first
   screen and keeps its finished install, its database and its Bots; its conversations stay in that
   hosted Intelligence.
+- OpenBot Desktop's local Intelligence is 0.16.0-rc.5, the same release the Helm chart installs.
+  The app carries an Intelligence CLI built to install exactly that release
+  (`copilotkit` 4.33.1-pre.256cc68), where the stable CLI would install the newest stable
+  Intelligence, 0.15.1.
 - OpenBot Desktop runs every new installation as Compose project `openbot-desktop`, never a source
   checkout's. An installation an earlier app made keeps its own project, and with it its database
   and its Bots' computers, even when Stop or Quit took its containers down. If another OpenBot on
@@ -33,7 +37,7 @@ Newest first. `Unreleased` is what is on `main` and not yet tagged.
   candidate's and never an unsigned build, and follow a new release within minutes of it becoming
   Latest. Each release's installers stay under `releases/<tag>/`. See
   [Releasing](docs/releasing.md#downloadscopilotkitai).
-- The Helm chart now installs CopilotKit Intelligence with OpenBot by default, so one `helm install` is the whole product: Intelligence 0.16.0-rc.4 in self-hosted mode on its own bundled PostgreSQL and Redis, with every credential it needs generated and kept across upgrades, OpenBot's project and runtime key created inside it by Intelligence's own bootstrap from a key the chart generates, with nobody signing in, and Automatic Learning and Trajectories on. The licence is given once, as `secrets.licenseToken`, and reaches both; Learning's agent runs on `secrets.modelApiKey`. The server carries the browser's socket to Intelligence's gateway on its own address, so a single `kubectl port-forward` reaches everything. The chart README's vanilla install is the three steps. **Before upgrading:** a release pointed at managed Intelligence, or at one of its own, needs `--set intelligence.enabled=false`; the chart refuses the upgrade until it is set rather than install a second, empty Intelligence.
+- The Helm chart now installs CopilotKit Intelligence with OpenBot by default, so one `helm install` is the whole product: Intelligence 0.16.0-rc.5 in self-hosted mode on its own bundled PostgreSQL and Redis, with every credential it needs generated and kept across upgrades, OpenBot's project and runtime key created inside it by Intelligence's own bootstrap from a key the chart generates, with nobody signing in, and Automatic Learning and Trajectories on. The licence is given once, as `secrets.licenseToken`, and reaches both; Learning's agent runs on `secrets.modelApiKey`. The server carries the browser's socket to Intelligence's gateway on its own address, so a single `kubectl port-forward` reaches everything. The chart README's vanilla install is the three steps. **Before upgrading:** a release pointed at managed Intelligence, or at one of its own, needs `--set intelligence.enabled=false`; the chart refuses the upgrade until it is set rather than install a second, empty Intelligence.
 - Connecting an app through Arcade on a single-user or personal install now brings you back to the OpenBot you started from, wherever it runs. After the consent screen, Arcade sends you to the address its project names as its user verifier, which used to be set by hand in Arcade's dashboard, so any OpenBot at another address (anything but `localhost:3001` on a shared key) landed on a page that does not exist. A single-user install now points that setting at its own `OPENBOT_PUBLIC_URL` (or `BETTER_AUTH_URL`) before each Connect or Authorize and reads it back; several on one key take turns, and the latest Connect decides where people come back. A deployment that signs people in treats its Arcade project as shared and never changes the setting: it checks it before each Connect and, until it names this deployment, refuses before anybody signs in, with the exact address to set in Arcade's dashboard. It also names that address at startup. See [Arcade](docs/plugins/arcade.md#the-verifier-url).
 - A Bot's work in a conversation reads as one line. A subtask is a step in the same line as the
   searches and pages beside it ("Searched the web, read 5 pages and ran 2 subtasks"), and opens to

@@ -4,6 +4,6 @@ dependencies:
   version: 16.7.27
 - name: intelligence
   repository: oci://ghcr.io/copilotkit/charts
-  version: 0.16.0-rc.4
-digest: sha256:0ab0aa52906070274b8a2d4c45646764c817c6e8cfe8a563a9aafbbf8fa276b1
-generated: "2026-11-05T14:00:34.927532-08:00"
+  version: 0.16.0-rc.5
+digest: sha256:b78c69af0d490b3b8a2e59c17dcd153ea24fa8f96a0ff55b3268b15451104345
+generated: "2026-11-05T14:26:25.62136-08:00"
@@ -39,6 +39,6 @@ dependencies:
     # EXACT, NOT A RANGE, for the reason the pin above gives: a new release of this chart carries new
     # images and new required values, and arriving on its own it would be an install nobody tested.
     # Bump it deliberately, with the values under `intelligence` in values.yaml.
-    version: "0.16.0-rc.4"
+    version: "0.16.0-rc.5"
     repository: "oci://ghcr.io/copilotkit/charts"
     condition: intelligence.enabled
@@ -817,7 +817,7 @@ commonAnnotations: {}
 #
 # Everything under this key except `enabled` is the Intelligence chart's own values, passed to it
 # unchanged: its README (`helm show readme oci://ghcr.io/copilotkit/charts/intelligence --version
-# 0.16.0-rc.4`) documents every one, and anything it documents can be set here.
+# 0.16.0-rc.5`) documents every one, and anything it documents can be set here.
 #
 # THE SECRET NAMES BELOW ARE FIXED, NOT DERIVED FROM THE RELEASE, because the Intelligence chart takes
 # them as plain names. This chart creates each one under exactly the name written here, so changing a

@@ -1,5 +1,5 @@
 {
-  "cli": "latest",
+  "cli": "https://pkg.pr.new/CopilotKit/Intelligence/copilotkit@256cc68",
   "node": {
     "version": "26.13.0",
     "sha256": {