claude-code - 💡(How to fix) Fix Feature request: Isolated preview tabs per session [1 comments, 2 participants]

TL;DR

The most likely fix is to scope the preview webview instance to the calling session, ensuring each session has its own isolated browser view.

Guidance

• Investigate how the preview webview is currently instantiated and shared across sessions to identify the root cause of the sharing issue.
• Consider implementing a session-specific identifier or token to isolate the preview webview instance for each session.
• Review the launch.json configuration, particularly the autoPort setting, to understand how it handles port assignment and if it can be leveraged to support isolated preview views.
• Explore the possibility of using a separate browser view or iframe for each session, while still sharing the underlying dev server.

Example

No specific code snippet can be provided without more context, but the solution might involve creating a new browser view instance for each session, similar to:

// Pseudo-code example, actual implementation may vary
const sessionWebView = createBrowserView(sessionId);

Notes

The exact implementation details will depend on the underlying architecture of Claude Code Desktop and how the preview webview is currently integrated. This solution assumes that the dev server can be shared across sessions without issues.

Recommendation

Apply a workaround by scoping the preview webview instance to the calling session, as this directly addresses the reported issue and aligns with the suggested solution.