1c-debug-hmr

You can debug 1C BSL code with session persistence by using a persistent MCP wrapper that maintains breakpoint state and recovers automatically, even when the debug server restarts or the target process changes.

Yes, you can set breakpoints, inspect stopped stack frames, evaluate variables, and step through BSL code execution in a live 1C infobase by attaching to the target process via RDBG HTTP connectivity.

Hot-module reload applies edits to the debug wrapper directly without requiring reconnection to the MCP session, allowing live iteration on the debug server itself while maintaining active breakpoint propagation.

Attaching a debugger to 1C:Enterprise with warm rphosts requires RDBG HTTP connectivity, guarded handling of pre-existing rphost processes, target attachment, and breakpoint propagation to ensure a stable debugging session.

You can use logpoints to investigate failing 1C business rules by injecting logging statements at specific BSL module lines without stopping execution, capturing variable state and expression evaluation output during runtime.

Thin-client launch workflows require guarded handling to avoid disrupting pre-existing sessions, and breakpoint propagation depends on stable RDBG HTTP connectivity, meaning network interruptions can pause debugging state recovery.