We rebuilt the MCP runtime to reduce Studio disconnects and reconnection delays
Back to boardPreviously, when an AI Agent closed or the MCP Server encountered a problem, the Studio Plugin connection could also be affected, leaving you waiting for reconnection or retrying a request. This update reduces unnecessary disconnects and reconnection delays.
When an Agent session closes, the Studio Plugin connection remains active. If the process responsible for the connection exits unexpectedly, an active Agent recovers it automatically and waits for the Studio Plugin to reconnect before processing the next request. A mutating command whose completion cannot be confirmed is not replayed automatically, preventing the same change from being applied twice.
To support this, the MCP runtime is separated into one MCP Adapter per Agent and a shared WEPPY Bridge that owns the Studio connection. The Dashboard Connection page shows AI Agents → WEPPY Bridge → Studio Targets and the state of each connection. No settings change is required.