copilotkit 4.5.1 → 4.7.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +101 -0
- package/cli-build-info.json +8 -8
- package/index.js +12450 -7036
- package/package.json +1 -1
- package/release/release-tool.js +1 -1
package/README.md
CHANGED
|
@@ -85,6 +85,101 @@ already have a valid CLI session, the CLI reuses that workspace connection;
|
|
|
85
85
|
otherwise it opens browser sign-in. This workspace connection is required for
|
|
86
86
|
project creation and is separate from license issuance.
|
|
87
87
|
|
|
88
|
+
## Managed Channels
|
|
89
|
+
|
|
90
|
+
`copilotkit channels` connects a hosted Intelligence project to Slack or
|
|
91
|
+
Microsoft Teams. The supported path today is a project scaffolded by
|
|
92
|
+
`copilotkit init`, which offers a Channel during setup and writes the hosted
|
|
93
|
+
`INTELLIGENCE_*` values the runtime needs.
|
|
94
|
+
|
|
95
|
+
The commands also run in a project that already exists, but that path is not
|
|
96
|
+
hardened yet: `copilotkit project select` provisions the project API key without
|
|
97
|
+
the hosted URLs, so a Channel can attach and still be unable to connect. See
|
|
98
|
+
OSS-714.
|
|
99
|
+
|
|
100
|
+
```bash
|
|
101
|
+
copilotkit channels add support
|
|
102
|
+
copilotkit channels add support --adapter teams
|
|
103
|
+
copilotkit channels status
|
|
104
|
+
copilotkit channels list
|
|
105
|
+
copilotkit channels rotate support --adapter slack
|
|
106
|
+
copilotkit channels setup
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
This configures **managed Intelligence Channels**. It does not configure the
|
|
110
|
+
open-source `@copilotkit/channels` adapter packages, which are a separate product
|
|
111
|
+
that shares the words "channels" and "Slack".
|
|
112
|
+
|
|
113
|
+
`channels add` does the next undone step and is safe to re-run: it declares the
|
|
114
|
+
Channel in `.copilotkit/channels.json`, creates it on the server, writes the
|
|
115
|
+
provider app manifest, and attaches the adapter once your credentials are
|
|
116
|
+
available. Where the flow needs you to do something in a provider console it
|
|
117
|
+
stops and tells you what, why, which variables to set, and the exact command to
|
|
118
|
+
resume with. A stop is a normal outcome and exits 0.
|
|
119
|
+
|
|
120
|
+
No flag accepts a credential value. Credentials are read from your project's
|
|
121
|
+
`.env`, from a named environment variable, or from a JSON document on stdin; at a
|
|
122
|
+
terminal the CLI offers a masked prompt instead.
|
|
123
|
+
|
|
124
|
+
### Agent-assisted setup
|
|
125
|
+
|
|
126
|
+
Much of Slack and Teams setup happens in a provider website — creating the app,
|
|
127
|
+
collecting its tokens, installing it into a workspace. `channels setup` hands
|
|
128
|
+
that work to your coding agent instead of you walking it yourself:
|
|
129
|
+
|
|
130
|
+
```bash
|
|
131
|
+
copilotkit channels setup
|
|
132
|
+
copilotkit channels setup --no-clipboard
|
|
133
|
+
```
|
|
134
|
+
|
|
135
|
+
It installs the `channels-setup` skill, then prints a one-line prompt to paste
|
|
136
|
+
into your coding agent and copies it to your clipboard. The prompt is always
|
|
137
|
+
printed, so you can read it before handing it over. Pass `--no-clipboard` in a
|
|
138
|
+
headless or remote shell.
|
|
139
|
+
|
|
140
|
+
Everything the run needs is in the skill, so the prompt only names the skill and
|
|
141
|
+
the goal. It does not name a provider: Slack or Microsoft Teams is the skill's
|
|
142
|
+
own first question.
|
|
143
|
+
|
|
144
|
+
Only the prompt goes to stdout. The line introducing it and the clipboard result
|
|
145
|
+
go to stderr, so `copilotkit channels setup > prompt.txt` gives you the payload
|
|
146
|
+
and nothing else.
|
|
147
|
+
|
|
148
|
+
The install runs first, and the command stops if it fails. A prompt that points
|
|
149
|
+
at a skill which is not there would send the agent to set the provider up from
|
|
150
|
+
memory against a live workspace, which is the outcome the prompt exists to
|
|
151
|
+
prevent.
|
|
152
|
+
|
|
153
|
+
The install asks you nothing. It pins the skill and every detected coding agent,
|
|
154
|
+
so it runs to completion in a script or a non-TTY shell rather than stopping on a
|
|
155
|
+
picker.
|
|
156
|
+
|
|
157
|
+
Only `channels-setup` is installed, not every CopilotKit skill. To add the rest:
|
|
158
|
+
|
|
159
|
+
```bash
|
|
160
|
+
npx copilotkit@latest skills install
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
`copilotkit skills onboard --channels` installs the skills, signs you in, and
|
|
164
|
+
hands over the same prompt.
|
|
165
|
+
|
|
166
|
+
`channels setup` selects no hosted project and provisions nothing, so it needs no
|
|
167
|
+
sign-in and works from any directory. Installing the skill is the only thing it
|
|
168
|
+
reaches out for.
|
|
169
|
+
|
|
170
|
+
`channels status` compares three things that all have to agree — your declared
|
|
171
|
+
configuration, your project's source, and the server — and names whichever one is
|
|
172
|
+
missing. That includes the failure worth knowing about: some runtime mounts defer
|
|
173
|
+
opening the gateway connection until an awaited `channels.ready()` call, so on
|
|
174
|
+
those a project that never makes the call serves HTTP normally, reports no error,
|
|
175
|
+
and answers nothing. Mounts that own their process lifetime start on their own,
|
|
176
|
+
and `status` distinguishes the two rather than warning about both.
|
|
177
|
+
|
|
178
|
+
`--json` emits a versioned envelope on stdout for agents and scripts, never
|
|
179
|
+
prompts, and never opens a browser. See
|
|
180
|
+
[Managed Channel CLI contracts](../../docs/channels-cli-contracts.md) for the
|
|
181
|
+
declared-Channels file, the envelope shape, and the credential resolution order.
|
|
182
|
+
|
|
88
183
|
## Skills And Agent-Assisted Onboarding
|
|
89
184
|
|
|
90
185
|
Use `copilotkit create` to start a **new** project. Use `copilotkit skills onboard`
|
|
@@ -97,8 +192,14 @@ copilotkit skills install --skill react-core,runtime --agent claude-code
|
|
|
97
192
|
copilotkit skills install --list
|
|
98
193
|
copilotkit skills onboard
|
|
99
194
|
copilotkit skills onboard --no-clipboard
|
|
195
|
+
copilotkit skills onboard --channels
|
|
100
196
|
```
|
|
101
197
|
|
|
198
|
+
`--channels` hands over the Slack Channel setup prompt instead of the generic
|
|
199
|
+
add-CopilotKit-to-my-app prompt. It is the same prompt
|
|
200
|
+
`copilotkit channels setup` prints; only the prompt differs, and the install
|
|
201
|
+
and sign-in are unchanged.
|
|
202
|
+
|
|
102
203
|
`copilotkit skills install` installs CopilotKit agent skills for your coding
|
|
103
204
|
agent (Claude Code, Codex, Cursor, Gemini, and others) by running the standalone
|
|
104
205
|
`skills` installer under the hood.
|
package/cli-build-info.json
CHANGED
|
@@ -2,20 +2,20 @@
|
|
|
2
2
|
"schemaVersion": 1,
|
|
3
3
|
"package": {
|
|
4
4
|
"name": "copilotkit",
|
|
5
|
-
"version": "4.
|
|
5
|
+
"version": "4.7.0"
|
|
6
6
|
},
|
|
7
7
|
"intelligence": {
|
|
8
|
-
"commit": "
|
|
8
|
+
"commit": "932bad4f3c97b61dd0ee5c20b99362e302e5e48a"
|
|
9
9
|
},
|
|
10
10
|
"copilotKit": {
|
|
11
|
-
"submittedInput": "
|
|
12
|
-
"commit": "
|
|
11
|
+
"submittedInput": "8e59bfd16b415b9f776a4742aa43942a8d02c2ef",
|
|
12
|
+
"commit": "8e59bfd16b415b9f776a4742aa43942a8d02c2ef"
|
|
13
13
|
},
|
|
14
14
|
"channel": "production",
|
|
15
|
-
"triggeringActor": "
|
|
15
|
+
"triggeringActor": "BenTaylorDev",
|
|
16
16
|
"workflow": {
|
|
17
|
-
"runId": "
|
|
18
|
-
"runUrl": "https://github.com/CopilotKit/Intelligence/actions/runs/
|
|
17
|
+
"runId": "30933084879",
|
|
18
|
+
"runUrl": "https://github.com/CopilotKit/Intelligence/actions/runs/30933084879"
|
|
19
19
|
},
|
|
20
20
|
"validationResult": "passed",
|
|
21
21
|
"ag2": {
|
|
@@ -24,5 +24,5 @@
|
|
|
24
24
|
"revision": "main",
|
|
25
25
|
"pinned": false
|
|
26
26
|
},
|
|
27
|
-
"builtAt": "2026-
|
|
27
|
+
"builtAt": "2026-08-04T17:17:46Z"
|
|
28
28
|
}
|