Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
fix(skill): verify platform project credentials
Kshitij Jhunjhunwala committed
Aug 7, 2026 at 11:33 UTC
07dfcc76f8cf7c5cd20ff0c7f4ab4ba095dcfdf1
1 file changed
+22
-1
skills/composio/references/platform.md
+22
-1
@@ -18,7 +18,8 @@ Extend the existing architecture. Do not create a separate demo agent when the r
18
19
## 2. Authenticate the project
20
21
-Run from the project directory:
21
+Run from the project directory. Install the CLI when it is missing; upgrade it
22
+first when an installed CLI reports that a newer version is available:
23
24
```bash
25
curl -fsSL https://composio.dev/install | bash
@@ -27,8 +28,28 @@ composio dev init
28
29
`composio dev init` logs in when needed, binds the directory to the selected Composio project, and provisions `COMPOSIO_API_KEY` in `.env.local`. If developer mode is off, run `composio dev --mode on` first. When the agent cannot open a browser, use `composio dev init --no-browser` and give the returned URL to the user.
30
31
+Before opening the initializer, run `composio dev projects list` and confirm the
32
+exact project is visible. Do this only when initialization is still required; do
33
+not repeat the online project-list check after a local binding already exists. If
34
+the project is missing, stop and ask the developer to sign in to the account or
35
+organization that owns it. Do not accept the selector's default project.
36
+`--no-browser` changes the login step; project selection is still interactive.
37
+
38
Select the exact project the user named. Do not use `-y` when multiple projects exist unless the current CLI project context already matches it. There is no bare `composio init` command.
39
40
+After initialization, verify both checkpoints without printing the credential:
41
+
42
+- `.composio/project.json` names the exact selected project.
43
+- `.env.local` contains a plausible `COMPOSIO_API_KEY` (`ak_...`, at least 10
44
+ characters).
45
+
46
+Treat an HTTP error, a missing key, a shorter placeholder key, or an SDK 401 as
47
+incomplete setup. Perform these local checks before any SDK or network call. If
48
+either local checkpoint fails, stop: do not install dependencies, call the CLI or
49
+backend again, change application code, or claim success. Use the dashboard
50
+fallback to create or copy a project key, store it in `.env.local`, then retry
51
+the SDK call.
52
+
53
If the developer already has a key, store it as `COMPOSIO_API_KEY`. Never print it back, place it in a URL, or commit it.
54
55
Dashboard fallback: Platform → project → API Keys.