Kshitij Jhunjhunwala
50d43960eb
## What Sends CLI telemetry **directly to PostHog** (project 196278) instead of through Apollo/Segment, and stitches the anonymous install identity to the Apollo user at login. This unlocks the previously-dark top of the CLI adoption funnel (install → setup → login → connect → execute). ### Why Two live funnel breaks in PostHog today: 1. **Install/setup/plugin events were dark.** Pre-login, `dispatch.ts` had no API base URL (→ endpoint null → dropped), and Apollo's ingest 401s anonymous requests. So `CLI_INSTALL_*`/`CLI_SETUP_*` never arrived. 2. **Identity split.** CLI/server events landed on *email*-keyed PostHog persons (via Segment); dashboard onboarding on *UUID*-keyed persons — the two never joined. The CLI already knows the canonical Apollo UUID (`org_member.id` from session info), so it can self-stitch with no platform/dashboard change. ## How - **Direct transport.** New PostHog capture path (`captureToPostHog`) reusing the existing detached best-effort worker. No dependency on the API base URL, so **pre-login events send**. - **Identity.** Pre-login `distinct_id = install_id`; at login `linkApolloIdentityForAnalytics(org_member.id)` persists the UUID to `~/.composio/analytics.json` and fires one `$create_alias` (`install_id → org_member.id`); post-login events key on the persisted `apollo_user_id`. Because onboarding is already UUID-keyed, the CLI funnel now joins web onboarding. - **Public key, baked at build.** The write-only `phc_` project key is injected via `bun build --define` from the `COMPOSIO_POSTHOG_KEY` env (CI Actions **variable**), never committed to source. `--define` (not a second `--env`) is deliberate — Bun honors only the last `--env`, which would clobber the existing `DEBUG_OVERRIDE_*` bake. For this OSS repo this keeps the key out of git history and means **forks / local builds compile a no-op binary** (only official releases carry the key). - **Direct-only:** the Apollo `/cli/analytics` send is dropped for CLI events; the CLI attaches its own `org_id` (project_id is per-session; a follow-up). ## Guards No-op (no send, no worker spawn, no identity-file write) when telemetry is disabled (`COMPOSIO_CLI_TELEMETRY_DISABLED`/`TELEMETRY_DISABLED`/`COMPOSIO_DISABLE_TELEMETRY`/`CI`/`NODE_ENV=test`) or when no project key is configured. Alias fires once per install (idempotent). No user API key or tool-arg values in event properties. ## Verification - `pnpm typecheck`, `validate:boundaries`, full CLI vitest (**954 passed / 1 skipped**) — green. - Independent code review pass; findings addressed (spawn-gated-on-key, disabled=no-file, idempotent alias). - **Live cold-install trace:** built the real compiled binary with the key baked, ran it from a throwaway `$HOME` → fresh `install_id` → 2 pre-login events delivered to `us.i.posthog.com` with **HTTP 200** → confirmed queryable in PostHog 196278 within ~10s, keyed by `install_id`. ## Notes - CLI is Changesets-ignored; human note added to `CHANGELOG.md` directly. - Requires the `COMPOSIO_POSTHOG_KEY` Actions variable to be set for official release builds (done). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
composio.dev • Documentation • Quickstart • Changelog
Composio
Composio gives your AI agents 1000+ pre-authenticated toolkits, per-user sessions, authentication, triggers, and a sandbox, so you can ship agents that turn intent into action.
This is the Composio SDK monorepo. It contains:
@composio/core: TypeScript SDKcomposio: Python SDKcomposioCLI: search, execute, and script tools from your shell- Provider adapters for OpenAI Agents, Claude Agent SDK, Vercel AI SDK, LangChain, and more
Quickstart
Create a session for a user, hand its tools to your agent, and let the agent take action across 1000+ apps. Grab a COMPOSIO_API_KEY from the dashboard first.
TypeScript
npm install @composio/core @composio/openai-agents @openai/agents
@composio/coreintentionally packages its TypeScript source and SDK docs so the installed package is inspectable to coding agents. If you want a smaller install with the same API, use@composio/slim.
import { Composio } from "@composio/core";
import { OpenAIAgentsProvider } from "@composio/openai-agents";
import { Agent, run } from "@openai/agents";
const composio = new Composio({ provider: new OpenAIAgentsProvider() });
// Each session is scoped to one of your users
const session = await composio.create("user_123");
const tools = await session.tools();
const agent = new Agent({
name: "Personal Assistant",
instructions: "You are a helpful assistant. Use Composio tools to take action.",
tools,
});
const result = await run(agent, "Summarize my emails from today");
console.log(result.finalOutput);
Python
pip install composio composio-openai-agents openai-agents
from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner
composio = Composio(provider=OpenAIAgentsProvider())
# Each session is scoped to one of your users
session = composio.create(user_id="user_123")
tools = session.tools()
agent = Agent(
name="Personal Assistant",
instructions="You are a helpful assistant. Use Composio tools to take action.",
tools=tools,
)
result = Runner.run_sync(starting_agent=agent, input="Summarize my emails from today")
print(result.final_output)
By default a session gets meta tools that discover, authenticate, and execute app tools at runtime, so you don't load hundreds of tool definitions into context. Store session.session_id and reuse it with composio.use() across turns. See what a session is and configuring sessions for restricting toolkits, auth configs, and connected accounts.
Prefer MCP? Every session also exposes a hosted MCP endpoint. Pass mcp: true to composio.create() and point Claude, Cursor, or any MCP client at session.mcp.url. See sessions via MCP.
CLI
The composio CLI runs Composio from your shell and gives coding agents like Claude Code a local tool surface.
curl -fsSL https://composio.dev/install | bash
composio login
Use composio search to find tools, composio execute to run them, composio link to connect accounts, and composio run to script workflows in TypeScript. See the CLI docs.
Providers
A provider adapts Composio tools to your agent framework's native tool format:
| Provider | TypeScript | Python |
|---|---|---|
| OpenAI | @composio/openai |
composio-openai |
| OpenAI Agents | @composio/openai-agents |
composio-openai-agents |
| Anthropic | @composio/anthropic |
composio-anthropic |
| Claude Agent SDK | @composio/claude-agent-sdk |
composio-claude-agent-sdk |
| Vercel AI SDK | @composio/vercel |
— |
| Google GenAI | @composio/google |
composio-gemini, composio-google |
| Google ADK | — | composio-google-adk |
| LangChain | @composio/langchain |
composio-langchain |
| LangGraph | via @composio/langchain |
composio-langgraph |
| LlamaIndex | @composio/llamaindex |
composio-llamaindex |
| Mastra | @composio/mastra |
— |
| Pi | @composio/experimental* |
— |
| Cloudflare Workers AI | @composio/cloudflare |
— |
| CrewAI | — | composio-crewai |
| AutoGen | — | composio-autogen |
* The Pi provider is experimental and ships from @composio/experimental.
Don't see your framework? Build a custom provider, or skip providers entirely and connect over MCP.
All packages
Everything published from this repo:
| Package | Description |
|---|---|
@composio/core |
TypeScript SDK |
@composio/slim |
@composio/core without packaged source or docs; same API, smaller install |
composio CLI |
Standalone CLI binary: curl -fsSL https://composio.dev/install | bash |
@composio/experimental |
Experimental integrations, including the Pi provider |
@composio/json-schema-to-zod |
JSON Schema to Zod conversion |
@composio/* provider adapters |
OpenAI, OpenAI Agents, Anthropic, Claude Agent SDK, Vercel, Google, LangChain, LlamaIndex, Mastra, Cloudflare |
composio |
Python SDK |
composio-* provider adapters |
OpenAI, OpenAI Agents, Anthropic, Claude Agent SDK, Gemini, Google, Google ADK, LangChain, LangGraph, LlamaIndex, CrewAI, AutoGen |
Repository layout
ts/ TypeScript SDK workspace
packages/core/ @composio/core
packages/providers/ Provider adapters
packages/cli/ Composio CLI
python/ Python SDK and provider packages
docs/ Documentation site (docs.composio.dev)
The TypeScript SDK is tested against Node 22+; the Python SDK supports Python 3.10+.
Development
mise install # pinned toolchain (Node, Python, pnpm)
pnpm install
pnpm build
pnpm test
Python commands run from python/; see python/README.md. We welcome contributions to both SDKs; read the contribution guidelines before submitting pull requests.
Support
License
MIT. See LICENSE.