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
- - 11 node overlap risks detected.
- - 9 likely edge crossings may reduce readability.
- - 3 edges flow backward, which can hurt scanability.
Click a system in the map
Explore warpdotdev/warp 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
OSS binary bootstrapping and channel configuration
Main app lifecycle, platform initialization, feature flags, Tokio setup
Entity-Component-Handle UI pattern, view lifecycle, rendering pipeline
PTY management, shell integration, block list viewport, output buffering
Agent SDK driver, task execution, tool call handling, LLM streaming
Conversation state management, multi-turn workflows, artifact handling
Diesel ORM, schema management, migrations, conversation/session storage
Server API communication, subscriptions, cloud object synchronization
Evidence coverage
What this context is grounded in
Coverage
- Citations
- 7
- Findings
- 5
- Indexed entities
- Unknown
- Relationships
- Unknown