Your agent doesn't understand
your codebase.

$ pip install dotscope
click to copy
Works with Cursor · Windsurf · Claude Code · Claude Desktop · any MCP client

This is what happens without structural context.

# Agent refactors auth.py — looks clean, tests pass
→ Refactoring authenticate() signature
✓ auth.py updated
✓ auth_test.py passes

# What the agent didn't know:
✗ 47 downstream files depend on old signature
✗ payments/processor.py — implicit contract broken
✗ middleware/session.py — silent failure in prod
✗ 3 services will crash on next deploy
with dotscope
# Agent queries the same refactor
→ Checking blast radius for authenticate()
├─ 47 direct dependents
├─ 3 critical paths (payments, session, api-gateway)
└─ implicit contract: processor.py expects dict return

→ Refactoring with backward-compatible wrapper
✓ auth.py updated — old signature preserved as alias
✓ All 47 dependents verified
✓ Zero breaking changes

Every context tool gives agents more text.
dotscope gives them structure.

Three commands. Nothing to configure.

Install

pip install dotscope

One package. No dependencies to manage. No build step.

Initialize

dotscope init

Compiles your repo into a structural topology. Launches the daemon. Generates agent config.

Done

Agent sees architecture

Blast radius, dependencies, implicit contracts — served automatically via MCP.

Built for real codebases.

Rust daemon running continuous AST ingestion. Double-buffered mmap matrices borrowed from HFT infrastructure. RCU epoch locks guarantee agents never read stale state. Save a file — the graph updates before your cursor moves.

100K
files ingested
~32s
cold compile
208MB
RAM ceiling at scale
0 CPU
cycles per read (mmap)

Open source. Enterprise when you're ready.

Community edition is MIT licensed and always free. When your team runs agent fleets across multiple repos, we're here.

View Source Talk to Us