Hello, I’m testing the MCP for Claud using the built in terminal. when i tell it to shut down the engine to compile the code, it also inevitably closes itself, killing all processes and whipping it’s memory as well. I assume you expect us to use live coding instead ? Sorry if this is a dumb question and I missed a step because i assume there is no way something so critical slipped though the net.
looks like thats not the MCP connection dying but the terminal. Running the agent inside the editor’s built-in terminal makes it a child of the editor process, so closing the editor kills the agent and its session with it.
Try to run the agent from an external terminal instead. The MCP connection survives an editor restart: close the editor, compile, reopen, and the agent keeps its full conversation memory and the tools come back as soon as the editor finishes loading. At least I do this cycle daily (editor closed for C++ compile, reopened, same agent session continues).
The one thing that does not survive is restarting the agent itself, that drops the MCP session, but not the editor restart. Hope it does make sense