In-app preview pane resets to blank 'New tab' and stops responding to clicks/URL input

Summary

During a long-running Claude Code session, the in-app Browser preview pane periodically resets to a blank "New tab" screen showing the configured server list (from .claude/launch.json), and becomes unresponsive to user interaction: clicking a running server's row does nothing, and typing a URL directly into the pane's own address bar and pressing Enter also does nothing.

Steps to reproduce

1. Start a local dev server through the preview pane (agent calls a Browser MCP tool to start a server from .claude/launch.json) and navigate to a page within the app.
2. Continue a long Claude Code session with many tool calls driving that pane (hours, dozens of navigation/eval calls via MCP).
3. At some point the pane's visible tab resets on its own to a blank "New tab" screen listing the configured servers — one shown as already running (red stop icon).
4. Click directly on the running server's row to open it in this tab — nothing happens, the picker screen stays as-is.
5. Type a URL (e.g. http://localhost:3005/...) into the pane's own address bar and press Enter — nothing happens either.

Expected behavior

Clicking a running server's row, or typing and submitting a URL in the pane's address bar, should navigate that tab to the target URL.

Actual behavior

The tab remains stuck on the blank "New tab" / server-picker screen with no visible response to either interaction.

Additional context

• The underlying dev server process itself stayed healthy and reachable the whole time — confirmed from the agent side, since its own MCP tool calls (navigate/eval) continued to work correctly against the same running server/session even while the picker screen was stuck for the user.
• The issue appears specific to the pane's own UI chrome (the "New tab" / server-picker screen), not the dev server or the page content itself.
• This happened more than once in the same session, always following a reset to the blank "New tab" state — never observed while a tab was already showing loaded app content.
• No reliable end-user-side workaround was found (reload attempts, retyping the URL, and re-clicking the server row all had no effect); the agent could still drive the already-attached tab's content directly via its own tool calls, just not select/populate a fresh "New tab".