brekenandbreken-ai b41445d092 🐛 Keep background plugins registered when another plugin opens (#11929) ...

Loading a plugin closed every non-background plugin and then emptied the
runtime registry, dropping background plugins (allowBackground, such as
the MCP plugin) that were left running. The registry is what routes a
plugin iframe's postMessage traffic to its plugin and what ɵunloadPlugin
searches, so after the user opened any other plugin the MCP plugin never
received task requests from its UI (MCP tool calls timed out) and could
no longer be unloaded.

Keep background plugins in the registry and drop only the plugins that
were closed.

AI-assisted-by: claude-opus-5.5

Signed-off-by: breken-ai <312387581+breken-ai@users.noreply.github.com>
Co-authored-by: breken-ai <312387581+breken-ai@users.noreply.github.com>

2026-10-05 20:17:04 +02:00

..

lib

🐛 Keep background plugins registered when another plugin opens (#11929)

2026-10-05 20:17:04 +02:00

index.ts

🐛 Handle plugin errors gracefully without crashing the UI (#8810)

2026-04-01 11:37:27 +02:00