What it does
C/C++ crash, hang and dump debugging for Claude Code, Codex and Qwen via GDB, LLDB and MCP
- Connects Runs on your computer
- Account or key No key needed
- Category Developer tools
Use together with
Skills that teach the AI this kind of work; they work alongside this one
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 20/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 32/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen. Follow https://mcp.popnx.com/i/spk-c-qwen-dap-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Let AI install it
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "qwen-dap": { "command": "npx", "args": [ "-y", "@slp-dev1/qwen-dap-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
node -vInstall once; it works for everything that needs Node.js
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Paste these settings and save the file
{ "mcpServers": { "qwen-dap": { "command": "npx", "args": [ "-y", "@slp-dev1/qwen-dap-mcp" ] } } }Quit Claude and open it again
Try it
Use Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen and tell me what you can do for me, then show me one thing✓ If Claude says it is using Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen or shows a Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen yet
Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen
- Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
- Install Node.js on your computer first (one time)
- Install Node.js on your computer first (one time)
- Install Node.js on your computer first (one time)
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Let AI install it
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user qwen-dap -- npx -y @slp-dev1/qwen-dap-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
node -vInstall once; it works for everything that needs Node.js
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --scope user qwen-dap -- npx -y @slp-dev1/qwen-dap-mcpType /mcp in Claude Code
You should see Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen listed as connected
Try it
Use Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen or shows a Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Let AI install it
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "qwen-dap": { "command": "npx", "args": [ "-y", "@slp-dev1/qwen-dap-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
node -vInstall once; it works for everything that needs Node.js
Open the AI chat in Cursor in Agent mode
Try it
Use Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen or shows a Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Let AI install it
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "qwen-dap": { "type": "stdio", "command": "npx", "args": [ "-y", "@slp-dev1/qwen-dap-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
node -vInstall once; it works for everything that needs Node.js
Open the AI chat in VS Code in Agent mode
Try it
Use Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen or shows a Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
For developers: Terminal commands and JSON settings
Installed on your computer
Claude Code
claude mcp add --scope user qwen-dap -- npx -y @slp-dev1/qwen-dap-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"qwen-dap": {
"command": "npx",
"args": [
"-y",
"@slp-dev1/qwen-dap-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"qwen-dap": {
"command": "npx",
"args": [
"-y",
"@slp-dev1/qwen-dap-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"qwen-dap": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@slp-dev1/qwen-dap-mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account spk-c, which owns the repo
- ✓ Pass
Still maintained
Code last changed 11 days ago
- ✓ Pass
Has a licence
Uses Apache-2.0
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Published vulnerabilities (OSV.dev)
No entries on OSV.dev for @slp-dev1/qwen-dap-mcp@0.19.4
Checks only this package version, not every dependency · checked Nov 15, 2026
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/spk-c-qwen-dap-mcp)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 69% of the other 6116 servers in this category
- Published to the registry more recently than 64% of the other 6116 servers in this category
- Basic checks equal to or better than 99% of the other 6116 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed 11 days ago, and the latest version (0.19.4) reached the registry 16 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP
Cloudflare MCP servers
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | Apache-2.0 | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Qwen DAP MCP — Native Debugger MCP for Claude Code, Codex, Qwen and AI Coding Agents
Debug native C/C++ crashes, hangs, deadlocks, Windows minidumps and core dumps with Claude Code, OpenAI Codex CLI, Qwen Code, Gemini CLI and other local MCP-compatible coding agents. Connect a real GDB, LLDB or CodeLLDB debugger through the Debug Adapter Protocol (DAP) and Model Context Protocol (MCP).
qwen-dap-mcp is a local Debug Adapter Protocol (DAP) → Model Context Protocol (MCP) bridge for native crash debugging, hang/deadlock triage, crash dumps, differential runtime analysis, remote targets, and bounded fix/verify workflows.
Originally designed for Qwen Code, but usable from other local stdio MCP clients including Claude Code and Codex CLI. The AI model may run in the cloud; the debugger bridge and target binary still run where the MCP process is started.
[Quick start](#quick-start) · [Capabilities](#what-it-does) · [Debugger support](#debugger-support) · [Safety](#safety-by-design) · [Docs](https://github.com/spk-c/Qwen-dap-mcp/blob/main/docs/README.md) · [Contributing](https://github.com/spk-c/Qwen-dap-mcp/blob/main/CONTRIBUTING.md)
Maintained Apache-2.0 fork of the original project by SLP-DEV1. The maintained source is spk-c/Qwen-dap-mcp; npm distributes
@slp-dev1/qwen-dap-mcp. GitHub'smainmay be ahead of the latest published npm version. See fork notes and TypeScript migration status.
See it in action: C++ crash → evidence → verification
*Illustrated architecture/workflow, not a captured AI session or fabricated debugger transcript.* Reproduce an actual intentional crash in the project's own C++ fixture, collect a GDB backtrace, apply an illustrative change only in a temporary copy, and rerun the same command:
bash scripts/demo-native-crash.sh
Requires Linux, g++ and gdb. CI also executes the demo with a real debugger. [View step-by-step verified demo and Claude/Codex MCP setup](https://github.com/spk-c/Qwen-dap-mcp/blob/main/docs/demo-native-crash.md).
Why this exists
Coding agents can read source and propose patches, but native failures often cannot be diagnosed reliably from source alone. The useful evidence lives at runtime: thread stacks, registers, locals, disassembly, exception state, modules, memory, wait states, symbols, and crash dumps.
qwen-dap-mcp makes that evidence available through MCP and adds agent-oriented workflows on top of raw debugger primitives:
- Evidence first — inspect the actual failing process instead of guessing from source.
- High-level workflows — crash, hang, differential, causal tracing, progress probing, runtime-report, dump, and verification tools are designed for agents rather than humans driving a debugger console.
- Bounded automation — autonomous fix/verify state is explicit, serializable, iteration-limited, and re-checks the original reproduction.
- Small default surface — 18 core agent tools stay visible by default; forensic workflows and raw DAP controls are separate opt-in tiers.
- Local by default — the MCP server communicates over stdio and debugger adapters run locally unless you explicitly configure a validated remote target.
Quick start
Qwen Code
Install the current published npm version:
qwen extensions install @slp-dev1/qwen-dap-mcp
Or install the newest code directly from the maintained GitHub repository (this can be ahead of npm):
qwen extensions install spk-c/Qwen-dap-mcp
In Qwen Code, run /mcp and /skills to check that the qwen-dap-mcp server and the native-runtime-debug skill were discovered.
Prerequisites: Node.js 20+, and a supported native DAP debugger installed separately (CodeLLDB, LLVM lldb-dap, or GNU GDB DAP). This package is a bridge, not a bundled debugger. See platform setup.
Claude Code
Use a local Claude Code CLI with Node.js 20+ and an installed native DAP debugger:
claude mcp add --transport stdio --scope user qwen-dap-mcp -- npx -y @slp-dev1/qwen-dap-mcp
claude mcp list
See Claude Code native debugging guide for a setup check, test prompt, Windows notes and safety boundaries.
OpenAI Codex CLI
codex mcp add qwen-dap-mcp -- npx -y @slp-dev1/qwen-dap-mcp
codex mcp list
See Codex CLI + IDE debugging guide and versioned Codex TOML configuration.
Gemini CLI, Cursor, VS Code Copilot and other clients
Use a local stdio MCP entry pointing to npx -y @slp-dev1/qwen-dap-mcp. These clients have different configuration schemas: Gemini CLI and Cursor use mcpServers, while VS Code's .vscode/mcp.json uses servers. See multi-client setup and compatibility matrix and the tested configuration examples.
Cloud execution boundary: Claude Code or Codex CLI may call a cloud AI model while the CLI and debugger remain on your desktop. A browser-only Claude.ai/ChatGPT session or a remote Codex task cannot automatically access your PC's local stdio MCP server or Windows processes. Remote debugging requires separately authorized local execution or a protected connection; never expose a raw debugger port to the public internet.
Other stdio MCP clients
Run the published package with npx:
npx -y @slp-dev1/qwen-dap-mcp --help
npx -y @slp-dev1/qwen-dap-mcp --version
Configure a trusted local MCP client with:
{
"mcpServers": { "qwen-dap-mcp": { "command": "npx", "args": ["-y", "@slp-dev1/qwen-dap-mcp"] } } }
When started without --help or --version, the CLI operates as a local stdio MCP server. Client configuration syntax may vary.
Update an existing installation
Update the npm-backed Qwen extension using the extension manager in your installed Qwen Code version, or reinstall the package with the command above. For npx, restart the MCP client to use newly resolved versions. npm releases are immutable: README changes appear on npmjs.com only after publishing a new package version, not when GitHub's README changes.
MCP client compatibility
| Client | Local MCP setup | Verification |
|---|---|---|
| Qwen Code | Qwen extension | /mcp and /skills |
| Claude Code | Local stdio claude mcp add | claude mcp list and /mcp |
| OpenAI Codex CLI | Local stdio codex mcp add | codex mcp list and /mcp |
| Gemini CLI | settings.json mcpServers | gemini mcp list |
| Cursor | Desktop MCP settings | Connected tools in Cursor |
| GitHub Copilot in VS Code | .vscode/mcp.json servers | MCP tools in Agent mode |
| Browser-only / cloud task | Not direct local stdio | Requires independent secure execution path |
The project includes automatic protocol-level stdio initialize + tools/list smoke tests with Claude Code, Codex CLI and Gemini client identities. These prove the shared MCP server protocol and example configuration consistency, not full end-to-end verification inside proprietary client applications. Native debugger E2E checks run separately. Run npm run test:clients from a built checkout.
30-second example
You: Debug why app.exe crashes with --repro
Coding agent ↓ qwen-dap-mcp starts a DAP debugger ↓ captures the native failure + project-controlled frame ↓ correlates stack + registers + locals + disassembly ↓ backtracks runtime evidence toward the likely producer ↓ agent applies a minimal source fix ↓ builds and repeats the original reproduction ↓ verifies whether the original crash fingerprint is gone
The MCP server supplies debugger evidence and bounded workflow state. Source editing, builds, tests, and source-control operations stay with the coding agent's normal authorized tools.
What it does
| Problem | Agent-oriented capability |
|---|---|
| Native crash | Diagnose a stopped process, identify project frames, collect runtime evidence, and drive bounded fix/verify loops |
| Hang or deadlock | Observe, pause when needed, capture all-thread stacks, classify waits, and surface conservative deadlock candidates |
| Good run vs bad run | Compare stopped sessions semantically while suppressing raw ASLR/address noise |
| Suspicious value | Trace real writers with data breakpoints/watchpoints and bounded temporal tracing |
| Runtime causality | Build a bounded suspicious-value consumer → writer/producer chain with debug_causal_trace |
| Suspected busy loop | Resume/pause sample a live target with debug_progress_probe to distinguish repeated state from observed execution movement |
| Record/replay target | Move backward with capability-gated debug_reverse_execution using DAP stepBack / reverseContinue |
| Crash fleet triage | Build debug_runtime_report fingerprints, cluster them with debug_cluster_crashes, and classify regression reproductions with debug_regression_oracle |
| Child/fork signal | Inspect fail-closed adapter startDebugging requests with debug_child_requests without auto-spawning child sessions |
| Crash dump | Inspect Windows minidumps and supported LLDB/GDB postmortem targets without launching the failed program |
| Remote native target | Attach through validated gdbserver / lldb-server gdbserver endpoints with loopback-first policy |
| Multiple targets | Keep isolated DAP sessions and route requests by sessionId |
| Agent safety | Keep the default surface high-level and optionally gate executable/mutating DAP actions with HOL Guard |
| Object lifetime / UAF | Correlate pointer writers, sanitizer evidence, reverse stepping, and allocation/free hints |
| Symbol mismatch | Compare adapter symbol state with bounded local binary/PDB identity evidence |
| Crash fleets | Batch postmortem analysis plus exact/semantic/family grouping |
| Offline handoff | Export structured evidence and SARIF without keeping the target alive |
Tool surfaces
The default agent toolset intentionally exposes 18 core tools so coding models spend less context and selection effort on rarely needed forensic workflows.
| Core tool | Purpose |
|---|---|
debug_this_crash | High-level native crash diagnosis and bounded autonomous verification |
debug_this_hang | High-level hang/deadlock triage |
debug_compare_runs | Semantic comparison of baseline and failing stopped sessions |
debug_trace_value | Bounded temporal tracing of a suspicious value |
debug_causal_trace |