Skip to main content

Dotscope: The Physics Engine for AI Coding Agents

If you've used AI coding agents (Claude, Cursor, Windsurf), you've probably watched them blindly hallucinate an import or break a downstream service because they don't understand the blast radius of their changes. Standard search is lexically blind.

We built Dotscope to fix this. It’s a bare-metal structural compiler written in Rust that maps the explicit dependencies and temporal coupling (Git history) of your codebase, and force-feeds that "architectural gravity" into the agent's context window. The agent just stops breaking things.

Supported natively via the Model Context Protocol (MCP) on Cursor, Windsurf, and Claude Desktop, Dotscope operates entirely locally, evaluates bounds near-instantly, and requires zero manual UI.


Installation (Now Zero-Dependency Setup)

We recently overhauled our distribution pipeline. pip install dotscope automatically pulls pre-compiled, native PyO3 Rust wheels globally for Apple Silicon, Intel macOS, Linux, and Windows. You do not need to install a local rustc compiler. Day One is an instant binary installation.

# 1. Install the core toolkit
pip install dotscope[mcp]

# 2. Bind your repository and trigger the bare-metal physics engine
dotscope init

# 3. Verify the MCP boot contract
dotscope doctor mcp --check --json

dotscope init now enforces a repository boot contract for MCP startup: a working managed runtime, a passing stdio self-test, current repo-local MCP configs, and durable diagnostics in .dotscope/mcp_install.json and .dotscope/mcp_last_failure.json.


Architectural Rigor: The FFI Topology Graph

Dotscope isn't a wrapper; it is an optimized topological execution plane engineered to map planetary-scale structures. Standard agents rely on simple string searching which leads to broken logic in large codebases. Dotscope natively hooks into petgraph, calculates the precise in-degree topological gravity of files, and pushes strict limits across the Python FFI via zero-copy vectors.

The Benchmark:

  • Execution Time: ~32 seconds for an entire 100,000 file ingestion.
  • Memory Ceiling: Bounded strictly to 208MB RAM.
  • Concurrency: Fully isolates multi-threaded file writes natively using a Token Bucket architecture to debounce IDE "save-spam," deploying atomic locks so memory never tears natively across agent requests.

The Feedback Loop

You do not need to teach your AI a new paradigm. The AI simply searches the codebase exactly as it normally does.

Under the hood, Dotscope intercepts the query and dynamically calculates physical constraints. If an agent touches a file with a gravity_score > 50 (massive downstream blast-radius), Dotscope silently injects a [DOTSCOPE_GRAVITY_WARNING] constraint directly into the JSON-RPC stream, forcing the LLM to structurally verify impact before ever returning a line of logic to you.

The AI stops acting like a junior parsing text and starts acting like a senior respecting architecture.


Scaling to the Swarm (Coming Soon)

Dotscope Pro: The Genesis Matrix

Open-source Dotscope calculates the physical layout of your local codebase in realtime. Dotscope Pro is the global intelligence vector. By connecting to the Pro WebSocket, your agents don't have to compile graphs from scratch; they instantly stream pre-compiled structural fingerprints from over 10,000 top-tier open-source architectural hubs. Your agent doesn't just know how you construct code, it mathematically recognizes how the planet constructs it natively across boundaries.

Dotswarm: Fleet Telemetry & Swarm Locks

What happens when you deploy 50 autonomous agents against a single enterprise monorepo infrastructure? They clobber each other's execution states. Dotswarm lifts our zero-latency local MVCC synchronization primitives directly into a distributed backend. It formally enforces Swarm Locks across distributed memory pools, guaranteeing massive AI fleets can orchestrate cross-repository execution simultaneously without triggering catastrophic merge collisions.

Metadata

Release files for dotscope 1.7.11

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dotscope 1.7.11
File Size Uploaded Provenance
dotscope-1.7.11.tar.gz 373.2 kB With provenance Details

Built distributions (wheels)

Table of built distributions (wheels) for dotscope 1.7.11
File
dotscope-1.7.11-cp310-abi3-win_amd64.whl CPython 3.10 abi3 Windows x86-64 Details
dotscope-1.7.11-cp310-abi3-manylinux_2_34_x86_64.whl CPython 3.10 abi3 Linux glibc 2.34+ x86-64 Details
dotscope-1.7.11-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.10 abi3 Linux glibc 2.17+ ARM64 Details
dotscope-1.7.11-cp310-abi3-macosx_11_0_arm64.whl CPython 3.10 abi3 macOS 11.0+ ARM64 Details
dotscope-1.7.11-cp310-abi3-macosx_10_12_x86_64.whl CPython 3.10 abi3 macOS 10.12+ x86-64 Details

Total release size: 13.6 MB

Release files / dotscope-1.7.11.tar.gz

Download URL dotscope-1.7.11.tar.gz
Size 373.2 kB
Tags Source
SHA-256 checksum
How to use checksums
acaaa0c48ac8e201f61cb223b206a982af1b500188671c0569fe3216044f85f9
BLAKE2b-256 checksum
How to use checksums
eb2002f1dac85abe6a29aed906eb7304cdb60fb257f1e7ef96bd900b06c1f9c9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 17, 2026.

Transparency log

Release files / dotscope-1.7.11-cp310-abi3-win_amd64.whl

Download URL dotscope-1.7.11-cp310-abi3-win_amd64.whl
Size 2.9 MB
Tags CPython 3.10 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
a2b42e4fe600e7bc9a3362c0662bcaf696c4747b92ecfefc098d8607ca0d4e2f
BLAKE2b-256 checksum
How to use checksums
417443d31041b6a4c2645b3b80cb9db0702d9023b1fb331a35dd956b7a3e6d38
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 17, 2026.

Transparency log

Release files / dotscope-1.7.11-cp310-abi3-manylinux_2_34_x86_64.whl

Download URL dotscope-1.7.11-cp310-abi3-manylinux_2_34_x86_64.whl
Size 2.7 MB
Tags CPython 3.10 Linux glibc 2.34+ x86-64 abi3
SHA-256 checksum
How to use checksums
105864e49e2e169333dcd3cd5f7abef358c0f17a8b86beabfee69f37c4cf6b86
BLAKE2b-256 checksum
How to use checksums
975521f62dcde759cd0b6d4eaa8e7bda4953cb29f98af479ab33e2b216e2a1b5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 17, 2026.

Transparency log

Release files / dotscope-1.7.11-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL dotscope-1.7.11-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 2.7 MB
Tags CPython 3.10 Linux glibc 2.17+ ARM64 abi3
SHA-256 checksum
How to use checksums
e8d90d2caccd45685807cc370118a1302e18fcd01aef9902ae4ef60ab6c66e51
BLAKE2b-256 checksum
How to use checksums
0b449888161fdd4358779ffa9b8976e6baacd4dda432b79d6fb248d3a90517ae
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 17, 2026.

Transparency log

Release files / dotscope-1.7.11-cp310-abi3-macosx_11_0_arm64.whl

Download URL dotscope-1.7.11-cp310-abi3-macosx_11_0_arm64.whl
Size 2.5 MB
Tags CPython 3.10 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
002d60df574b14a0ddd18b75fa48d2d452da478feb9c7bd2abd2ab4bc2ba5946
BLAKE2b-256 checksum
How to use checksums
3595339d462cf656ff1963594ca6f82c28676976ce8fd22a88d6d4e927b8dee9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 17, 2026.

Transparency log

Release files / dotscope-1.7.11-cp310-abi3-macosx_10_12_x86_64.whl

Download URL dotscope-1.7.11-cp310-abi3-macosx_10_12_x86_64.whl
Size 2.5 MB
Tags CPython 3.10 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
3ef458a975a3785959e112334f57fb551c18d90c19ab838ca0e1d9013219522b
BLAKE2b-256 checksum
How to use checksums
5e8d6175430572bf299e2d716e12bbe90c9ac6594f057c1812e3aba7ed1cb978
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 17, 2026.

Transparency log

Security for dotscope 1.7.11

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 6 files in this release have been uploaded with provenance metadata.

Select from 6 files

Attestation for dotscope-1.7.11.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 17, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page