GoLand Remote SSH Development and Delve Debugger: Session Continuity Across Connection Interruptions

When using GoLand's remote development over SSH, the local JetBrains client relies on a remote Go toolchain and Delve debugger running on the target host. If the underlying SSH connection drops—due to a network interruption or laptop sleep—the state of an active debug session becomes uncertain. The IDE may attempt to re-establish the tunnel, but Delve session persistence after reconnection is not documented as guaranteed, and breakpoints may require reattachment.

This uncertainty is amplified when the local and remote Go toolchain versions differ, since symbol resolution and stack traces can mismatch. The integration boundary between the local UI and the remote Delve instance is the critical unknown: does the client transparently resume the existing debug session, or does it treat the reconnection as a new attachment point?

Does GoLand automatically resume an active Delve session after an SSH reconnection, or does it require manually restarting the debug configuration? Are breakpoints and watch expressions preserved across such a reconnection? How does a mismatch between local and remote Go toolchain versions affect Delve's ability to reattach after the connection is restored?