v1.0 is live — works with Cursor, Claude Code, Windsurf, Copilot, Cline & Antigravity. See pricing →

Pre-Edit Breaking-Change Gate

Know what breaks before your AI agent edits it.

Your agent changes one function. The linter passes. Ten minutes later, a React screen crashes and three workers throw TypeError. BlastTrace traces every proposed edit across Database → Backend → API → Frontend → Tests and stops the break before it's written.

$ pip install blasttrace
  • <1ms native C++ core
  • 5 stack layers linked
  • 0 bytes of code uploaded
agent-session · sample_backend.py IDLE
Speaks MCP with

The 4:47 PM incident

Every AI coding tool reads 3 files.
Your bug lives in the 4th.

  1. Agent renames users.balance → wallet_balance in schema.sql.

  2. Updates models.py. Tests it can see: green.

  3. PR merged. "Looks good to me."

  4. Checkout.tsx renders undefined. Revenue page down. Analytics endpoint 500s.

  5. Blocked at 4:31 with the exact 4-file chain and a sync patch.

How it works

Three steps. Zero cloud.

01

Index the whole stack

SQL & Prisma schemas, ORM models, Python & TypeScript functions, API routes, React consumers and test suites become one contract map inside the BlastTrace Native Core.

index_repository_topology("./")
02

Gate every proposed edit

Before writing, your agent asks the Pre-Edit Breaking-Change Gate. It diffs signatures, columns and payloads and returns PASS WARN or BLOCK.

verify_pre_edit_safety_gate(...)
03

Ship the synced patch

You get the hop-by-hop evidence chain, an ordered checklist of files to update, copy-paste patches, and the exact tests to run.

select_impacted_tests([...])

Blast Radius

See how far one edit travels.

Pick an edit. Each ring is a layer of your stack. Red means it breaks.

    Supported stacks · v1.0

    Deterministic. Not guessed.

    1 Database & Schema

    • SQL (.sql) — PostgreSQL, MySQL, SQLite
    • CREATE / ALTER TABLE, FKs
    • Prisma schema.prisma
    • Drizzle ORM
    • SQLAlchemy & Django ORM

    2 Backend & Functions

    • Python — def, async def, classes
    • Type hints, defaults, decorators
    • TypeScript & JavaScript
    • Arrow fns, interfaces, types
    • ES & CommonJS imports

    3 API Contracts

    • FastAPI, Flask, Django REST
    • Next.js App Router route.ts
    • Express, NestJS
    • OpenAPI / Swagger
    • response_model payloads

    4 Frontend Consumers

    • React, Next.js, Vue
    • fetch(), axios.*()
    • useSWR(), useQuery()
    • Response property access
    • Props & interfaces

    5 Tests

    • Pytest / Unittest
    • Jest / Vitest
    • Playwright / Cypress
    • Endpoint-level mapping
    • Case-level selection

    10 MCP tools + CLI

    Your agent calls them automatically.

    ToolWhat it answersTier
    index_repository_topologyWhat's in this repo across all 5 layers?Free
    analyze_symbol_reachabilityWho calls or imports this?Free
    verify_pre_edit_safety_gateIs this edit safe to write? PASS / WARN / BLOCKPro
    trace_fullstack_contract_chainHow does this column reach the UI?Pro
    analyze_db_schema_blast_radiusWhat breaks if I drop or rename this column?Pro
    analyze_api_contract_impactWhich frontends read this payload field?Pro
    analyze_python_module_impactDeep signature & call-chain impact in PythonPro
    analyze_typescript_frontend_impactProps, interfaces, hooks & API consumersPro
    select_impacted_testsWhich tests should I actually run?Pro
    detect_circular_code_dependenciesDid a refactor create an import loop? (Circular Dependency Interceptor)Pro
    blasttrace check <symbol> blasttrace diff blasttrace pre-commit blasttrace status

    Versus free code-graph MCPs

    They see files. We see contracts.

    Free single-language AST tools

    • File A imports File B
    • Required vs. optional parameters
    • SQL column → ORM → handler
    • API route → React fetch consumer
    • Circular import interception
    • Change-aware test selection
    • Multi-file sync patches

    BlastTrace

    • File A imports File B (free tier)
    • Signature diffing with PASS / WARN / BLOCK
    • SQL & Prisma → SQLAlchemy / Django
    • FastAPI / Express / Next.js → fetch / axios
    • Recursive Loop Analysis in native C++
    • Pytest / Vitest / Jest case selection
    • Ordered checklist + copy-paste patches

    Pricing

    One prevented outage pays for the year.

    Community

    Hobbyists, solo exploratory testing

    $0forever

    • Basic single-file AST inspection
    • Local CLI & single-seat MCP
    • Repository topology indexing
    • Community Discord support
    Install free

    Team / CI Gate

    Engineering & tech leads, startups (up to 5 devs)

    $99/ month

    • Everything in Pro
    • 5 machine seats ($20/seat for extras)
    • Git pre-commit hook enforcement across repos
    • GitHub Actions / GitLab CI PR gate
    • Priority issue handling
    Get Team — $99/mo

    1 · Add to your MCP config

    {
      "mcpServers": {
        "blasttrace": { "command": "blasttrace" }
      }
    }

    2 · Activate Pro on this machine

    $ blasttrace activate <YOUR_KEY>
    [+] BlastTrace Pro activated on this machine!
    $ blasttrace status
    Air-Gapped & Zero-Telemetry Architecture

    Your code never leaves your workstation. Period.

    Unlike cloud linters or remote code-indexers, BlastTrace runs 100% locally on your machine CPU. We engineered it specifically so developers at fintech, healthcare, and enterprise companies can use it without security audit friction.

    🔒 Zero Cloud Code Uploads

    Every SQL file, AST signature, and React component is evaluated in volatile local RAM by the BlastTrace Native Core. No repository files, AST nodes, or diffs are ever uploaded, transmitted, or logged to remote servers.

    🚫 No AI Training On Your Code

    We do not operate a cloud language model. Your proprietary code is never stored, indexed for search, or used to train, fine-tune, or benchmark any public or private AI models.

    ✈️ 100% Offline-First Resilience

    Coding on a flight, in a secure enclave, or during a network outage? Pro licenses include a 14-day cryptographically verified offline grace window bound to your hardware fingerprint.

    🛡️ Compliance & Enterprise Ready

    Because zero source code or personal customer data enters our infrastructure, using BlastTrace introduces zero data processing liability under GDPR, CCPA, or strict NDA policies.

    Questions

    Does my code leave my machine?

    No. Indexing and analysis run 100% locally in the compiled BlastTrace Native Core. Only Pro license activation contacts Paddle, using a one-way hardware fingerprint.

    Do I need an AI agent to use it?

    No. The standalone CLI (check, diff, pre-commit) works in any terminal, git hook, or CI pipeline.

    Which editors are supported?

    Any MCP-compatible client: Cursor, Claude Code, Claude Desktop, Windsurf, VS Code (Copilot Agent Mode, Cline, Roo Code, Continue), Google Antigravity, JetBrains IDEs and Zed.

    What if my stack isn't listed?

    v1.0 covers the matrix above deterministically. Unsupported files are skipped rather than guessed, so you never get hallucinated impact.

    Can I work offline?

    Yes. Pro includes a 14-day cryptographically signed offline grace window.

    Refunds?

    14-day money-back guarantee if BlastTrace doesn't work on your supported stack. Email support@blasttrace.dev.

    Stop shipping the 4th file bug.

    $ pip install blasttrace