Architecture of juliusbrussee/caveman
juliusbrussee/caveman is 1,610 source files holding 16,626 symbols across 24 modules, written mainly in Go, JavaScript, Python. The largest module is proxy, with 412 files, and 31 files are entry points into the dependency graph.
How caveman fits together
Traffic from a coding agent goes through the proxy module, the largest module with 412 files. The gateway code in proxy/internal/gateway, including route.go and proxy.go, is listed as a hotspot file. The engine module, started through engine/cmd/caveman-engine/main.go, shrinks logs, JSON and code that the agent sends to a model, and it keeps the original bytes locally so the agent can fetch them later. The browse directory lets an agent read and act on web pages in a local Chrome, and an MCP client starts that server through browse/bin/caveman-browse.mjs before calling its browser tools. The .codex/codex-sessionstart.js hook runs when a Codex session starts, and packages/cli/src/index.ts, a hotspot file, belongs to the command-line package.
Largest modules
- proxy: 412 files and 108,444 lines of code
- packages: 330 files and 86,875 lines of code
- engine: 180 files and 36,219 lines of code
- tests: 102 files and 20,142 lines of code
- shared: 43 files and 9,194 lines of code
- browse: 17 files and 2,692 lines of code
- extension: 17 files and 1,573 lines of code
- src: 17 files and 3,139 lines of code
Languages
By file count: Go 665 files, JavaScript 370 files, Python 108 files, TypeScript 71 files, Shell 6 files, Dockerfile 1 file.
Documentation
Repowise documents caveman in 828 pages generated from the source, 67 of them written explanations of the repository and its modules. Module guides include:
- src/hooks: Agent Hook Lifecycle
More on caveman: summary and FAQ, codebase overview, code health.
Related guide: Best dependency graph tools for monorepos