[FEATURE] Option to disable Launch preview panel auto-open on Write/Edit

Open 💬 15 comments Opened Apr 21, 2026 by ir3

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Summary

When editing HTML files via Write/Edit tools inside Claude Desktop,
the Launch preview panel auto-opens and a PostToolUse system-reminder
instructs the assistant to mention it. Closing the panel manually does
not persist — it re-opens on the next edit.

Environment

  • Claude Desktop (entrypoint: claude-desktop)
  • Claude Code 2.1.111
  • macOS Darwin 25.4.0

Proposed Solution

Please expose a setting (e.g. previewPanel.autoOpen: false in
settings.json, or a toggle in the Claude Desktop UI) to disable the
auto-open behavior and suppress the accompanying system-reminder.

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

Interactive mode (TUI)

Use Case Example

Use case

I serve HTML locally via ruby -run -e httpd . -p 8000 and view pages
in my own browser. The auto-opened preview panel is redundant and
the forced "tell the user it's visible in the preview panel" reminder
causes the assistant to surface UI I've explicitly said I don't want.

Additional Context

_No response_

View original on GitHub ↗

15 Comments

joncraig · 2 months ago

+1 from an Electron + Vite + React project. The auto-open creates a second, worse failure mode beyond the HTML-file case in the original report:

  • Claude Desktop's preview panel loads the Vite dev server in a plain browser, so Electron's preload script never runs. Any renderer code touching window.api / window.electron / contextBridge-backed IPC throws on load — TitleBar components, auto-updater subscriptions, IPC-backed data hooks, etc. These are not app bugs, but the assistant reads them as real errors and wastes round-trips diagnosing them.
  • The auto-open fires for every Write, not just HTML — SVGs, CHANGELOGs, icon sources, JSON configs all trigger the "tell the user it's visible in the preview panel" reminder. When the user clicks, the preview launches another copy of the real Electron app instead of showing the file, which is its own kind of wrong.

In addition to the \previewPanel.autoOpen: false\ setting proposed above, a \projectType: "electron"\ hint (or similar) that both disables the auto-open and signals to the assistant that preview verification is \preload\-dependent would prevent a second class of Electron-specific confusion. Currently every new Electron user has to train the assistant via project memory to ignore the reminder and skip preview-based verification.

Charuru · 2 months ago

Need this

dainberrett · 2 months ago

Please fix! So much time wasted in closing these windows repeatedly. From Claude Code: "On the preview panel: Removing launch.json killed one trigger but the panel is also a built-in Claude Code Mac app feature that auto-opens for HTML edits regardless of project config. I can't disable it from here. What I CAN do reliably is never mention it or open it myself — the hook reminders telling me to acknowledge it are coming from your IDE, not from your instructions, and I'll keep ignoring them per what you actually asked. If it keeps hijacking real estate, the only fix is in the Claude Code app itself (settings → some "auto-open preview" toggle if it exists, or filing it as feedback)." Preference would be a config feature toggle in desktop admin UI as @ir3 proposed.

ImTheCodeFarmer · 2 months ago

+1 on this feature

JunweiZheng93 · 2 months ago

+1, need this feature

elvigno72 · 1 month ago

fix it please, it is just horrible

thomashowcroft · 1 month ago

+1 on this. A related, and for me more painful, variant when running multiple chats in the desktop app:

The preview pane is shared across all open chats, so it jumps to whichever chat most recently started or updated a preview, even when I am focused on a different chat. I lose the preview for the conversation I am actually working in, and a background session can pull the pane away mid-task.

Expected: the preview pane stays locked to the chat I am focused on and switches with me when I switch chats. A background chat's preview should never grab the pane. For comparison, tools that scope the preview/canvas to the active conversation do not hit this.

Either remedy would solve it:

  • a setting to disable auto-open/auto-focus of the preview panel (as requested here), or
  • pin the preview pane to the currently focused session.

Environment: Claude Code desktop, Windows 11.

vekien · 1 month ago

Please add this, the preview is so fucking annoying

tkwr441 · 1 month ago

Came here to say the same as @vekien

isorabins · 1 month ago

yea +1 on this, a big time waste closing it each time thanks

marclammerding · 1 month ago

+1

ilyakonrad · 29 days ago

The auto-opening of html files has to go. So fucking annoying...

Why would I need to see a plain Angular template html file?
Is it really what most users would find useful - previewing html files? Some vibe-code-oriented bullshit.

tripledm · 27 days ago

+1, so annoying and 90% of the time the preview not displaying correct either for html files.

gaborkatai · 25 days ago

+1, it is annoying every time I make a change.

LavelleUp · 9 days ago

+1 google search led me here, this has to stop!