Fast text search across the workspace files. Uses ripgrep when available, falls back to a recursive file walk. Returns matching file paths, line numbers, and line content.

Auto-detects the workspace's technology stack, package manager, test runner, log paths, and entry points. Call this first to establish context before debugging.

Executes the workspace's test suite. Auto-detects the appropriate test runner. The confirm flag MUST be set to true to actually execute — this is a safety measure.

Retrieves recent git commits for the workspace. Useful for correlating code changes with failures. Returns commit hash, author, date, and message.

Establishes a TCP connection to a running Debug Adapter Protocol (DAP) server. This must be called before inspect_runtime_state or evaluate_expression. The debug adapter must already be listening on the specified host and port (e.g., a Node.js app started with --inspect-brk, or a VS Code debug adapter in server mode).

Retrieves the live debugging snapshot from a connected DAP session: threads, call stack, scopes, and local variables with their current values. Requires an active DAP connection (call connect_dap first). Most useful when the debuggee is stopped at a breakpoint.

Evaluates an expression in the context of the debuggee's current state. Requires an active DAP connection and typically works best when the debuggee is stopped. The context parameter restricts what kind of evaluation is performed: "hover" (default, safe, no side effects) or "watch".

Controls execution flow of the debuggee. Use this to resume, step over, step into, or step out. Requires an established debugging connection which is currently paused. This command will mutate the state of the debuggee and wait up to 3 seconds for it to pause again.

Cleanly disconnects from the current DAP session. The debuggee continues running — this does NOT terminate it. Idempotent: safe to call even if not connected.