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
- - 28 node overlap risks detected.
- - 10 likely edge crossings may reduce readability.
Click a system in the map
Explore pingdotgg/t3code 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 SPA with TanStack Router for thread management, code review, and terminal interface
Electron wrapper providing native UI, window management, and local server bootstrap
React Native/Expo app with same orchestration protocol for iOS/Android
WebSocket RPC client, state machines, reducers for thread/terminal/vcs state synchronization
Shared OpenAPI/RPC schema definitions for client-server communication
Effect-based HTTP router with REST endpoints and WebSocket upgrade handling
Event sourcing with Decider (command → events) and Projector (events → read model)
AI provider adapters (Codex, Claude, OpenCode) with instance registry and session management
Evidence coverage
What this context is grounded in
Coverage
- Citations
- 8
- Findings
- 5
- Indexed entities
- Unknown
- Relationships
- Unknown