ashgti wrote: Reading more about this in the VSCode docs and on the MCP website I think I understand the flow of logic a bit more.
I think this is definitely helpful for allowing an agent to help control a debug session. However, I'm still not sure how we should handle the MCP client and debugger instance association. The main limitation I see is being able to launch a debug session (either by starting a binary or attaching). I suppose that if you were to just use `lldb` in the command line and then start the server it could always use `process launch ...` to start a debug session. In the lldb-dap VSCode extension, we could use the VSCode APIs to make a different tool for launching a debug session with lldb-dap and dynamically register the MCP server once the debug session starts (https://code.visualstudio.com/api/extension-guides/mcp#register-an-mcp-server allows us to update the list of servers dynamically from our extension). https://github.com/llvm/llvm-project/pull/143628 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
