Architecture map
How the repo is organized
Click systems in the graph to inspect responsibilities, important files, and nearby dependencies.
Diagram quality
Generated draft: use it for orientation, then verify components and edges in source before relying on the layout.
Layout checks
- - 1 node overlap risk detected.
- - 24 likely edge crossings may reduce readability.
- - 8 edges flow backward, which can hurt scanability.
Click a system in the map
Explore composiohq/composio by selecting services, gateways, clients, and data stores. Each node shows the files, responsibilities, and neighboring systems an agent should keep in scope.
Pan, zoom, and use the minimap to keep large repos navigable.
Sign up to turn selected graph context into repo-aware agent sessions.
Key systems
What an agent should understand first
Main SDK initialization and model orchestration. Manages SDK configuration, initializes all models, sets up provider integration, and coordinates between components.
Retrieves, transforms, and executes tools. Handles schema conversion, applies modifiers (file upload, hooks), version management, and delegates execution to API client.
Manages toolkit metadata, logos, authorization schemes, and authentication configurations. Provides auth flow initiation.
Manages user OAuth and API key integrations. CRUD operations for authenticated connections to third-party services.
Creates isolated MCP server sessions per user. Manages session lifecycle, tool preloading, and session-specific execution.
Manages webhook event subscriptions. Allows agents to subscribe to and receive events from external services.
Framework-specific adapters that wrap tools in format expected by LLM frameworks (OpenAI, Anthropic, Claude Agents, LangChain, etc.).
HTTP client for Composio backend communication. Handles authentication, request marshalling, and response parsing.
Evidence coverage
What this context is grounded in
Coverage
- Citations
- 7
- Findings
- 5
- Indexed entities
- Unknown
- Relationships
- Unknown