Documentation

Graphtia documentation · feature

Explorer overview

Move between a project’s code graph and the source that gives it meaning.

Keep the question and the source together

Explorer provides a project tree, a graph of indexed relationships, source viewing and an inspector. These surfaces answer different questions. The tree locates an item; the graph explains nearby structure; the source shows the implementation; the inspector carries identity and evidence.

Explorer on Windows with checkout-service.ts selected, verified TypeScript source, file tree, inspector and a filtered graph.
The commerce-platform example is locally indexed. The source pane verifies checkout-service.ts against the published revision, while the graph identifies its filtered scope: seven nodes and eight relationships in view.

A first investigation

  1. Open an indexed project and search for a recognizable module, such as checkout-service.ts.

  2. Select the result and open graph + code. Check the source path before drawing a conclusion from a similar name.

  3. Inspect the relationships around the module. Use dependencies to examine what it needs, and dependents to investigate consumers.

  4. Check the indexed revision and any view notices. Read the source behind the relationship that matters to your question.

What the graph can tell you

The engine implements files, symbols, callers, callees, dependencies, dependents, references, paths, neighborhoods, impact candidates, related tests and findings. Results carry bounds and revision context. Availability and precision can differ by language and query.

Choose the right view

  • Code: navigate files and symbols, inspect relationships and read source evidence.

  • API & DB: inspect API declarations, incoming and outgoing endpoints, SQL schemas and supported database uses in code.

  • Documents: read and search indexed project documentation, keeping prose separate from executable code.

  • AI agents: connect a supported agent or a compatible MCP client to ask focused questions about the same workspace.

Panel availability follows the installed Explorer version. If a panel described here is missing, check the version and available updates; an empty view does not prove that the project has no such information.

What you can use today

Explorer is available to eligible Beta members on Windows x64 and Ubuntu Linux x64. Sign in and open Account → Beta for the installers available to your account. A Free account does not itself grant Beta membership. Public downloads and paid checkout are not offered by this private release.

Explorer provides graph and source exploration, symbol search, dependencies, impact candidates, related tests, findings, API and database inspection, indexed documents and supported agent integrations. Coverage depends on the source language, supported constructs and indexed revision. The separate Audit/Argus review workflow is not enabled in this version; structural findings and impact views are separate features.

The current Free allowance is two local workspaces per installation and 100,000 source lines of code per workspace. Open your account’s Products page to see the access assigned to you. Beta membership controls private downloads separately from your product plan.

Graphtia

This page is on its way. Join the waitlist to hear what’s next for Graphtia.

Join waitlist