Getting Started

What You’ll Install

Pointbreak needs two pieces to work:

🔧 IDE Extension - Connects your IDE to the debugger
🤖 MCP Server - Lets your AI control the debugger

Good news: If you use GitHub Copilot or Cursor, the MCP server installs automatically! You only need to install the extension.

Choose your installation path:

Quick Setup

GitHub Copilot or Cursor:1 step - Just install the extension!

Full Setup

Claude Code, Codex, Windsurf, Goose:2 steps - Extension + CLI

Quick Setup: GitHub Copilot/Cursor

Install Extension

Open VS Code or Cursor
Go to Extensions (Cmd+Shift+X / Ctrl+Shift+X)
Search for “Pointbreak”
Click “Install”

That’s it! The MCP server auto-registers with GitHub Copilot and Cursor.

Install Debug Adapter

Install the debug adapter for your language:

Python
JavaScript/TypeScript
Rust
Go

Search for “Python” in Extensions and install the official Microsoft Python extension (includes debugpy).

Verify Installation

Open the Output panel (View → Output), select “Pointbreak” from dropdown.You should see: Pointbreak debug bridge started successfully

Check the status bar at the bottom of VS Code - a green Pointbreak indicator means you’re ready!

Try It Out

You’re ready to debug!Skip to Your First Debugging Session

Full Setup: Claude Code/Other AIs

Both pieces required! These AI assistants need manual MCP configuration, so you must install the extension AND the CLI.

Install Extension

Open VS Code (or compatible editor)
Go to Extensions (Cmd+Shift+X / Ctrl+Shift+X)
Search for “Pointbreak”
Click “Install”

Direct link: VS Code Marketplace

Install Debug Adapter

Install the debug adapter for your language:

Python
JavaScript/TypeScript
Rust
Go

Search for “Python” in Extensions and install the official Microsoft Python extension (includes debugpy).

Install MCP Server (CLI)

macOS / Linux:

curl -fsSL https://withpointbreak.com/install.sh | sh

Windows (PowerShell):

irm https://withpointbreak.com/install.ps1 | iex

Verify it worked:

pointbreak --version
# Should output: pointbreak X.X.X

The script installs to ~/.local/bin (Unix) or %LOCALAPPDATA%\Pointbreak\bin (Windows). Don’t use sudo!

Configure Your AI Assistant

Claude Code
Codex
Windsurf
Goose
Other

claude mcp add --transport stdio pointbreak -- pointbreak mcp serve

Verify with:

claude mcp list
# Should show: pointbreak

Detailed Claude Code Setup →

codex mcp add pointbreak -- pointbreak mcp serve

Verify with the /mcp command in Codex.

Configure Windsurf’s MCP settings to point to the binary:

macOS/Linux: ~/.local/bin/pointbreak
Windows: %LOCALAPPDATA%\Pointbreak\bin\pointbreak.exe

Detailed Windsurf Setup →

Add to your Goose MCP configuration:

{
  "mcpServers": {
    "pointbreak": {
      "command": "pointbreak",
      "args": ["mcp", "serve"]
    }
  }
}

Configure your MCP client to use:

macOS/Linux: ~/.local/bin/pointbreak
Windows: %LOCALAPPDATA%\Pointbreak\bin\pointbreak.exe

See all AI assistants →

Verify Everything Works

Check extension - Output panel should show: Pointbreak debug bridge started successfully
Check CLI - Run: pointbreak --version
Check AI config - List MCP servers (e.g., claude mcp list)

If something’s wrong, see Troubleshooting.

Your First Debugging Session

Let’s debug a simple program to verify everything works!

Create Example Code

Python
JavaScript
Rust
Go

Create test.py:

def calculate_average(numbers):
    total = sum(numbers)
    count = len(numbers)
    return total / count

result = calculate_average([1, 2, 3, 4, 5])
print(f"Average: {result}")

Create test.js:

function calculateAverage(numbers) {
  const total = numbers.reduce((sum, n) => sum + n, 0);
  const count = numbers.length;
  return total / count;
}

const result = calculateAverage([1, 2, 3, 4, 5]);
console.log(`Average: ${result}`);

Create test.rs:

fn calculate_average(numbers: &[i32]) -> f64 {
    let total: i32 = numbers.iter().sum();
    let count = numbers.len() as f64;
    total as f64 / count
}

fn main() {
    let result = calculate_average(&[1, 2, 3, 4, 5]);
    println!("Average: {}", result);
}

Create test.go:

package main

import "fmt"

func calculateAverage(numbers []int) float64 {
    total := 0
    for _, n := range numbers {
        total += n
    }
    return float64(total) / float64(len(numbers))
}

func main() {
    result := calculateAverage([]int{1, 2, 3, 4, 5})
    fmt.Printf("Average: %.2f\n", result)
}

Ask Your AI Assistant

Try this prompt:

"Set a breakpoint on line 3 and start debugging test.py.
Show me the value of 'numbers' when we hit the breakpoint."

(Adjust line number and filename for your language)

What Should Happen

Breakpoint appears - Red dot on line 3 in VS Code
Debug session starts - Debugger launches automatically
Execution pauses - Code stops at line 3
AI inspects variables - Shows you the value of numbers

Example AI Response

I've set a breakpoint at line 3 and started debugging.
The execution has paused at the breakpoint.

The value of 'numbers' is: [1, 2, 3, 4, 5]

Would you like me to step through the rest of the function?

Common First-Time Issues

”AI can’t find Pointbreak”

VS Code/Cursor users: Restart your editor Claude Code users:

Check CLI: pointbreak --version
Check MCP config: claude mcp list
See Claude Code troubleshooting

”Breakpoint not hit”

Ensure debug adapter is installed for your language
Try running debugger manually (F5) first to verify it works
Check that file is saved

”No debug adapter available”

Install the debug adapter for your language (see Step 2 above).

Tips for Effective AI Debugging

Be specific - “Set a breakpoint on line 42” > “debug this”
Set breakpoints first - Ask AI to set breakpoints before starting debugger
Ask for context - “Show me the stack trace” or “What are all the local variables?”
Step through interactively - “Step into this function” or “Step over the next line”
Use natural language - No need to memorize commands!

Example Prompts to Try

"Set a breakpoint where the error occurs and start debugging"

"Step through this loop and show me how the counter changes"

"What's the call stack when we hit this breakpoint?"

"Set a conditional breakpoint that only triggers when x > 10"

"Step into this function and inspect all local variables"

Next Steps

Now that you’re up and running:

Learn debugging patterns - See Usage Guide
Advanced features - See AI Assistants Guide
Troubleshooting - See Troubleshooting Guide
Join the community - GitHub Discussions

Ready to debug? Try asking your AI assistant to help you debug your code!

Guides

About

Legal

Getting Started

What You’ll Install

Quick Setup

Full Setup

Quick Setup: GitHub Copilot/Cursor

Full Setup: Claude Code/Other AIs

Your First Debugging Session

Create Example Code

Ask Your AI Assistant

What Should Happen

Example AI Response

Common First-Time Issues

”AI can’t find Pointbreak”

”Breakpoint not hit”

”No debug adapter available”

Tips for Effective AI Debugging

Example Prompts to Try

Next Steps

Getting Started

Guides

About

Legal

​What You’ll Install

Quick Setup

Full Setup

​Quick Setup: GitHub Copilot/Cursor

​Full Setup: Claude Code/Other AIs

​Your First Debugging Session

​Create Example Code

​Ask Your AI Assistant

​What Should Happen

​Example AI Response

​Common First-Time Issues

​”AI can’t find Pointbreak”

​”Breakpoint not hit”

​”No debug adapter available”

​Tips for Effective AI Debugging

​Example Prompts to Try

​Next Steps

What You’ll Install

Quick Setup: GitHub Copilot/Cursor

Full Setup: Claude Code/Other AIs

Your First Debugging Session

Create Example Code

Ask Your AI Assistant

What Should Happen

Example AI Response

Common First-Time Issues

”AI can’t find Pointbreak”

”Breakpoint not hit”

”No debug adapter available”

Tips for Effective AI Debugging

Example Prompts to Try

Next Steps