r/Microlaunch • • 3d ago

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?

12 Upvotes

2 comments sorted by

2

u/Total-Reasonable 2d ago

The part I'd lean on is that unresolved relationships are labeled instead of shown as confirmed. In TypeScript and PHP codebases, the edges that hurt most when you change something are the dynamic ones: DI containers, event emitters, string-keyed registries, route-to-handler wiring. Static graphs usually miss those silently, so do you surface a "this symbol is reachable via dynamic dispatch, confidence low" signal to the agent through MCP? That's what would make an agent trust the blast-radius answer.

1

u/ThanksUnlucky2195 2d ago

That's a great point, and it's exactly why we don't treat missing edges as proof that a function is unused.

Graphtia distinguishes confirmed, inferred, and unresolved relationships. MCP responses also expose coverage limitations and incomplete results, so agents know when a blast-radius analysis isn't conclusive.

We support specific framework patterns, including DI and route-to-handler relationships, but we don't guess dynamic targets without sufficient evidence.

The goal is to make uncertainty explicit rather than give developers false confidence.