How jofyni/code-atlas works
CodeAtlas is a local Claude Code workbench: the user submits a request, Claude works in the selected project through the Python bridge, and the browser UI streams activity into a live code graph. The graph also supports review, approval, rollback, execution and analysis. The README documents these capabilities, but the sampled bridge excerpts do not expose most route-level wiring, so relationships below are limited to documented flows; the bridge is a monolithic implementation.
Main entry points: codeatlas_bridge.py Local bridge · CodeAtlasLab.jsx Live code graph
Components 19
Work session
- Workbench UI
src/CodeAtlasLab.jsx - Local bridge
codeatlas_bridge.py - Activity stream
codeatlas_bridge.py - Live code graph
src/CodeAtlasLab.jsx
Review and control
- Command approvals
codeatlas_bridge.py - Change review
src/CodeAtlasLab.jsx - Snapshots and rollback
codeatlas_bridge.py
Execution and tests
- Program runner
codeatlas_bridge.py - Live call trace
codeatlas_bridge.py - Test runner
codeatlas_bridge.py
Project insight
- MCP graph tools
codeatlas_bridge.py - Impact analysis
codeatlas_bridge.py - Architecture analysis
codeatlas_bridge.py
Planning and teams
- Idea-to-task pipeline
codeatlas_bridge.py - Quality gate
codeatlas_bridge.py - Team agents
codeatlas_bridge.py
Other components
- Developer
- Claude Code
- Project files
Connections 26
- Developer → Workbench UI: submits request
README.md - Workbench UI → Local bridge: sends session
README.md - Local bridge → Claude Code: runs Claude Code
README.md - Claude Code → Project files: reads and edits
README.md - Local bridge → Activity stream: streams steps
README.md - Activity stream → Live code graph: updates graph
README.md - Developer → Command approvals: reviews commands
README.md - Command approvals → Claude Code: allows or denies
README.md - Local bridge → Snapshots and rollback: saves checkpoint
README.md - Developer → Change review: reviews changes
README.md - Change review → Snapshots and rollback: requests rollback
README.md - Developer → Program runner: starts program
README.md - Program runner → Live call trace: captures calls
README.md - Live call trace → Live code graph: shows trace
README.md - Developer → Test runner: runs tests
README.md - Claude Code → MCP graph tools: queries graph
README.md - MCP graph tools → Live code graph: reads project graph
README.md - Developer → Impact analysis: requests impact
README.md - Impact analysis → Test runner: identifies affected tests
README.md - Developer → Architecture analysis: reviews architecture
README.md - Developer → Idea-to-task pipeline: defines idea
README.md - Idea-to-task pipeline → Claude Code: assigns tasks
README.md - Quality gate → Test runner: checks tests
README.md - Quality gate → Claude Code: returns failures
README.md - Developer → Team agents: starts team work
README.md - Team agents → Project files: uses Git worktrees
README.md