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 kevin-liu-01/agent-machines 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
Next.js frontend: overview, machines, terminal, registry, settings
Landing page with agent/runtime/loadout showcase
OAuth2 user auth + public/private metadata storage
Schema + Clerk metadata management for machines, crons, memory, profiles
SSE streaming endpoint for LLM completions via gateway bearer
Chats, terminal, bootstrap, machine state, metrics, benchmarks, registry
Unified interface for Dedalus, E2B, Sprites, Vercel (provision, exec, state, wake, sleep)
REST API wrapper with exponential backoff exec polling
Evidence coverage
What this context is grounded in
Coverage
- Citations
- 8
- Findings
- 5
- Files discovered
- 788
- Architecture systems
- 18
- Architecture relationships
- 24
- Agent graph
- Agent graph entities
- 1,446
- Agent graph relationships
- 1,970