[BUG] Artifacts viewer window: View > Zoom In/Out and Ctrl+/Ctrl- zoom the main Claude Code window instead of the artifact
Preflight Checklist
- [x] I have searched existing issues. The closest is #62449 (detached/pop-out conversation windows), which I believe shares a root cause but does not cover this window. See "Relationship to #62449" below.
- [x] This is a single bug report
- [x] I am using the latest version of Claude Code (2.1.251, desktop app 1.37937.0.0)
What's Wrong?
The Artifacts viewer opens as its own top-level window, with its own menu bar. Its View menu offers Zoom In (Ctrl++) and Zoom Out (Ctrl+-).
Neither one changes the size of the artifact being viewed. They change the zoom level of the main Claude Code Desktop window instead.
The Artifacts window is left at whatever zoom it started at, with no way to make the artifact larger or smaller. The main window silently rescales behind it, which on a second monitor or a maximized Artifacts window is not visible at all.
Both routes are affected and behave identically:
- Clicking
View > Zoom In/View > Zoom Outin the Artifacts window's own menu bar - Pressing Ctrl+
+/ Ctrl+-while the Artifacts window is focused
This is a menu item that the Artifacts window itself advertises, so there is no ambiguity about which window the user meant to act on.
What Should Happen?
| Observed | Expected |
|---|---|
| View > Zoom In in the Artifacts window zooms the main window | It zooms the artifact content in the Artifacts window |
| View > Zoom Out in the Artifacts window zooms the main window | It zooms the artifact content out in the Artifacts window |
| Ctrl++ / Ctrl+- with the Artifacts window focused hits the main window | The shortcut acts on the focused window |
| No way to resize artifact content | The artifact scales, so dense diagrams and wide tables can be read |
A zoom control in a window's own menu bar should act on that window.
Steps to Reproduce
- Launch Claude Code Desktop on Windows 11.
- Publish or open any artifact so the separate Artifacts window appears. A dense one makes the effect easiest to see (the screenshot below is a wide diagram whose text is too small to read at the default zoom).
- Put the main Claude Code window somewhere visible at the same time, or note its current text size.
- Click into the Artifacts window to focus it.
- Choose
View > Zoom In, or press Ctrl++. - Observe: the artifact does not change size. The main Claude Code window's content gets larger.
- Repeat with
View > Zoom Outor Ctrl+-. Same result in the other direction.
Is this a regression?
I don't know. This is the first time I have tried to zoom an artifact, so I cannot say whether an earlier build routed it correctly.
Relationship to #62449
#62449 reports the same misrouting for detached/pop-out conversation windows, and its body proposes a root cause that would explain this report as well:
the Cmd+/- handler targetsle.webContents(the main window's WebContentsView) rather thanBrowserWindow.getFocusedWindow().webContents
A comment on that issue also confirms the menu bar route is affected, not only the keyboard accelerator, which matches what I see here.
I filed this separately rather than as a comment because the surface is different: this is the Artifacts viewer, not a detached conversation, and it ships a View menu of its own that presents these as first-class commands. If the fix is the single getFocusedWindow() change, please close this as a duplicate. If pop-out zoom is fixed without covering the Artifacts window, this report is the one that would still be open.
Environment
| Field | Value |
|---|---|
| Claude Code version | 2.1.251 |
| Claude Desktop app version | 1.37937.0.0 (MSIX, x64) |
| Operating System | Windows 11 Pro, build 10.0.26200 |
| Display scaling | Single display |
Additional Information
Screenshot of the Artifacts window's View menu, showing the three zoom commands in that window's own menu bar:
Actual Size Ctrl+0, Zoom In Ctrl++, Zoom Out Ctrl+-
Two things I did not test, so I am not claiming either way:
- Whether
Actual Size(Ctrl+0) is also misrouted. I only exercised Zoom In and Zoom Out. - Whether the Artifacts window inherits the main window's zoom factor at creation time, which is the other half of #62449.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗