MCP dap_reconnect

Description

Recover a BrightScript (DAP) debug backend after its connection has dropped.

Speaks Roku's socket-based BrightScript debug protocol on TCP 8081 -- NOT the Microsoft Debug Adapter Protocol.

IMPORTANT: this is NOT a socket reconnect. Port 8081 only exists for a sideload launched with the remotedebug fields, so there is no running app to re-attach to. Recovery is EXIT_CHANNEL (the control socket is still alive) followed by a fresh remotedebug sideload and a brand-new handshake. After this call, the session is a NEW device-side session: thread IDs and breakpoint verification state are not preserved and must be re-established.

Returns an error if there is no active DAP connection to recover.

Device-verified: recovery works identically whether the connection dropped because of a software-initiated rebuild or because of an externally-triggered exit (e.g. pressing the Home button mid-session) -- both go through the exact same DapConnectionManager.recover()/onReconnected path. Every previously-set breakpoint is automatically reapplied afterward under its original (stable) id -- despite the fresh device-side breakpoint group starting empty -- and genuinely refires on the new connection, not merely re-listed. A breakpoint that fails to reapply is reported into debug_errors_read rather than silently dropped.

See also

• HTTP dapReconnect (POST /api/dap/reconnect)
• rk dap reconnect

Parameters

additionalProperties: false

This tool has no parameters.