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
- - 29 node overlap risks detected.
- - 13 likely edge crossings may reduce readability.
- - 4 edges flow backward, which can hurt scanability.
Click a system in the map
Explore bubblelabai/bubblelab 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
React IDE for building, editing, and testing BubbleFlows with visual flow editor, parameter configuration, and execution monitoring
Clerk authentication, JWT token validation, OAuth state management, user session tracking
REST API router, request validation, OpenAPI documentation, middleware orchestration for all endpoints
TypeScript code parsing, BubbleFlow AST extraction, parameter detection, type validation, error reporting
Dynamic TypeScript code execution, BubbleFlow instantiation, context injection, execution lifecycle orchestration
70+ service integrations (Slack, Salesforce, PostgreSQL, GCP, etc.), plugin instantiation, capability metadata, type safety
HTTP webhook routing, Slack event processing (URL verification, events, messages), trigger matching, event transformation
OAuth flow orchestration, credential encryption/storage, token refresh, provider-specific auth handling (Google, Slack, Salesforce, etc.)
Evidence coverage
What this context is grounded in
Coverage
- Citations
- 8
- Findings
- 5
- Indexed entities
- Unknown
- Relationships
- Unknown