Attach to a running app's renderers over its remote debugging port. Whoever reaches that port has
full control of the pages, so this is gated like eval (eab-mcp --allow-eval).
Disconnect, and close the app this session launched (killing it and its processes).
Replace the connection. Calls are serialized: overlapping connects (e.g. parallel tool calls reconnecting after a drop) run one after another, and only the last connection is kept open.
The current connection. If it dropped, reconnects to the same app with the same options (role, capabilities) — once, shared by concurrent callers.
Start an app with the bridge injected and work against it (Launch mode).
The app this session launched, while it runs.
Holds the one app connection an MCP session works against, and the app it launched, if any: a launched app belongs to the session and is closed with it (or replaced by the next launch).