Browser Plugin Freezes and Fails to Render Image When Receiving Base64 Data from MCP

Describe the bug
The browser plugin fails to render images correctly when the MCP returns an image in base64 format. More critically, the large size of the base64 string causes the browser tab to lag severely or become completely unresponsive, significantly degrading the user experience.

To Reproduce
Steps to reproduce the behavior:

1. Launch the browser and activate the extension.
2. Send a prompt to the MCP that is expected to return an image (e.g., "draw a cat").
3. Wait for the MCP to process the request and return the result.
4. Observe that the plugin does not display the image. Simultaneously, the browser tab begins to lag, becomes difficult to scroll, and may freeze entirely.

Expected behavior
The web-based LLM should be able to correctly receive and display the image returned by the MCP.

Screenshots
(Not applicable, as the primary issue is performance-related, manifesting as UI lagging and unresponsiveness rather than a static visual defect.)

Desktop (please complete the following information):

• OS: Windows
• OS Version: 10
• Browser: Microsoft Edge
• Browser Version: 141.0.3537.57 (Official build) (64-bit)
• Node Version: v22.16.0
• Other Necessary Packages Version: Extension Version: 0.5.6

Additional context
The root cause appears to be the direct handling and rendering of a large base64 string within the plugin's UI.

Suggested solutions could include:
The base64 string should be displayed as an <img> tag, and it should be sent to the web client in the format of an image file to ensure efficient rendering without freezing the UI.