debug_status

July 31, 2026 · View on GitHub

Report active debug sessions: applicationId (real or synthetic 'attach:' / 'launch:'), launch configuration name/type, mode (debug/run), whether the target is currently suspended, thread count, and the line of the top suspended frame. Also reports debugServerTargets: 1C debug-server sessions (server-side suspends, EDT-UI-started 'Debug As') addressable as 'ServerApplication.'. Optionally filter by applicationId.

Parameters

ParameterRequiredTypeDescription
applicationId—stringOptional application id filter

Guide

Shows the active debug launches and whether each is currently suspended - the "where am I?" tool for a debug session. Use it to find the applicationId to drive the other debug tools, and to check if execution is paused at a breakpoint.

When to use

  • You don't know the applicationId of a running debug session and need it for wait_for_break / resume.
  • To check whether a launch is suspended (and at which line) before stepping or reading variables.
  • To confirm a debug_launch (or an attach) is actually running.

Parameter details

  • applicationId - optional filter to a single launch; omit to list all active EDT debug launches.

What you get

JSON: launches - each with applicationId (a real id, or a synthetic attach:<configName> for attach launches), launchConfiguration name and configurationType, mode/debug, project, whether it is suspended, the threadCount, and suspendedAt (the top frame name and line) when paused. Plus a count, a registry snapshot and recentLaunchFailures — failures of fire-and-forget launches from the last hour ({launchConfiguration, applicationId, message, ageSeconds}), filtered by applicationId like the launches. This is where a debug_launch that already answered status: "launching" reports what went wrong afterwards, including an external-changes conflict its policy declined to resolve.

Notes & gotchas

  • Only EDT/1C debug launches are listed; unrelated Java/Ant launches are filtered out.
  • For attach configurations that don't carry an application id, use the reported attach:<configName> value as the applicationId for other tools.
  • This only reports state - it doesn't pause or resume anything. To block until a suspend happens use wait_for_break; to continue use resume.

Generated from the live MCP server (get_tool_guide) by docs/generate_tool_docs.py. Do not edit this file. Edit the tool's description/schema in its Java source and its guide body in mcp/bundles/com.ditrix.edt.mcp.server/guides/<tool>.md.