Feature request: Isolated preview tabs per session

Problem

When running multiple Claude Code Desktop sessions on the same project, all sessions share a single preview pane. Navigating in one session (e.g. going to /pulse) immediately affects what the other sessions see, making the preview unusable in multi-session workflows.

Expected behavior

Each session should get its own isolated, dedicated preview webview. They can share the same underlying dev server — autoPort in launch.json already handles port assignment nicely. The issue is purely that the preview view itself is shared, so one session's navigation stomps on the others.

Why this matters

Multi-session is a core feature of Claude Code Desktop — working on different parts of an app in parallel is one of the biggest productivity gains. But the shared preview pane breaks this workflow entirely, forcing users to fall back to external browser tabs (e.g. Claude in Chrome) instead of the built-in preview.

Suggested solution

• Scope the preview webview instance to the calling session
• Each session owns its own isolated browser view
• The underlying dev server can be shared or separate — that's already configurable via autoPort: true

Environment

• Claude Code Desktop on Windows (latest version)
• Multiple concurrent sessions on the same project