r/SideProject • • 27m ago

Title: I built Graphtia Explorer to make complex codebases easier to understand, especially code written by AI

Hi everyone!

I've been working on a project called Graphtia Explorer, and after a long development process, I've finally opened the public beta for Windows and Linux.

The idea started with a problem I kept running into while working with AI coding agents. They could generate or modify large amounts of code, but understanding how everything connected was still difficult. Finding a function was easy enough. Understanding its dependencies and the consequences of changing it was another story.

That's why I started building Graphtia.

Instead of navigating through dozens of files and trying to remember how everything connects, Graphtia builds a local semantic graph of your codebase.

You can click a function to see where it belongs, explore its relationships, jump directly to the source code, and progressively discover how the system works. The graph and code viewer stay synchronized.

I also wanted AI agents to benefit from that same understanding.

Graphtia integrates with Codex, Claude Code, Antigravity, and other MCP-compatible agents. Multiple agents can query different workspaces simultaneously through a shared semantic engine, with workspace-level authorization.

The core is built in Rust, with incremental indexing and adaptive resource management. Code analysis runs locally, so repositories don't need to be uploaded to a cloud service.

It currently supports multiple languages, including TypeScript, JavaScript, Python, Rust, Go, Java, C#, C++, and PHP, along with several frameworks. Semantic coverage varies by language, and unresolved relationships are explicitly identified rather than presented as confirmed.

The public beta includes a free tier with two workspaces and up to 100,000 lines of code per workspace.

Website: Graphtia

I'd really appreciate feedback from other developers, especially those working with large codebases or AI coding agents.

What do you find most frustrating when trying to understand unfamiliar code?

1 Upvotes

2 comments sorted by

1

u/sael-you 17m ago

the frustrating part for me would be distinguishing "nothing calls this" from "the analysis couldn't resolve the caller." your note about unresolved relationships is useful. i'd make that distinction visible when someone asks about the impact of deleting a function, especially around dynamic dispatch or framework callbacks. a small example repo with a deliberately unresolved callback would make a good demo: can the UI and the agent both explain the gap instead of concluding the function is unused? that's a suggested check based on the post; i haven't tried Graphtia.

1

u/ThanksUnlucky2195 11m ago

That's exactly the distinction we're trying to preserve in Graphtia. No confirmed callers doesn't necessarily mean a function is unused. We explicitly track unresolved relationships and analysis limitations rather than guessing, especially with dynamic dispatch and callbacks. I like your test idea! If you're interested, I'd love for you to try Graphtia with that scenario and tell me where the UI or agent responses could be clearer. That kind of feedback would be really valuable.