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
SolidJS-based web application and Electron desktop wrapper. Handles session routing, message composition, terminal rendering, and file exploration.
SolidJS context system for state management (ServerSDK, Settings, Tabs, Permissions, Models, Language, Theme)
HTTP API endpoints built with Effect + Hono. Handles authentication, CORS, request validation, and routes to core services.
Event-sourced session management with Effect. Coordinates prompt admission, message handling, execution lifecycle, and agent switching.
Pub/Sub event system with durable event storage. Publishes session events (PromptSubmitted, MessageCreated, ToolOutput) to projectors and subscribers.
Multi-agent orchestration with skill-based tool system. Routes prompts to build/plan agents with shell, diff, file edit, and plugin skills.
Provider-agnostic LLM abstraction with 20+ integrations (OpenAI, Anthropic, Bedrock, Mistral, Cohere, etc). Routes prompts to selected model.
Drizzle-based persistence for sessions, messages, events, credentials, projects, and configuration using SQLite.
Evidence coverage
What this context is grounded in
Coverage
- Citations
- 7
- Findings
- 5
- Files discovered
- 12,804
- Architecture systems
- 13
- Architecture relationships
- 15
- Agent graph
- Agent graph entities
- 1,504
- Agent graph relationships
- 2,524