# Show HN: Atlas – Local Dependency Graph

> Source: <https://atlas-repo-wu76.vercel.app/>
> Published: 2026-07-21 22:07:49+00:00

# Know what may break

before the code changes.

Atlas maps your repository into persistent, evidence-backed memory — so you and your coding agent (Claude Code, Cursor, Codex) see likely blast radius before a change, locally, across every session.

Windows · Free to use · No signup required · Local-first · Your code stays on your machine

01 · Scan

## Atlas maps your repository.

Files, symbols, imports and callers — resolved into a dependency graph and an evidence store. Entirely on your machine.

- resolving files
- resolving symbols
- resolving imports
- building relationships

02 · Memory

## Memory that survives across sessions.

The map is written to disk and validated against the live repo before reuse. A fresh agent session restores it in milliseconds — no re-exploration.

03 · Retrieval

## Your agent asks; Atlas answers with citations.

Claude Code, Cursor and Codex request context over MCP. Atlas returns the exact files — cited, ranked, with the reason each was selected. No model in the loop; deterministic lookups.

04 · Persistent memory

## Give your coding agent a persistent

understanding of your project.

Windows · v1.0.5 · MCP · 18 tools · no signup

Capabilities

## Read your codebase as a graph.

Three views of the same indexed repository, each grounded in cited files. No model in the retrieval loop — deterministic lookups against the local index.

- 01
### Graph

Where behavior lives, why a module matters, which files are involved — read straight off the dependency graph built from your local index.

- 02
### Impact

The files a change is likely to affect and the dependency paths between them, before you touch a subsystem.

- 03
### Debug

Start from an error or symptom; Atlas parses the traceback to repo files and symbol spans and returns an investigation path.

Integrations

## Built for the agents you already use.

[All integrations](/integrations)

```
{
  "mcpServers": {
    "atlas": { "command": "Atlas.exe", "args": ["--mcp"] }
  }
}
```

The same local index serves every agent — your source never leaves the machine. Exact per-client setup is in the [docs](/docs).

Proof

## Measured, not marketed.

[Methodology & limits](/benchmarks)

Self-measured on one Windows machine against a reference repository, not a random OSS sample. Every number has a reproducible harness in the repo.

Local-first

## Your repo is indexed on your machine.

Atlas scans local files, builds a repository map, and returns cited answers from that local index. It does not upload your repository to a hosted analysis service.

## Do I need an account to download Atlas?

No. Download the Windows installer and start locally — there's a guest mode with no signup.

## Does Atlas replace my AI coding agent?

No. Atlas gives Claude Code, Cursor, and Codex a persistent, cited memory of your repository that they can use.

## Does Atlas upload my source code?

No. Repository indexing runs on your machine. You decide what context to send to an agent.

## How is this different from repeated file search?

Atlas builds a dependency graph + evidence store once and restores it in milliseconds across sessions, returning ranked, cited files — not a fresh grep each time.