DWG. SYNAPTIC · CODEBASE GRAPH

Your codebase,
drawn to scale.

Synaptic turns any repo into a persistent, queryable knowledge graph across 30+ languages, then traces exactly what a change would break and serves it to your AI assistant over MCP. One static Rust binary. No runtime.

$ synaptic query "auth flow" 1,950 tokens 31× fewer
Detail A An engineering-schematic drawing of the Synaptic codebase: open-circle symbol nodes joined by construction lines, with three callouts naming the most-connected symbols. REV 0.3.12

An assistant re-reads thousands of files to answer one structural question. Synaptic answers from a compact graph: a fraction of the tokens, none of the dead-end reads.

Fig. 2 · Token economy

What one query costs.

Read the source
60,900
One Synaptic query
1,950
31×

fewer tokens to answer one structural question. The ratio grows with the size of the repo.

Exact cl100k counts on Synaptic's own source (199 files, 510,966 tokens). 27 to 38× across six questions. See the full breakdown →

Sheet 02 · Capabilities

Six tools over the graph.

Every inferred relationship is tagged EXTRACTED, INFERRED, or AMBIGUOUS, so you can audit what the graph believes before you trust it.

1 Datum part · reverse impact

Trace what a change breaks, before you make it.

$ synaptic affected parse_config

Every other capability dimensions off this one. affected walks the real call, import, and dispatch edges to bound a change's blast radius; predict forecasts it, and speculate proves it by running the at-risk tests in a throwaway worktree. Synaptic never edits your source.

BLAST RADIUS parse_config AFFECTED: 5 SYMBOLS
Part 2 · Graph & query
$ synaptic query "session reaper"

Query relationships, not text.

Relevance-ranked subgraph search, shortest paths, and node explanations over a graph of symbols and relationships in 30+ languages.

Part 3 · Dynamic dispatch
$ synaptic hazards

A "0 dependents" answer that means it.

Event buses, Electron IPC, reflection and dispatch tables are modeled or cataloged, so an empty result is never mistaken for "safe to change."

Part 4 · Safe refactor
$ synaptic refactor rename

A plan an agent applies, then verifies.

Rename, move, or extract emits a confidence-scored edit plan; verify rebuilds and checks the graph held. The tool proposes, it never edits.

Part 5 · SQL audit
$ synaptic sql audit

Queries linked to the tables they touch.

Flags row-level-security gaps, over-broad grants, likely injection, missing indexes, SELECT * and N+1 over a SQL-aware graph.

Part 6 · MCP server
$ synaptic serve

The graph, handed to your assistant.

28 read-only tools over stdio or HTTP, so your AI assistant queries the graph before it greps or reads a single file.

Dwg. 3D-01 · the live graph

The same graph, live in 3D.

The drawing above is Synaptic's own codebase. Open the explorer to search, orbit, and inspect any node in three dimensions, then load the whole graph.

Open the 3D explorer

nodes5,902
edges18,509
communitiescore 1.2k
renderwebgl
Sheet 03 · Bill of materials 30+ languages

Each language is built and tested in isolation in CI. Highlighted rows are Tier 1.

Sheet 04 · Assembly procedure

One command to a full graph.

Builds with a stable Rust toolchain, or grab a prebuilt binary for Linux, macOS, or Windows.

SH install
# from a clone: installs the `synaptic` binary onto PATH
$cargo install --path bin/synaptic
 
# ...or build it in-tree
$cargo build --release → target/release/synaptic
 
# prebuilt binaries: Linux · macOS · Windows → Releases
synaptic extract .
build the graph → synaptic-out/
synaptic query "authentication flow"
ask the graph a question
synaptic affected parse_config
what would changing this break?
synaptic serve
hand the graph to your AI assistant over MCP
Synaptic · sheet 01 of 04 · rev 0.3.12 Approved for use

Point it at your own repo.