New Agents Window text is tiny - doesnt respect zoom in or text size in the settings

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor new Agents Window doesn’t respect zoom in instructions neither the text size instructions set
Its way too small and doesnt zoom in neither via cmd + (using mac) neither from the wondow settings which has the text set for very large c

This is apparently a bug , I can’t use the agents window becaus text is way too small

Steps to Reproduce

Mac
open the Agents Window
try to zoom in via cmd + or via chanding the text size in the setting to large

text doesnt change

Operating System

MacOS

Version Information

Version: 3.0.16
VSCode Version: 1.105.1
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
Date: 2026-04-09T05:33:51.767Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. This is a known issue. Agents Window uses its own zoom system, separate from the main IDE. So Cmd+= and settings like editor.fontSize and window.zoomLevel don’t affect it.

Workaround: inside the Agents Window, go to Settings > Appearance. There are separate UI Font Size and Code Font Size settings. You can use those to increase the text size.

The team is aware of the issue. Let me know if the workaround helped.

Thank you for the workaround , unfortunately the workaround did not work.
any ETA for the fix ?

And what will you guys do to avoid bugs like this in production releases?

Hey, sorry the workaround didn’t help. To figure out what’s going on, a couple of quick questions:

  1. Did you open Settings > Appearance inside the Agents Window (via the gear menu in the Glass window), not in the main IDE? These are different settings.
  2. What exact values did you set for UI Font Size and Code Font Size? A screenshot of the Appearance panel plus what it looks like after the change would help a lot.
  3. After changing the values, did you try closing and reopening the Agents Window?

On the ETA, honestly there’s no exact timeline. The issue is being tracked, but there’s no fix date scheduled yet. As soon as there’s an update, I’ll post it here.

On your second point, that report is really helpful. We’re sharing it with the Glass team. The new Agents Window is still being actively worked on, and reports like this help catch cases QA misses.

Thank you Dean for the update