Architecture map
How the repo is organized
Click systems in the graph to inspect responsibilities, important files, and nearby dependencies.
Architecture map
Use this map to orient around systems, dependencies, and files worth reading first.
Click a system in the map
Explore anomalyco/opencode 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
Command-line interface with yargs parser routing 25+ commands (run, serve, tui, web, debug, etc.)
Solid.js web interface for IDE and session console with server SDK context
OpenTUI-based interactive terminal interface with keybindings and session rendering
Electron wrapper with native PTY and IPC handlers for local server coordination
HTTP API layer with Effect-based routing, location middleware, and authorization
Typed API endpoint groups (sessions, events, models, permissions, fs, pty, etc.)
Durable session execution engine orchestrating LLM interaction loops with tool settlement
Composable context sources with independent refresh lifecycle and durable snapshots
Evidence coverage
What this context is grounded in
Coverage
- Citations
- 7
- Findings
- 5
- Files discovered
- 12,684
- Architecture systems
- 13
- Architecture relationships
- 14
- Agent graph
- Agent graph entities
- 1,403
- Agent graph relationships
- 2,346