Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs: update CLAUDE.md for composio SDK
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Zen Agent committed
May 11, 2026 at 09:53 UTC
f273e95f922baf5a2a15325687179a633d70ec88
2 files changed
+185
-674
CLAUDE.md
+68
-375
@@ -1,404 +1,97 @@
1
# CLAUDE.md
2
3
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
3
+Guidance for Claude Code when working in this repository. For Codex / generic-agent guidance see `AGENTS.md`.
4
5
## Overview
6
7
-This is the Composio SDK v3 repository containing both TypeScript and Python SDKs. The main development focus is on the TypeScript SDK located in `/ts/` directory. The project uses a monorepo structure with multiple packages and examples.
7
+Composio SDK v3 — monorepo containing the **TypeScript SDK** (primary, under `ts/`) and the **Python SDK** (under `python/`). Built with **pnpm workspaces + Turbo** for TS, **uv + nox** for Python. Default branch: `next`.
8
9
-## Memories and Notes
9
+## Repository Layout
10
11
-- For documentation tasks, refer to `docs/CLAUDE.md`
12
-
13
-## Effect.ts Reference Source
14
-
15
-The CLI package (`@composio/cli`) is built on the Effect.ts ecosystem. A local copy of the Effect source code is available as a git submodule:
16
-
17
-- **Location:** `ts/vendor/effect/`
18
-- **Repo:** [Effect-TS/effect](https://github.com/Effect-TS/effect)
19
-- **Branch:** `main`
20
-
21
-When working on CLI code, reference the Effect source for accurate patterns:
22
-- `ts/vendor/effect/packages/effect/src/` — core Effect runtime
23
-- `ts/vendor/effect/packages/cli/src/` — @effect/cli (Command, Options, Args)
24
-- `ts/vendor/effect/packages/platform/src/` — @effect/platform (FileSystem, Terminal)
25
-
26
-**Important:** The submodule is for **read-only reference only**. Do not modify files in `ts/vendor/`. The CLI's actual dependencies come from npm via `pnpm install`.
27
-
28
-## Clack Reference Source
29
-
30
-The CLI uses [`@clack/prompts`](https://github.com/bombshell-dev/clack) for interactive terminal UI. A local copy of the Clack source code is available as a git submodule:
31
-
32
-- **Location:** `ts/vendor/clack/`
33
-- **Repo:** [bombshell-dev/clack](https://github.com/bombshell-dev/clack)
34
-
35
-When working on CLI prompts and terminal UI, reference the Clack source for accurate APIs:
36
-- `ts/vendor/clack/packages/prompts/src/` — `@clack/prompts` (high-level API: text, select, confirm, spinner, etc.)
37
-- `ts/vendor/clack/packages/core/src/` — `@clack/core` (low-level primitives)
38
-
39
-See `ts/packages/cli/AGENTS.md` for detailed Clack usage guidelines.
40
-
41
-**Important:** The submodule is for **read-only reference only**. Do not modify files in `ts/vendor/`. The CLI's actual `@clack/prompts` dependency comes from npm via `pnpm install`.
42
-
43
-## Common Development Commands
44
-
45
-### Build and Development
46
-```bash
47
-# Build all packages
48
-pnpm build
49
-
50
-# Build only TypeScript packages
51
-pnpm build:packages
52
-
53
-# Clean build artifacts
54
-pnpm clean
55
-pnpm clean:workspace
56
-
57
-# Lint code
58
-pnpm lint
59
-pnpm lint:fix
60
-
61
-# Format code
62
-pnpm format
63
-
64
-# Run tests
65
-pnpm test
66
-```
67
-
68
-### Package Management
69
-```bash
70
-# Install dependencies
71
-pnpm install
72
-
73
-# Check peer dependencies
74
-pnpm check:peer-deps
75
-
76
-# Update peer dependencies
77
-pnpm update:peer-deps
78
-```
79
-
80
-### Creating New Components
81
-```bash
82
-# Create a new provider
83
-pnpm create:provider <provider-name> [--agentic]
84
-
85
-# Create a new example
86
-pnpm create:example <example-name>
87
-```
88
-
89
-### Release Management
90
-```bash
91
-# Create changeset for releases
92
-pnpm changeset
93
-
94
-# Version packages
95
-pnpm changeset:version
96
-
97
-# Publish packages
98
-pnpm changeset:release
99
-```
100
-
101
-## Project Architecture
102
-
103
-### Repository Structure
11
```
12
composio/
106
-├── ts/ # TypeScript SDK (main development)
13
+├── ts/
14
│ ├── packages/
108
-│ │ ├── core/ # Core SDK functionality
109
-│ │ ├── providers/ # AI provider integrations (OpenAI, Anthropic, etc.)
110
-│ │ ├── cli/ # Command-line interface
111
-│ │ ├── json-schema-to-zod/ # Schema conversion utility
112
-│ │ └── ts-builders/ # TypeScript code generation utilities
113
-│ └── examples/ # Usage examples for different providers
114
-├── python/ # Python SDK
115
-├── docs/ # Documentation (Fumadocs)
116
-└── examples/ # Cross-platform examples
117
-```
118
-
119
-### Core Packages
120
-
121
-**@composio/core** - Main SDK functionality:
122
-- `src/composio.ts` - Main Composio class
123
-- `src/models/` - Core models (Tools, Toolkits, ConnectedAccounts, etc.)
124
-- `src/provider/` - Base provider implementations
125
-- `src/services/` - Internal services (telemetry, pusher)
126
-- `src/types/` - TypeScript type definitions
127
-- `src/utils/` - Utility functions and helpers
128
-
129
-**Provider Packages** - AI integrations:
130
-- `@composio/openai` - OpenAI integration
131
-- `@composio/anthropic` - Anthropic integration
132
-- `@composio/google` - Google GenAI integration
133
-- `@composio/langchain` - LangChain integration
134
-- `@composio/vercel` - Vercel AI integration
135
-- `@composio/mastra` - Mastra integration
136
-
137
-### Key Concepts
138
-
139
-**Tools** - Individual functions that can be executed (e.g., GITHUB_CREATE_REPO, GMAIL_SEND_EMAIL)
140
-
141
-**Toolkits** - Collections of related tools grouped by service (e.g., github, gmail, slack)
142
-
143
-**Connected Accounts** - User authentication/authorization for external services
144
-
145
-**Auth Configs** - Configuration for different authentication methods
146
-
147
-**Custom Tools** - User-defined tools with custom logic
148
-
149
-**Providers** - Integrations with AI frameworks (OpenAI, Anthropic, etc.)
150
-
151
-**Modifiers** - Middleware to transform tool inputs/outputs
152
-
153
-## Development Workflow
154
-
155
-### For Tool Development
156
-1. Tools are auto-generated from OpenAPI specifications
157
-2. Custom tools can be created using the Custom Tools API
158
-3. Tool execution happens through the main Composio class
159
-
160
-### For Provider Development
161
-1. Use `pnpm create:provider <name>` to scaffold new providers
162
-2. Implement required methods: `wrapTool`, `wrapTools`
163
-3. For agentic providers, also implement execution handlers
164
-4. Add comprehensive tests and documentation
165
-
166
-### Testing
167
-- Unit tests use Vitest
168
-- Run tests with `pnpm test`
169
-- Tests are located in `test/` directories within each package
170
-- Mock implementations are available in `test/utils/mocks/`
171
-
172
-### Code Quality
173
-- ESLint configuration in `eslint.config.mjs`
174
-- Prettier for code formatting
175
-- TypeScript strict mode enabled
176
-- Comprehensive TSDoc documentation required
177
-- Husky pre-commit hooks for quality checks
178
-
179
-## Environment Variables
180
-
181
-```bash
182
-COMPOSIO_API_KEY # Required: Your Composio API key
183
-COMPOSIO_BASE_URL # Optional: Custom API base URL
184
-COMPOSIO_LOG_LEVEL # Optional: Logging level (silent, error, warn, info, debug)
185
-COMPOSIO_DISABLE_TELEMETRY # Optional: Set to "true" to disable telemetry
186
-DEVELOPMENT # Development mode flag
187
-CI # CI environment flag
188
-```
189
-
190
-## Key Files and Locations
191
-
192
-- **Main SDK Entry**: `ts/packages/core/src/index.ts`
193
-- **Core Composio Class**: `ts/packages/core/src/composio.ts`
194
-- **Type Definitions**: `ts/packages/core/src/types/`
195
-- **Error Classes**: `ts/packages/core/src/errors/`
196
-- **Examples**: `ts/examples/` and `examples/`
197
-- **Documentation**: `docs/`
198
-- **Build Configs**: `turbo.jsonc`, `tsconfig.base.json`, `tsdown.config.base.ts`
199
-- **E2E Tests**: `ts/e2e-tests/`
200
-
201
-## Maintenance Tasks
202
-
203
-### When Updating GitHub Actions
204
-
205
-When modifying files in `.github/workflows/`, update the "Prerequisites" section in `ts/docs/internal/release.md` with the current tool versions:
206
-
207
-- **Node.js**: `cat .nvmrc`
208
-- **Bun**: `cat .bun-version`
209
-- **pnpm**: `cat package.json | jq -r .packageManager | cut -d'@' -f2`
210
-
211
-## Testing Commands
15
+│ │ ├── core/ # @composio/core — main SDK
16
+│ │ ├── providers/ # @composio/openai, anthropic, google, langchain, vercel, mastra, ...
17
+│ │ ├── cli/ # @composio/cli — Effect.ts + Bun (see ts/packages/cli/AGENTS.md)
18
+│ │ ├── cli-keyring/ # @composio/cli-keyring — macOS Keychain / Linux Secret Service
19
+│ │ ├── cli-local-tools/ # @composio/cli-local-tools — local toolkit declarations
20
+│ │ ├── json-schema-to-zod/
21
+│ │ └── ts-builders/ # AST builders for code generation
22
+│ ├── vendor/ # Read-only Effect + Clack submodules (do NOT modify)
23
+│ ├── e2e-tests/ # Docker-based Node/Deno/Cloudflare runtime tests
24
+│ └── examples/
25
+├── python/ # Python SDK (composio, providers, examples)
26
+└── docs/ # Fumadocs site (see docs/CLAUDE.md)
27
+```
28
+
29
+## TypeScript Commands
30
31
```bash
214
-# Run all tests
215
-pnpm test
216
-
217
-# Run tests for core package only
218
-cd ts/packages/core && pnpm test
219
-
220
-# Run tests with UI
221
-pnpm test:ui
222
-```
223
-
224
-### TypeScript E2E Tests
225
-
226
-E2E tests for `@composio/core` are located in `ts/e2e-tests/` and test runtime compatibility across different JavaScript environments.
227
-
228
-```bash
229
-# Run all e2e tests (Node.js + Deno + Cloudflare)
230
-pnpm test:e2e
231
-
232
-# Run only Node.js e2e tests (CJS/ESM compatibility, runs in Docker)
233
-pnpm test:e2e:node
234
-
235
-# Run only Deno e2e tests (npm: specifier compatibility, runs in Docker)
236
-pnpm test:e2e:deno
237
-
238
-# Run only Cloudflare Workers e2e tests
32
+pnpm install # First-time setup. Use BYPASS_BUN_VERSION_CHECK=1 if .bun-version mismatch
33
+pnpm build # Build all packages (Turbo)
34
+pnpm build:packages # TS packages only
35
+pnpm lint / lint:fix
36
+pnpm format
37
+pnpm typecheck # MANDATORY before pushing CLI changes
38
+pnpm test # Vitest, all packages
39
+pnpm test:e2e # All runtimes (Node CJS+ESM, Deno, Cloudflare Workers) via Docker
40
+pnpm test:e2e:node # Override with COMPOSIO_E2E_NODE_VERSION=22.12.0
41
+pnpm test:e2e:deno # Override with COMPOSIO_E2E_DENO_VERSION=2.6.7
42
pnpm test:e2e:cloudflare
240
-
241
-# Run Node.js tests with a specific Node version
242
-COMPOSIO_E2E_NODE_VERSION=22.12.0 pnpm test:e2e:node
243
-
244
-# Run Deno tests with a specific Deno version
245
-COMPOSIO_E2E_DENO_VERSION=2.6.7 pnpm test:e2e:deno
246
-```
247
-
248
-**E2E Test Structure:**
249
-```
250
-ts/e2e-tests/
251
-├── _utils/ # Shared Docker infrastructure
252
-├── runtimes/
253
-│ ├── node/ # Node.js runtime tests
254
-│ │ ├── cjs-basic/ # CommonJS compatibility
255
-│ │ └── esm-basic/ # ESM compatibility
256
-│ ├── deno/ # Deno runtime tests
257
-│ │ └── esm-basic/ # npm: specifier compatibility
258
-│ └── cloudflare/ # Cloudflare runtime tests
259
-│ └── cf-workers-basic/ # Cloudflare Workers tests
260
-└── README.md # E2E test documentation
43
+pnpm changeset # Create release changeset (required for stable CLI/SDK releases)
44
+pnpm create:provider <name> [--agentic]
45
+pnpm create:example <name>
46
```
47
263
-> **Note:** When adding new e2e tests, update `ts/e2e-tests/README.md` with the new test information.
48
+Pinned tool versions: Node `.nvmrc` (20.20.2), Bun `.bun-version` (1.3.10), pnpm via `packageManager` in `package.json`. CI sets `BYPASS_BUN_VERSION_CHECK=1`; local sandboxes often need it too.
49
265
-## Common Patterns
50
+## Python Commands
51
267
-### Tool Execution
268
-```typescript
269
-const composio = new Composio({ apiKey: 'your-key' });
270
-const result = await composio.tools.execute('TOOL_NAME', {
271
- userId: 'user-id',
272
- arguments: { /* tool args */ }
273
-});
274
-```
275
-
276
-### Provider Integration
277
-```typescript
278
-import { OpenAIProvider } from '@composio/openai';
279
-const provider = new OpenAIProvider({ apiKey: 'openai-key' });
280
-const tools = await composio.tools.get('user-id', { toolkits: ['github'] });
281
-const wrappedTools = provider.wrapTools(tools);
282
-```
283
-
284
-### Custom Tool Creation
285
-```typescript
286
-import { z } from 'zod';
287
-
288
-const customTool = await composio.tools.createCustomTool({
289
- name: 'My Tool',
290
- description: 'Tool description',
291
- slug: 'MY_TOOL',
292
- inputParams: z.object({
293
- param: z.string().describe('Parameter description')
294
- }),
295
- execute: async (input) => {
296
- // Implementation
297
- return {
298
- data: { result: input.param },
299
- error: null,
300
- successful: true
301
- };
302
- }
303
-});
304
-```
305
-
306
-This monorepo uses pnpm workspaces and Turbo for efficient builds and development.
307
-
308
-## Python SDK Development
309
-
310
-### Setup
311
-The Python SDK is located in the `/python/` directory and uses `uv` for dependency management and `nox` for automation.
312
-
313
-### Environment Setup
52
```bash
315
-# Create and setup Python development environment
53
cd python
317
-make env
318
-source .venv/bin/activate
54
+make env # uv-managed venv with all deps (NOT pre-built in sandboxes)
55
+source .venv/bin/activate # ALWAYS activate before pytest/ruff/pip
56
+make fmt # ruff format
57
+make chk # ruff check + mypy
58
+make tst / make snt # pytest / sanity tests
59
+pytest -m core # Markers: core, openai, langchain, agno
60
+make build / make bump
61
```
62
321
-### Python Development Commands
322
-```bash
323
-# Setup environment (creates virtual env with all dependencies)
324
-make env
325
-
326
-# Sync dependencies (when in an existing environment)
327
-make sync
328
-
329
-# Install provider packages
330
-make provider
331
-
332
-# Format code using ruff
333
-make fmt
334
-# Or directly: nox -s fmt
63
+Python: >=3.10, <4. Formatter/linter: Ruff (88 char). Type checker: mypy strict. Core deps include `composio-client` (Stainless-generated; source repo is `ComposioHQ/composio-base-py`).
64
336
-# Check linting and type issues
337
-make chk
338
-# Or directly: nox -s chk
339
-
340
-# Fix linting issues
341
-nox -s fix
342
-
343
-# Run tests (requires implementing tst session)
344
-make tst
345
-# Or directly: nox -s tst
346
-
347
-# Run sanity tests (requires implementing snt session)
348
-make snt
349
-# Or directly: nox -s snt
350
-
351
-# Clean build artifacts
352
-make clean-build
353
-
354
-# Bump version
355
-make bump
65
+## Environment Variables
66
357
-# Build packages
358
-make build
67
+```bash
68
+COMPOSIO_API_KEY # Required
69
+COMPOSIO_BASE_URL # Optional override
70
+COMPOSIO_LOG_LEVEL # silent | error | warn | info | debug
71
+COMPOSIO_DISABLE_TELEMETRY # "true" to disable
72
```
73
361
-### Python Project Structure
362
-```
363
-python/
364
-├── composio/ # Main SDK package
365
-├── providers/ # Provider implementations
366
-├── tests/ # Test suite
367
-├── examples/ # Usage examples
368
-├── scripts/ # Development scripts
369
-├── config/ # Configuration files
370
-│ ├── pytest.ini # Pytest configuration
371
-│ ├── mypy.ini # MyPy type checking config
372
-│ ├── ruff.toml # Ruff linter/formatter config
373
-│ └── codecov.yml # Code coverage config
374
-├── Makefile # Development shortcuts
375
-├── noxfile.py # Nox automation sessions
376
-└── pyproject.toml # Project configuration
377
-```
74
+## Gotchas
75
379
-### Python Code Quality
380
-- **Formatter**: Ruff (Black-compatible, 88 char line length)
381
-- **Linter**: Ruff with custom configuration
382
-- **Type Checker**: mypy with strict optional typing
383
-- **Test Framework**: pytest with custom markers (core, openai, langchain, agno)
384
-- **Python Version**: >=3.10, <4
385
-- **Dependency Managers**: uv
76
+- **Default branch is `next`**, not `main`/`master`. Branch from `next` and target `next` for PRs.
77
+- **Docs PRs also target `next`** (see `docs/CLAUDE.md` rule).
78
+- `pnpm install` hard-fails on Bun version mismatch — use `BYPASS_BUN_VERSION_CHECK=1`.
79
+- `ts/vendor/effect/` and `ts/vendor/clack/` are **read-only reference submodules** — npm provides the actual deps.
80
+- The CLI is **Effect.ts + Bun**, not plain Node — see `ts/packages/cli/AGENTS.md` (CLI's `CLAUDE.md` is a symlink to it).
81
+- E2E tests run in **Docker** and require Docker daemon access; skip them in restricted sandboxes.
82
+- Tool execution code generation is auto-derived from OpenAPI specs in hermes — don't hand-edit generated files under `@composio/core/generated`.
83
387
-### Python Testing
388
-```bash
389
-# Run tests with pytest markers
390
-pytest -m core # Run core tests only
391
-pytest -m openai # Run OpenAI provider tests
392
-pytest -m langchain # Run LangChain provider tests
393
-pytest -m agno # Run Agno provider tests
394
-```
84
+## Key Files
85
396
-### Python Package Dependencies
397
-- Core: `pysher`, `pydantic>=2.6.4`, `composio-client==1.4.0`, `typing-extensions>=4.0.0`, `openai`
398
-- Dev: `nox`, `pytest`, `ruff`, `langchain_openai`, `fastapi`, `twine`, `click`, `semver`
86
+- Main SDK entry: `ts/packages/core/src/index.ts`
87
+- Core Composio class: `ts/packages/core/src/composio.ts`
88
+- Types: `ts/packages/core/src/types/`, errors: `ts/packages/core/src/errors/`
89
+- Build configs: `turbo.jsonc`, `tsconfig.base.json`, `tsdown.config.base.ts`
90
+- CI release docs to update when bumping toolchain: `ts/docs/internal/release.md` (Node/Bun/pnpm versions)
91
+- Python config: `python/Makefile`, `python/noxfile.py`, `python/config/{pytest.ini,ruff.toml}`
92
400
-### Python Environment Variables
401
-Same as TypeScript SDK, with additional:
402
-```bash
403
-OPENAI_API_KEY # Required for OpenAI provider examples
404
-```
\ No newline at end of file
93
+## See Also
94
+
95
+- `AGENTS.md` — Codex/generic-agent variant of this file
96
+- `docs/CLAUDE.md` — Fumadocs site, link-checker, API-reference versioning
97
+- `ts/packages/cli/AGENTS.md` — CLI architecture, services, commands, release flow
ts/packages/cli/AGENTS.md
+117
-299
@@ -1,18 +1,18 @@
1
# AGENTS.md
2
3
-Instructions for AI agents working on `@composio/cli`.
3
+Instructions for AI agents working on `@composio/cli`. The sibling `CLAUDE.md` is a symlink to this file.
4
5
-## Architecture Overview
5
+## Required Checks
6
7
-The CLI is built on the **Effect.ts ecosystem** and runs on **Bun**. It follows a service-oriented architecture with dependency injection via Effect layers, generator-based control flow (`Effect.gen`), and structured error handling.
7
+When you touch CLI code (anything under `ts/packages/cli/src/`), run `pnpm typecheck` from the repo root before pushing. Fix all type errors. Build/lint failures block CI.
8
9
-## Required Checks
9
+## Architecture
10
11
-When you touch CLI commands (anything under `ts/packages/cli/src/commands/`), you must run `pnpm typecheck` from the repo root. If it fails, fix the issues before proceeding.
11
+The CLI is built on the **Effect.ts ecosystem** and runs on **Bun**. Service-oriented architecture with dependency injection via Effect layers, generator-based control flow (`Effect.gen`), and structured error handling.
12
13
-### Entry Point
13
+### Entry Point — `src/bin.ts`
14
15
-`src/bin.ts` bootstraps the CLI by composing Effect layers and running the root command via `BunRuntime.runMain()`:
15
+Bootstraps the CLI by composing Effect layers and running the root command via `BunRuntime.runMain()`:
16
17
- `CliConfigLive` — @effect/cli behavior (case-sensitive, no auto-correct, no built-ins)
18
- `ComposioUserContextLive` — User authentication state from `~/.composio/`
@@ -21,27 +21,44 @@ When you touch CLI commands (anything under `ts/packages/cli/src/commands/`), yo
21
- `UpgradeBinaryLive` — Self-update from GitHub releases
22
- `BunFileSystem.layer`, `BunContext.layer` — Bun runtime integration
23
24
-Errors are captured via the custom `effect-errors/` module, which provides source-mapped stack traces, Effect span timelines, and formatted output.
25
-
26
-### Commands (`src/commands/`)
27
-
28
-Each command is declared with `@effect/cli`'s `Command.make()` pattern:
29
-
30
-| Command | Description |
31
-| -------------------------------------------------------- | ------------------------------------------------------------------------------------- |
32
-| `composio version` | Display CLI version |
33
-| `composio whoami` | Show logged-in user's API key |
34
-| `composio login [--no-browser] [--no-wait] [--key text] [--user-api-key text] [--org text]` | Login with browser redirect or direct user API key |
35
-| `composio logout` | Clear stored API key |
36
-| `composio upgrade` | Self-update binary from GitHub releases |
37
-| `composio generate` | Auto-detect project language, delegate to `ts` or `py` |
38
-| `composio generate ts` | Generate TypeScript type stubs for toolkits/tools/triggers |
39
-| `composio generate py` | Generate Python type stubs |
40
-| `composio manage <command>` | Manage Composio resources (toolkits, tools, accounts, triggers, logs, orgs, projects) |
41
-
42
-Options use `Options.text()`, `Options.boolean()`, `Options.choice()`, `Options.directory()` with Effect Schema validation.
43
-
44
-### Services (`src/services/`)
24
+Errors are captured via the custom `effect-errors/` module (source-mapped stack traces, Effect span timelines, formatted output).
25
+
26
+### Commands — `src/commands/`
27
+
28
+Each command uses `@effect/cli`'s `Command.make()` pattern. Top-level command files end in `.cmd.ts`; nested command groups live in their own subdirectory with a `<group>.cmd.ts` entry. Current top-level commands:
29
+
30
+| Group / Command | Purpose |
31
+| ------------------------- | ------------------------------------------------------------------------------------------------------ |
32
+| `version` | Display CLI version |
33
+| `whoami` | Show logged-in user info (writes raw API key to stdout when piped — see Output Conventions) |
34
+| `login` | Login with browser redirect or direct user/API key (`--no-browser`, `--no-wait`, `--key`, `--user-api-key`, `--org`) |
35
+| `logout` | Clear stored API key |
36
+| `signup` | Create a Composio account |
37
+| `upgrade` | Self-update binary from GitHub releases |
38
+| `init` | Bootstrap a Composio project in the current directory |
39
+| `install` | Install local-tool integrations |
40
+| `generate {ts|py}` | Generate type stubs (auto-detects project language if no subcommand) |
41
+| `agent` | Manage AI agent presets |
42
+| `toolkits` | List / inspect / version toolkits |
43
+| `tools` | List / inspect / `execute` tools |
44
+| `triggers` | List / manage trigger types |
45
+| `auth-configs` | Manage auth-config resources (`ac_*`) |
46
+| `connected-accounts` | Manage connected accounts (`ca_*`) |
47
+| `connections` | Alias / helper for connected-account flows |
48
+| `orgs` | Manage organizations |
49
+| `projects` | Manage projects |
50
+| `local-tools` | Manage local toolkits (via `@composio/cli-local-tools`) |
51
+| `logs` | View tool-execution logs (`logs-cmd/`) |
52
+| `config` | Read/write CLI config |
53
+| `listen` | Listen for events |
54
+| `proxy` | Proxy authenticated API requests |
55
+| `run` | Run a saved script / preset |
56
+| `dev` | Developer-only utilities |
57
+| `artifacts` | Manage generated artifacts |
58
+
59
+Options use `Options.text()`, `Options.boolean()`, `Options.choice()`, `Options.directory()` with Effect Schema validation. Feature flags live in `feature-tags.ts` and `experimental-features.ts`.
60
+
61
+### Services — `src/services/`
62
63
| Service | Purpose |
64
| ---------------------------------- | ---------------------------------------------------------------------------- |
@@ -50,330 +67,131 @@ Options use `Options.text()`, `Options.boolean()`, `Options.choice()`, `Options.
67
| `ComposioToolkitsRepository` | API client — fetches toolkits, tools, trigger types; validates versions |
68
| `ComposioToolkitsRepositoryCached` | Decorator over base repository with file-based caching and graceful fallback |
69
| `NodeOs` | OS abstraction (`homedir`, `platform`, `arch`) |
53
-| `EnvLangDetector` | Detects project language (TS/Python) from config files and lock files |
54
-| `JsPackageManagerDetector` | Detects npm/pnpm/yarn/bun for helpful install instructions |
70
+| `EnvLangDetector` | Detects project language (TS/Python) from config / lock files |
71
+| `JsPackageManagerDetector` | Detects npm/pnpm/yarn/bun for install instructions |
72
| `UpgradeBinary` | Fetches latest release from GitHub, downloads and replaces binary |
73
57
-### Effects (`src/effects/`)
58
-
59
-Reusable Effect computations for cross-cutting concerns:
60
-
61
-| Effect | Purpose |
62
-| ------------------------------ | --------------------------------------------------------------------- |
63
-| `app-config` | Reads `COMPOSIO_*` env vars (API_KEY, BASE_URL, CACHE_DIR, etc.) |
64
-| `debug-config` | Debug overrides (DEBUG_OVERRIDE_VERSION, etc.) |
65
-| `force-config` | Force flags (FORCE_USE_CACHE) |
66
-| `setup-cache-dir` | Ensures `~/.composio/` directory exists |
67
-| `toolkit-version-overrides` | Parses `COMPOSIO_TOOLKIT_VERSION_<NAME>=<ver>` env vars |
68
-| `validate-toolkit-versions` | Validates overrides against available API versions |
69
-| `with-log-level` | Configures logger from CLI flag or env var |
70
-| `find-composio-core-generated` | Locates `@composio/core` in node_modules (handles pnpm virtual store) |
71
-| `version` | Resolves CLI version from package.json |
72
-| `compare-semver` | Semantic version comparison for upgrade checks |
73
-| `log-metrics` | Formats and logs API request count and bytes transferred |
74
+OS credential storage uses the sibling package `@composio/cli-keyring` (macOS Keychain / Linux Secret Service).
75
75
-### Models (`src/models/`)
76
+### Effects — `src/effects/`
77
77
-Effect Schema definitions for type-safe serialization:
78
+Reusable Effect computations: `app-config` (reads `COMPOSIO_*` env), `debug-config`, `force-config`, `setup-cache-dir`, `toolkit-version-overrides` (parses `COMPOSIO_TOOLKIT_VERSION_<NAME>=<ver>`), `validate-toolkit-versions`, `with-log-level`, `find-composio-core-generated`, `version`, `compare-semver`, `log-metrics`.
79
79
-- `Toolkit` — name, slug, auth_schemes, is_local_toolkit, meta
80
-- `Tool` — name, slug, available_versions, input/output_parameters, description, tags
81
-- `TriggerType` — slug, name, description, input/output parameters
82
-- `UserData` — apiKey, baseURL, webURL (with defaults)
83
-- `Session` — id, status (pending|linked), retrieved session with api_key
80
+### Models — `src/models/`
81
85
-Each model has `fromJSON`/`toJSON` helpers using `JSONTransformSchema()`.
82
+Effect Schema definitions with `fromJSON` / `toJSON` helpers via `JSONTransformSchema()`: `Toolkit`, `Tool`, `TriggerType`, `UserData`, `Session`.
83
87
-### Code Generation (`src/generation/`)
84
+### Code Generation — `src/generation/`
85
89
-Multi-stage pipeline for `composio generate ts` and `composio generate py`:
86
+Pipeline for `composio generate {ts,py}`:
87
91
-1. **Fetch** — Toolkits, tools, trigger types from API (optionally filtered by `--toolkits`)
92
-2. **Index** — Groups tools/triggers by toolkit prefix into a `ToolkitIndex` map
93
-3. **Generate** — Builds TypeScript/Python source using `@composio/ts-builders` AST builders
94
-4. **Transpile** — Optionally converts TS → ESM JS (when writing to @composio/core/generated)
88
+1. **Fetch** — Toolkits, tools, trigger types (filterable via `--toolkits`)
89
+2. **Index** — Groups by toolkit prefix into `ToolkitIndex`
90
+3. **Generate** — Builds TS/Python source using `@composio/ts-builders` AST builders
91
+4. **Transpile** — Optionally converts TS → ESM JS for `@composio/core/generated`
92
96
-Generated output includes toolkit objects, tool/trigger enums, and optionally full type definitions (with `--type-tools`).
93
+`--type-tools` includes full type definitions.
94
98
-### Error Handling (`src/effect-errors/`)
95
+### Configuration
96
100
-Custom error capture and formatting system:
101
-
102
-- **Capture** — Extracts error chain from Effect's `Cause`, handles interrupts separately
103
-- **Source maps** — Maps compiled `.mjs` stack traces back to TypeScript source
104
-- **Spans** — Extracts timing from Effect spans for execution timeline display
105
-- **Pretty print** — Colored, boxed error output with source context and suggestions
106
-
107
-### UI & Output (`src/ui/`)
108
-
109
-- `picocolors` and `ansis` for colored terminal output
110
-- Respects `NO_COLOR` env var
111
-- `@clack/prompts` symbols (`S_BAR`, `S_BAR_H`, `unicodeOr`) for box-drawing in formatted output
112
-- Effect's `Console.log()` / `Console.error()` for output
113
-
114
-### Configuration (`src/cli-config.ts`, `src/constants.ts`)
115
-
116
-- CLI behavior: `showBuiltIns: false`, `autoCorrectLimit: 0`, `isCaseSensitive: true`
117
-- Prefixes: `COMPOSIO_` for app config, `DEBUG_OVERRIDE_` for debug
118
-- User config stored in `~/.composio/`
97
+- CLI: `cli-config.ts` — `showBuiltIns: false`, `autoCorrectLimit: 0`, `isCaseSensitive: true`
98
+- Constants: `constants.ts` — env prefixes (`COMPOSIO_`, `DEBUG_OVERRIDE_`)
99
+- User config: `~/.composio/user-config.json`
100
- Cache files: `toolkits.json`, `tools.json`, `tools-as-enums.json`, `trigger-types.json`
101
121
-### Effect.ts Patterns
122
-
123
-The CLI uses the generator-based syntax throughout:
124
-
125
-```typescript
126
-Effect.gen(function* () {
127
- const service = yield* ServiceName; // resolve dependency
128
- const result = yield* someEffect; // await computation
129
- yield* Effect.log('message'); // side effect
130
- return result;
131
-});
132
-```
133
-
134
-Key patterns:
135
-
136
-- `Effect.all([...], { concurrency: 'unbounded' })` for parallel fetches
137
-- `Layer.provide()` for dependency composition
138
-- `Effect.mapError()` / `Effect.catchTag()` for typed error handling
139
-- `Effect.scoped` for resource cleanup
140
-
102
### Key Dependencies
103
143
-| Package | Role |
144
-| ----------------------- | ------------------------------------------------------------------- |
145
-| `effect` | Core runtime, data types, concurrency |
146
-| `@effect/cli` | Command, Options, Args declaration and parsing |
147
-| `@effect/platform` | FileSystem, Terminal abstraction |
148
-| `@effect/platform-bun` | Bun runtime layer |
149
-| `@clack/prompts` | Terminal UI — prompts, spinners, logs, notes (all output to stderr) |
150
-| `ansis`, `picocolors` | Colored output |
151
-| `@composio/client` | Raw Composio API client |
152
-| `@composio/core` | Core SDK types and constants |
153
-| `@composio/ts-builders` | TypeScript AST code generation |
154
-| `semver` | Version comparison for upgrades |
155
-| `open` | Opens URLs in browser (login flow) |
156
-| `decompress` | Extracts downloaded binaries |
157
-
158
----
104
+`effect`, `@effect/cli`, `@effect/platform`, `@effect/platform-bun`, `@clack/prompts` (terminal UI — stderr by default), `ansis` / `picocolors`, `@composio/client` (Composio API), `@composio/core` (types), `@composio/ts-builders` (AST gen), `@composio/cli-keyring` (OS credential store), `@composio/cli-local-tools` (local toolkit defs), `semver`, `open`, `decompress`.
105
106
## Output Conventions: Composable CLI Output
107
162
-The CLI follows the Unix convention of separating human-readable decoration from machine-readable data:
108
+Follow the Unix convention of separating human-readable decoration from machine-readable data:
109
164
-- **stdout** — data output only (`ui.output()`). This is what scripts and pipes capture.
110
+- **stdout** — data only (`ui.output()`). Captured by pipes / `$(...)` / `> file`.
111
- **stderr** — all decoration (Clack spinners, logs, notes, intro/outro). Visible in terminal, invisible in pipes.
112
167
-### Rules
168
-
169
-1. **All `TerminalUI` methods except `output()` write to stderr** via Clack's `{ output: process.stderr }` option — but only in interactive mode.
170
-2. **`ui.output(data)` writes to stdout only when piped** — it checks `process.stdout.isTTY` and is a no-op in interactive terminals (the human already sees the data via decoration on stderr).
171
-3. **When stdout is piped, ALL decoration is suppressed** — `isInteractive` (`process.stdout.isTTY`) gates every decoration method. Only `ui.output()` writes in piped mode. This keeps `composio whoami | pbcopy` completely silent.
172
-4. **Action commands** (logout, upgrade) produce no stdout data — their output is purely decorative.
173
-5. **Data commands** (whoami, version, login, generate) call both decoration (stderr) and `ui.output()` (stdout). In interactive mode, only decoration is visible. In pipes/scripts, only the raw data is captured.
174
-6. **Never write data to stderr** — decoration methods are for human context only.
175
-7. **Never write decoration to stdout** — it breaks pipes, `$(...)` captures, and `> file` redirects.
176
-
177
-### Pattern
113
+Rules:
114
179
-```typescript
180
-// Data command (e.g., whoami):
181
-yield * ui.note(apiKey, 'API Key'); // Decoration → stderr (human sees pretty box)
182
-yield * ui.output(apiKey); // Data → stdout (scripts capture plain value)
183
-
184
-// Action command (e.g., login):
185
-yield * ui.intro('composio login'); // Decoration → stderr
186
-yield * ui.log.step('Redirecting'); // Decoration → stderr
187
-// No ui.output() call — nothing for scripts to capture
188
-```
189
-
190
-### How it works in practice
115
+1. All `TerminalUI` methods **except `output()`** write to stderr via Clack's `{ output: process.stderr }`, and only in interactive mode.
116
+2. `ui.output(data)` writes to stdout **only when piped** (checked via `process.stdout.isTTY`).
117
+3. When stdout is piped, **all decoration is suppressed** — `composio whoami | pbcopy` is completely silent and clipboard gets the clean key.
118
+4. **Data commands** (whoami, version, login, generate, etc.) call both decoration (stderr) and `ui.output()` (stdout).
119
+5. **Action commands** (logout, upgrade) produce no stdout data — output is purely decorative.
120
+6. **Never** write data to stderr or decoration to stdout.
121
192
-The CLI checks `process.stdout.isTTY` once at startup to determine the output mode:
122
+When adding a new command: ask "Does this produce a value scripts should capture?" — yes → `ui.output(value)` + `ui.log.*`/`ui.note()`. No → decoration only.
123
194
-- **Interactive** (`stdout` is TTY): decoration visible on stderr, `ui.output()` is a no-op.
195
-- **Piped** (`stdout` is NOT TTY): decoration suppressed, `ui.output()` writes raw data to stdout.
124
+## Effect.ts Patterns
125
197
-```bash
198
-composio whoami # Pretty box only (interactive)
199
-composio whoami | pbcopy # Silent — clipboard gets clean key
200
-API_KEY=$(composio whoami) # Silent — variable gets clean key
201
-composio whoami > file.txt # Silent — file gets clean key
126
+Generator-based syntax throughout:
127
203
-composio version # Decorated version (interactive)
204
-composio version | cat # Raw version string
205
-
206
-composio login # All decoration visible, browser opens
207
-composio login 2>/dev/null # Silent (but still opens browser, polls API)
128
+```typescript
129
+Effect.gen(function* () {
130
+ const service = yield* ServiceName; // resolve dependency
131
+ const result = yield* someEffect; // await computation
132
+ yield* Effect.log('message');
133
+ return result;
134
+});
135
```
136
210
-### Adding new commands
137
+Key patterns: `Effect.all([...], { concurrency: 'unbounded' })` for parallel work, `Layer.provide()` for dependency composition, `Effect.mapError()` / `Effect.catchTag()` for typed errors, `Effect.scoped` for resource cleanup.
138
212
-When creating a new command, ask: "Does this command produce a value that scripts should capture?"
139
+## Vendor Reference Sources
140
214
-- **Yes** → Use `ui.output(value)` for the data, `ui.log.*` / `ui.note()` for context
215
-- **No** → Use only `ui.log.*` / `ui.note()` / `ui.intro()` / `ui.outro()` — everything goes to stderr automatically
216
-
217
----
218
-
219
-## Clack Reference Source
220
-
221
-The CLI uses [`@clack/prompts`](https://github.com/bombshell-dev/clack) for interactive terminal UI (prompts, spinners, logs, etc.). A local copy of the Clack source code is available as a git submodule:
222
-
223
-- **Location:** `ts/vendor/clack/`
224
-- **Repo:** [bombshell-dev/clack](https://github.com/bombshell-dev/clack)
225
-
226
-When working on CLI code that involves terminal UI, reference the Clack source for accurate APIs and patterns:
227
-
228
-- `ts/vendor/clack/packages/prompts/src/` — `@clack/prompts` (the high-level API used by this CLI)
229
-- `ts/vendor/clack/packages/core/src/` — `@clack/core` (low-level primitives underlying prompts)
230
-
231
-### Key modules in `@clack/prompts`
232
-
233
-| Module | Purpose |
234
-| ----------------------- | ------------------------------------------------------ |
235
-| `text.ts` | Text input prompt |
236
-| `password.ts` | Password input prompt |
237
-| `confirm.ts` | Yes/no confirmation prompt |
238
-| `select.ts` | Single-select list prompt |
239
-| `multi-select.ts` | Multi-select list prompt |
240
-| `group-multi-select.ts` | Grouped multi-select prompt |
241
-| `autocomplete.ts` | Autocomplete/search prompt |
242
-| `spinner.ts` | Loading spinner |
243
-| `progress-bar.ts` | Progress bar |
244
-| `log.ts` | Styled log messages |
245
-| `note.ts` | Boxed note output |
246
-| `task.ts` | Task runner with status |
247
-| `task-log.ts` | Task with streaming log output |
248
-| `stream.ts` | Streaming text output |
249
-| `box.ts` | Box drawing utility |
250
-| `messages.ts` | Intro/outro messages |
251
-| `common.ts` | Shared symbols (`S_BAR`, `S_BAR_H`, `unicodeOr`, etc.) |
252
-
253
-### Current clack usage in the CLI
254
-
255
-The CLI currently imports from `@clack/prompts`:
256
-
257
-- `S_BAR`, `S_BAR_H`, `unicodeOr` — Unicode box-drawing symbols for custom formatted output
258
-
259
-### Guidelines
260
-
261
-- The submodule is for **read-only reference only**. Do not modify files in `ts/vendor/clack/`.
262
-- The CLI's actual dependency comes from npm (`@clack/prompts` v1.0.1) via `pnpm install`.
263
-- When adding new interactive prompts or terminal UI, consult the source in `ts/vendor/clack/packages/prompts/src/` for the correct API surface and available options.
264
-- Prefer `@clack/prompts` (high-level) over `@clack/core` (low-level) unless you need custom prompt behavior.
265
-
266
----
267
-
268
-## Effect.ts Reference Source
269
-
270
-The CLI is built on the Effect.ts ecosystem. A local copy of the Effect source code is available as a git submodule:
271
-
272
-- **Location:** `ts/vendor/effect/`
273
-- **Repo:** [Effect-TS/effect](https://github.com/Effect-TS/effect)
274
-- **Branch:** `main`
275
-
276
-When working on CLI code, reference the Effect source for accurate patterns:
141
+Read-only submodules under `ts/vendor/` (do NOT modify — actual deps come from npm):
142
143
- `ts/vendor/effect/packages/effect/src/` — core Effect runtime
279
-- `ts/vendor/effect/packages/cli/src/` — @effect/cli (Command, Options, Args)
280
-- `ts/vendor/effect/packages/platform/src/` — @effect/platform (FileSystem, Terminal)
281
-
282
-### Guidelines
283
-
284
-- The submodule is for **read-only reference only**. Do not modify files in `ts/vendor/effect/`.
285
-- The CLI's actual dependencies come from npm via `pnpm install`.
286
-
287
----
144
+- `ts/vendor/effect/packages/cli/src/` — `@effect/cli` (Command, Options, Args)
145
+- `ts/vendor/effect/packages/platform/src/` — `@effect/platform`
146
+- `ts/vendor/clack/packages/prompts/src/` — `@clack/prompts` (text, select, confirm, spinner, note, task, etc.)
147
+- `ts/vendor/clack/packages/core/src/` — `@clack/core` primitives
148
149
## CLI Design Guidelines
150
291
-For principles on how to design CLI interactions (arguments, flags, help text, output, errors, interactivity, config precedence), see:
151
+Principles for arguments, flags, help, output, errors, interactivity, config precedence:
152
293
-- **Cursor rules**: `ts/packages/cli/.cursor/rules/cli-design-guidelines.mdc`
294
-- **Claude skill**: `.claude/skills/create-cli/SKILL.md` (standalone, trimmed for Claude Code context)
153
+- Cursor rules: `ts/packages/cli/.cursor/rules/cli-design-guidelines.mdc`
154
+- Claude skill: `/workspace/zen/skills/create-cli/` (also available as `/create-cli`)
155
296
-Use these guidelines when adding new commands, designing flag interfaces, or making UX decisions for the CLI.
297
-
298
----
156
+Use these when adding new commands or making UX decisions.
157
158
## Recording CLI Demos
159
302
-New commands should have VHS recordings for documentation. The recording script produces SVGs and asciicasts that demonstrate the CLI in action.
303
-
304
-### Adding Recordings
305
-
306
-1. Add entries to `recordings/recordings.yaml` under the appropriate group
307
-2. Run `bun scripts/record.ts` (requires `COMPOSIO_API_KEY` and `vhs` on PATH)
308
-
309
-### Recording Config
310
-
311
-Each entry in `recordings.yaml` accepts:
312
-
313
-| Field | Required | Description |
314
-| ----------------- | -------- | --------------------------------------------------------------------------------------- |
315
-| `name` | Yes | Filename stem (`<name>.svg`, `<name>.ascii`, `<name>.tape`) |
316
-| `command` | Yes | Shell command to record |
317
-| `description` | No | Comment shown instantly above the command (via VHS `Hide`/`Show`) |
318
-| `sleepAfterEnter` | No | Wait time after Enter (default: `6s` from `vhs.sleepAfterEnter`) |
319
-| `height` | No | `'dynamic'` for two-pass auto-sizing, or a fixed pixel number. Omit for default (750px) |
160
+New commands should ship with VHS recordings (SVG + asciicast). Workflow:
161
321
-Use `height: dynamic` for commands with long output (help text, full listings). The recorder probes with 2x height, parses the SVG to measure content, then re-records at the computed height (capped at `vhs.height * 2`).
162
+1. Add entry to `recordings/recordings.yaml` (fields: `name`, `command`, `description`, `sleepAfterEnter`, `height: dynamic` for long output).
163
+2. Run `bun scripts/record.ts` — requires `COMPOSIO_API_KEY` and `vhs` on `PATH`.
164
323
-### Output Structure
324
-
325
-```
326
-recordings/
327
-├── recordings.yaml # Config
328
-├── tapes/<group>/<name>.tape # Generated VHS tape files
329
-├── svgs/<group>/<name>.svg # SVG recordings
330
-└── ascii/<group>/<name>.ascii # Asciicast recordings
331
-```
332
-
333
-### Key Files
334
-
335
-- **Config**: `recordings/recordings.yaml`
336
-- **Script**: `scripts/record.ts` — Bun + Effect.ts, parallel VHS execution
337
-- **Shared tape**: `recordings/tapes/shared-config.tape` — common VHS settings (auto-generated)
338
-
339
----
165
+Outputs land in `recordings/{tapes,svgs,ascii}/<group>/<name>.{tape,svg,ascii}`.
166
167
## Release Workflow
168
343
-CLI releases use a two-channel system: **beta** (automatic) and **stable** (manual promotion).
344
-
345
-### Beta Releases (automatic)
169
+Two channels: **beta** (automatic) and **stable** (manual promotion via changeset).
170
347
-Every push to `next` that touches `ts/packages/cli/**` automatically triggers `.github/workflows/build-cli-binaries.yml`, which:
171
+### Beta (automatic)
172
349
-1. Finds the latest stable `@composio/cli@X.Y.Z` release
350
-2. Computes the next patch version (`X.Y.Z+1`)
351
-3. Builds cross-platform binaries (linux-x64, linux-aarch64, darwin-x64, darwin-aarch64)
352
-4. Creates a GitHub prerelease tagged `@composio/cli@X.Y.(Z+1)-beta.<run_number>`
173
+Every push to `next` touching `ts/packages/cli/**` triggers `.github/workflows/build-cli-binaries.yml`:
174
354
-You can also trigger a beta build from **any branch** via `workflow_dispatch` → `build-beta`.
175
+1. Find latest stable `@composio/cli@X.Y.Z`
176
+2. Compute next patch `X.Y.Z+1`
177
+3. Build cross-platform binaries (linux-x64, linux-aarch64, darwin-x64, darwin-aarch64)
178
+4. Publish GitHub prerelease `@composio/cli@X.Y.(Z+1)-beta.<run_number>`
179
356
-Users install beta releases with `composio upgrade --beta`.
180
+Also triggerable from any branch via `workflow_dispatch` → `build-beta`. Users install with `composio upgrade --beta`.
181
358
-### Stable Releases (via changeset)
182
+### Stable (via changeset)
183
360
-To promote to a stable release:
361
-
362
-1. Create a changeset PR (`.changeset/<name>.md` with `"@composio/cli": patch`)
363
-2. Merge it into `next`
364
-3. The changeset bot creates a "Release: update version" PR that bumps `package.json`
365
-4. Merge that PR → the push to `next` detects the `package.json` version changed → builds a **stable** release (`@composio/cli@X.Y.Z`, marked as `latest`)
184
+1. Create changeset PR (`.changeset/<name>.md` with `"@composio/cli": patch`)
185
+2. Merge into `next`
186
+3. Changeset bot opens "Release: update version" PR bumping `package.json`
187
+4. Merge that PR → push to `next` detects version change → builds **stable** release (`@composio/cli@X.Y.Z`, marked `latest`)
188
5. `ts.release.yml` also publishes to npm
189
368
-### Manual Promotion
369
-
370
-You can also promote an existing beta to stable via `workflow_dispatch` → `promote-stable` with the beta tag (e.g. `@composio/cli@0.2.20-beta.42`).
190
+Promote an existing beta to stable via `workflow_dispatch` → `promote-stable` with the beta tag (e.g. `@composio/cli@0.2.20-beta.42`).
191
372
-### Key Files
192
+### Key Workflow Files
193
374
-| File | Purpose |
375
-| --------------------------------------------- | -------------------------------- |
376
-| `.github/workflows/build-cli-binaries.yml` | Binary build + release workflow |
377
-| `.github/workflows/ts.release.yml` | Changeset bot + npm publish |
378
-| `.github/workflows/cli.test-installation.yml` | Post-release install smoke tests |
379
-| `.changeset/config.json` | Changeset configuration |
194
+- `.github/workflows/build-cli-binaries.yml` — binary build + release
195
+- `.github/workflows/ts.release.yml` — changeset bot + npm publish
196
+- `.github/workflows/cli.test-installation.yml` — post-release install smoke tests
197
+- `.changeset/config.json`