copilotkit 4.5.0 → 4.6.0

package/README.md

@@ -85,6 +85,87 @@ already have a valid CLI session, the CLI reuses that workspace connection;
 otherwise it opens browser sign-in. This workspace connection is required for
 project creation and is separate from license issuance.
 
+## Managed Channels
+
+`copilotkit channels` connects a hosted Intelligence project to Slack or
+Microsoft Teams. The supported path today is a project scaffolded by
+`copilotkit init`, which offers a Channel during setup and writes the hosted
+`INTELLIGENCE_*` values the runtime needs.
+
+The commands also run in a project that already exists, but that path is not
+hardened yet: `copilotkit project select` provisions the project API key without
+the hosted URLs, so a Channel can attach and still be unable to connect. See
+OSS-714.
+
+```bash
+copilotkit channels add support
+copilotkit channels add support --adapter teams
+copilotkit channels status
+copilotkit channels list
+copilotkit channels rotate support --adapter slack
+copilotkit channels setup
+```
+
+This configures **managed Intelligence Channels**. It does not configure the
+open-source `@copilotkit/channels` adapter packages, which are a separate product
+that shares the words "channels" and "Slack".
+
+`channels add` does the next undone step and is safe to re-run: it declares the
+Channel in `.copilotkit/channels.json`, creates it on the server, writes the
+provider app manifest, and attaches the adapter once your credentials are
+available. Where the flow needs you to do something in a provider console it
+stops and tells you what, why, which variables to set, and the exact command to
+resume with. A stop is a normal outcome and exits 0.
+
+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.
+
+### Agent-assisted setup
+
+Most of Slack setup is browser work — creating the app, collecting its tokens,
+installing it into a workspace. `channels setup` hands that to your coding
+agent instead of walking it yourself:
+
+```bash
+copilotkit channels setup
+copilotkit channels setup --no-clipboard
+```
+
+It prints a setup prompt and copies it to your clipboard; paste it into Claude
+(or your coding agent) to start. The prompt is always printed, so you can read
+it before handing it over. Pass `--no-clipboard` in a headless or remote shell.
+
+The prompt points at the `setup-slack-channel` skill, so install the skills
+first:
+
+```bash
+npx copilotkit@latest skills install --skill setup-slack-channel
+```
+
+`channels setup` does not install or check for the skill, so the prompt itself
+tells the agent to stop and ask for that command if the skill is missing —
+rather than fall back to setting Slack up from memory against a live workspace.
+
+`copilotkit skills onboard --channels` does both in one pass — installs the
+skills, signs you in, and hands over the same prompt.
+
+`channels setup` reaches no server and provisions nothing. It needs no hosted
+project and no sign-in, so it works from any directory.
+
+`channels status` compares three things that all have to agree — your declared
+configuration, your project's source, and the server — and names whichever one is
+missing. That includes the failure worth knowing about: some runtime mounts defer
+opening the gateway connection until an awaited `channels.ready()` call, so on
+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.
+
+`--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
+declared-Channels file, the envelope shape, and the credential resolution order.
+
 ## Skills And Agent-Assisted Onboarding
 
 Use `copilotkit create` to start a **new** project. Use `copilotkit skills onboard`
@@ -97,8 +178,14 @@ copilotkit skills install --skill react-core,runtime --agent claude-code
 copilotkit skills install --list
 copilotkit skills onboard
 copilotkit skills onboard --no-clipboard
+copilotkit skills onboard --channels
 ```
 
+`--channels` hands over the Slack Channel setup prompt instead of the generic
+add-CopilotKit-to-my-app prompt. It is the same prompt
+`copilotkit channels setup` prints; only the prompt differs, and the install
+and sign-in are unchanged.
+
 `copilotkit skills install` installs CopilotKit agent skills for your coding
 agent (Claude Code, Codex, Cursor, Gemini, and others) by running the standalone
 `skills` installer under the hood.

package/cli-build-info.json

@@ -2,20 +2,20 @@
   "schemaVersion": 1,
   "package": {
     "name": "copilotkit",
-    "version": "4.5.0"
+    "version": "4.6.0"
   },
   "intelligence": {
-    "commit": "cdb1dbd45dd27adbaa8be1fcfd6843c2927f5943"
+    "commit": "bbe66a43632d05b5206cebdf49518d7335cc0f78"
   },
   "copilotKit": {
-    "submittedInput": "a1c9b3147829ac358bae82df651f45a1aea2a437",
-    "commit": "a1c9b3147829ac358bae82df651f45a1aea2a437"
+    "submittedInput": "bc80efb17f5b729cc96a50cbbefca163079dc781",
+    "commit": "bc80efb17f5b729cc96a50cbbefca163079dc781"
   },
   "channel": "production",
   "triggeringActor": "MikeRyanDev",
   "workflow": {
-    "runId": "30390320157",
-    "runUrl": "https://github.com/CopilotKit/Intelligence/actions/runs/30390320157"
+    "runId": "30914059582",
+    "runUrl": "https://github.com/CopilotKit/Intelligence/actions/runs/30914059582"
   },
   "validationResult": "passed",
   "ag2": {
@@ -24,5 +24,5 @@
     "revision": "main",
     "pinned": false
   },
-  "builtAt": "2026-07-28T19:06:01Z"
+  "builtAt": "2026-08-04T13:31:09Z"
 }