Compass
Integrations

One graph. Every handoff.

Meet Compass where the work already happens: in the editor, beside an assistant, inside automation, or in the artifact your team shares. Every surface starts from the same local, evidence-backed snapshot.

Install Compass

The integration map

Build once. Route the answer.

Compass does not create a second graph for each tool. It publishes one validated snapshot, then gives each workflow the view it can use.

Shared snapshot

One validated graph, four useful hand-offs.

Compass / visual contract
Compass integration mapA local graph JSON snapshot routes the same identity, evidence, and limits to the editor, assistants, automation, and portable exports.inspectaskautomateshareVS Codesource + graph togetherMCP + skillsfocused context inCLI + CIrepeatable checksExportsHTML · JSON · SVGLOCAL SOURCE OF TRUTHgraph.jsonidentity · evidence · limitssame graph model · different place to use it

Choose a surface

Four ways to pick up the same answer.

Start with the hand-off that matches the decision in front of you. The contract stays stable when the destination changes.

Editor

VS Code

Inspect a symbol, trace its neighborhood, and jump from an edge to the exact source anchor without leaving the workspace.

For source-level explorationRead the VS Code guide
Assistant

MCP + native skills

Give coding tools a focused graph answer through a local process boundary instead of pasting the whole repository into context.

For focused machine contextSet up assistant access
Automation

CLI + CI

Build a snapshot, run a bounded CompassQL query, and publish explicit JSON or JSONL output in a script or pull request.

For repeatable structural checksRead the CI cookbook
Portable output

HTML, JSON, SVG + GraphML

Carry one validated snapshot into an interactive viewer, a static diagram, a machine-readable archive, or team notes.

For sharing and downstream toolsBrowse output formats

The stable contract

Different surfaces. Same evidence.

Identity, direction, source anchors, provenance, and explicit limits remain intact as the graph moves through the workflow.

local

source and graph stay on the machine

evidence

source anchors and provenance travel with edges

bounded

limits stay explicit in every query and export

deterministic

stable ordering keeps automation reviewable

Ready to give the codebase a bearing?

Install Compass locally, build one graph, and choose the surface that fits the next question.

Read the docs