DebugAI: The VS Code Debugger That Reads Your Whole Codebase

Most AI tools only know what you paste. DebugAI pre-indexes your project — imports, call chains, file structure — so every debug session already has full context. Root cause and 3 ranked fixes in 8 seconds. No copy-paste. No browser. No explaining your architecture.

Works in VS Code, Cursor, and Windsurf.

Get started in 60 seconds

1. Install from Marketplace (you're here)
2. Sign up at debugai.io — free, takes 10 seconds
3. On your dashboard → click "Connect VS Code" — key configured automatically
   (No VS Code open? Use Ctrl+Shift+P → "DebugAI: Set API Key" → paste key)
4. Ctrl+Shift+P → "DebugAI: Index Entire Workspace" (one-time setup, ~2 min)
5. Hit any error → Ctrl+Shift+P → "DebugAI: Analyze Terminal Error" → done

Free tier: 10 debug sessions per day. No credit card. No signup friction.

What happens when you hit an error

1. DebugAI reads your terminal error automatically
2. Queries your locally-indexed codebase for relevant files
3. Traces the error across imports and call chains — not just the crash line
4. Returns 3 ranked fixes with confidence scores, root cause, and exact file:line
5. Opens diff preview before anything is applied — you approve every change

Median time from error to fix: 8 seconds.

Why codebase indexing changes everything

Standard AI debugging: error → paste → explain your stack → get generic answer → adapt manually → try again → repeat.

DebugAI: error → Ctrl+Shift+P → "DebugAI: Analyze Terminal Error" → fix.

When your AI already read your project, it traces a NoneType error back to the function that returned None three files upstream — without you explaining anything. That's what codebase context gives you.

How to run DebugAI

Use the Command Palette (Ctrl+Shift+P / Cmd+Shift+P) and type DebugAI to see all available commands. This is the primary way to invoke DebugAI — reliable in every context with no shortcut conflicts.

Power user shortcut (optional): Ctrl+Shift+D / Cmd+Shift+D fires DebugAI directly when your cursor is in the terminal or editor. Note: this shortcut only activates inside those specific VS Code panels.

Commands

Supported languages and frameworks

Python — FastAPI, Django, Flask, Celery, SQLAlchemy, Streamlit, PyTorch, TensorFlow, Pandas, NumPy

JavaScript / TypeScript — React, Next.js, Node.js, Express, Vue, Svelte, Vite, tRPC

Framework detection is automatic — no config files needed.

What leaves your machine

• During indexing: File content sent over HTTPS → chunked → embeddings generated via Voyage AI → stored in your project index on DebugAI servers. Full source files not stored as-is — only semantic chunks for retrieval.
• During debugging: Error message + relevant code snippet (~800 bytes) + recent git change metadata (file names only, never contents or diffs).
• When idle: Nothing. No background scanning. No telemetry on your code.

API keys stored in VS Code SecretStorage — never in plaintext settings files.

Privacy policy

Pricing

All features available on the free tier during beta.

Frequently Asked Questions

Does DebugAI read my entire codebase without asking? No. You run DebugAI: Index Entire Workspace manually. Only files in your workspace are indexed, and only on your explicit command.

What AI model powers DebugAI? Claude (Anthropic) for root cause analysis. GPT-4o-mini fallback activates automatically if Claude is unavailable — response format is identical either way.

Does it conflict with GitHub Copilot? No. DebugAI only runs when you explicitly invoke a command. No interference with Copilot, Copilot Chat, or any other extension.

Does it work offline? No. Indexing and analysis both require a connection to the DebugAI API.

How many free debug sessions do I get? 10 per day, free forever. Need more: request extended access from your dashboard.

Does it work in Cursor or Windsurf? Yes. DebugAI is a standard VS Code extension — works in any VS Code-compatible editor.

debugai.io · support@debugai.io · Privacy · Terms