I wanted to emphasize that this is fairly urgent for me. I have vision issues and rely on larger UI text to comfortably use the IDE. Right now the text appears stuck at XS even though it’s set to XL, which makes the chat panel extremely difficult to read and effectively makes Cursor unusable for me.
Because this setting is an accessibility control, a bug preventing users from resizing text could potentially raise accessibility compliance concerns under WCAG 2.1 Guideline 1.4.4 (Resize Text), which requires interfaces to support text scaling up to 200% without loss of functionality. Since the UI control exists but appears broken, it may be worth escalating this issue internally to ensure accessibility requirements are being met.
Would it be possible to escalate this to the team for a quicker fix or workaround? I’d really appreciate any update or temporary solution since this currently blocks my ability to use Cursor.
Happy to provide logs, screenshots, or test anything if it helps move this forward.
The “Text Size” option of Agent conversation seem to be buggy now. I changed to “Extra Large” but the size is still the same. In fact, any options make no difference.
Cursor Settings → Agents → Text Size
Steps to Reproduce
Go to Cursor Settings → Agents → Text Size and try to change options
When the text size for the Agents panel is set to something other than “Default”, it will still display the text size as Default when re-opening previous agent histories.
Steps to Reproduce
Set the Text Size for agents to Large.
Open an agent chat and start using it.
Close that chat.
Open that previous chat.
OR
Switch back and forth between agent chat tabs.
Expected Behavior
When opening the previous chat, the text will be displayed in accordance with the “Large” setting.
The setting cursor.composer.textSizeScale in user settings.json is not applied when Cursor starts. The composer/chat text remains at default scale (1.0).
The setting only takes effect when I manually open settings.json and press Ctrl+S (save). No actual changes needed — just re-saving triggers it.
Steps to Reproduce
Add “cursor.composer.textSizeScale”: 1.15 to %APPDATA%\Cursor\User\settings.json
Close Cursor completely
Open Cursor
Observe: composer text is at default scale, not 1.15
Expected Behavior
cursor.composer.textSizeScale should be read and applied during initialization, not only on onDidChangeConfiguration event.
Using a workspace task (runOn: folderOpen) that overwrites settings.json with a different value and then restores the original — forcing a config change event. This confirms the setting works on change but not on cold start.
What is the latest version where this is fixed? I’m still encountering this problem (This is still happening for me in version 3.0.13 using the Large text size)
Could you share a bit more detail about what you’re seeing? Specifically:
Does the text size never change when you set it to Large, or does it apply initially but revert to Default when you switch tabs or reopen old chat histories?
Are you using the setting in Cursor Settings > Agents > Text Size, or the cursor.composer.textSizeScale value in settings.json?
There’s a known remaining issue where the text size setting doesn’t persist across tab switches and chat history – that part is still being tracked separately.
In the meantime, Ctrl + / Ctrl - (or Cmd + / Cmd - on Mac) to zoom the whole UI is a workaround that should help with readability.
I am using the setting in Cursor Settings > Agents > Text Size.
Text size applies when i toggle from another size to large, but reverts to default when i switch between chat windows.