mirror of
https://github.com/ComposioHQ/composio.git
synced 2026-09-22 11:46:35 +08:00
Alberto Schiabel
f8a6483cfb
This PR: - builds on top of https://github.com/ComposioHQ/composio/pull/4475 - stores `composio execute` responses over 40,000 UTF-8 bytes in a session file, replacing the check for more than 10,000 o200k tokens added in https://github.com/ComposioHQ/composio/pull/2979 - keeps `tokenCount` in the stored-output summary as an estimate (`ceil(sizeBytes / 4)`), adds `sizeBytes`, and logs `Response stored in <path> (N KB, ~M tokens)` - removes `js-tiktoken` and the `execute-output-encoder-runtime` companion from https://github.com/ComposioHQ/composio/pull/4469, with its tsdown entry, build-guard and startup-import patterns, upgrade fixture entry, and the encoder fallback and special-token tests - keeps `execute-output-encoder-runtime.mjs` in the three uninstall lists, so installs that shipped it can still remove the leftover file - behavior change: a 10–40KB response of more than 10,000 tokens now prints inline, and dense non-ASCII output (about 1–2 bytes per token) can print inline at up to ~20,000 tokens - verified: CLI typecheck, full CLI vitest (131 files, 1343 passed, 1 skipped), `test/release-workflow.test.ts`, and `build-companion-modules.ts` with the executable graph check ## Context Nothing reads `tokenCount` as a number: it appears only in the stored-output summary, the two log lines, session history, and a debug log in `run-helpers-runtime.ts`. o200k is not the tokenizer of the model that reads the output, so the exact count only moved the cutoff. It cost the 2.3MB rank table, ~330ms after large tool calls (measured in #4469, not re-measured here), and a separately shipped companion whose absence made `composio run` require a repair download after an upgrade.
Composio TypeScript workspace
This directory contains the TypeScript half of the Composio SDK monorepo: the core SDK, provider adapters, the CLI, examples, and end-to-end tests. For an overview of Composio itself, start at the root README and docs.composio.dev.
If you just want to use the SDK:
npm install @composio/core
import { Composio } from '@composio/core';
const composio = new Composio({ apiKey: process.env.COMPOSIO_API_KEY });
const session = await composio.create('user_123');
const tools = await session.tools();
See the @composio/core README and the quickstart for the full flow, including provider setup for your agent framework.
Packages
Published packages:
| Package | Description |
|---|---|
@composio/core |
The Composio SDK. Ships its TypeScript source and SDK docs so installed copies are inspectable by coding agents. |
@composio/slim |
Same API as @composio/core without the packaged source and docs; smaller install. |
composio CLI |
Standalone CLI binary: search, execute, and script tools from your shell. |
@composio/* providers |
Adapters that format Composio tools for agent frameworks (OpenAI, Anthropic, Vercel AI SDK, LangChain, and more). See the provider table. |
@composio/experimental |
Experimental integrations, currently the Pi provider. |
@composio/json-schema-to-zod |
JSON Schema to Zod conversion. |
Internal (unpublished) packages: cli-keyring and cli-local-tools support the CLI; ts-builders generates TypeScript source.
Layout
ts/
packages/ Published and internal packages (see above)
examples/ Runnable examples per feature and framework
e2e-tests/ Runtime E2E tests (Node, Deno, Cloudflare Workers, CLI)
docs/ Workspace SDK docs: API notes and internal guides
scripts/ Build, validation, and scaffolding scripts
vendor/ Read-only reference submodules; do not edit
Development
Commands run from the repository root. Install the pinned toolchain first:
mise install
pnpm install
Build and verify:
pnpm build:packages # build all TS packages
pnpm typecheck # typecheck all TS packages
pnpm lint:packages # oxlint over ts/packages
pnpm test # package unit tests plus example validation
Runtime E2E suites (require credentials):
pnpm test:e2e:node
pnpm test:e2e:deno
pnpm test:e2e:cloudflare
pnpm test:e2e:cli
Scaffolding:
pnpm create:provider <name> [--agentic] # new provider package
pnpm create:example <name> # new example under ts/examples
Changesets are required for changes to published packages; see the contribution guidelines.