page.tsx
ObsidianGraph.tsx
VoiceNavigator.tsx
navigate/route.ts
analyze/route.ts
graph.ts
graph-cache.ts
ollama.ts
resolver.ts
walker.ts
benderrender
PreviewUnderstand unfamiliar codebases through a visible graph before you start changing files.
benderrender maps repository structure, ranks credible entry points, keeps the route inspectable, and explains why a file matters while the surrounding project context stays on screen.
graph context -> ranked entry surface -> grounded summary
Project context
Visible route
Grounded summaries
Local AI ready
Product
One graph for the first hour inside a new repository.
The product surface stays simple: map the project, route intent through the graph, and explain the destination with enough context to make the next decision easier.
Workflow
Built around the moments where developers lose orientation.
benderrender is focused on the early comprehension bottleneck: where to start, which files matter, and how to trust the next jump inside a large codebase.
Map
Turn a repo into visible structure.
Walk files, resolve imports, and surface the project as a graph instead of a flat tree.
Route
Navigate by intent, not exact path.
Use ranked entry surfaces and graph neighbors to land on the most credible destination faster.
Explain
Keep summaries tied to structure.
Show why the file matters through connected nodes, nearby modules, and the route that led there.
Review
Leave the next action with the developer.
The route is inspectable before opening files or changing code, so the product supports judgment instead of replacing it.
Signals
Research and product flow point at the same bottleneck.
The underlying claim is simple: code understanding takes real time, visual context helps, and the current benderrender flow reduces the first search surface before editing even starts.
Use visual context to narrow the first search surface before code
changes begin.
Surface one
Map
Give developers a real sense of project shape from the first screen instead of asking them to guess where meaning starts.
- whole-project view
- central nodes first
- context before search
Route
Route intent through entry surfaces and connected files so the jump feels guided, not arbitrary.
- ranked starting points
- visible path
- relevant neighbors
Surface three
Explain
Keep the explanation grounded in structure, lines, and nearby modules so the summary is easier to trust and verify.
- line-backed summary
- structural context
- review before action
Proof
Visual proof points behind the product story.
58%
program comprehension load
55.8%
AI-assisted speed gain
4 / 6
visual overview advantage
278x
smaller initial search surface
Grounded output works better when the route stays inspectable.
benderrender is strongest when it reduces the first-hour tax of figuring out where a large codebase actually starts to make sense. The graph, the route, and the explanation reinforce each other.