Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
I am trying to switch from VS Code to Cursor in the hopes the AI experience will be better.
There are 3 major issues:
-
The hover buttons that show every time I select text: Add to Chat, and Quick Edit. It is infuriating when I select text to read with my screen reader (No, I do NOT use VoiceOver – people are not either 100% blind or 100% sighted, I use an on-demand screen reader that I wrote myself in Swift and Rust that reads the selection on demand) and suddenly, the chat pane pops open because I accidentally clicked the Add to Chat button.
Further, when I realized why this was happening (I did not even see the Add to Chat button until now, I thought it was just opening the chat pane magically), there is no menu accessible way to run Add to Chat programmatically, e.g. from the Commands menu. This is a UX disaster! VS Code has “Add File to Chat” and “Add Selection to Chat”. Why take something away from us that we already had to create a worse, mouse-dependent path/experience?
-
Why is there no way to customize the font size of the chat text, input, and UI elements in the chat window? Because I have photophobia – light sensitivity – and have to strain to see small elements on screen easily, it’s very hard to use. I get migraines often. I want huge buttons, huge text input, huge chat response fonts – and I don’t want to enlarge the entire Cursor window UI with Command-+ so large that there is no room for text. That’s just not useful. In VS Code there were several CSS extensions, which somehow are not available in Cursor, with which I could customize the VS Code UI to my needs – in spite of the fact that Microsoft designed it so that modifying CSS “corrupts” the VS Code application and it constantly nags me about this, and often reverts the settings. Why in the world is Cursor so unfriendly to adjusting the Chat UI since it is basically a WebView anyway, and we could just be allowed to use CSS to style its elements to our liking? I don’t understand how, in the supposed “golden era” of software engineering (I don’t buy it!), with all the AI tools we have available, software – especially web-based (well, OK, Electron-based – but web tech nonetheless) software like VS Code/Cursor – is becoming less and less customizable to the user. Is it lack of awareness, lack of priority, belief that users with disabilities are unprofitable? As an accessibility expert, I really don’t understand with all the resources available, how it is that the user isn’t just allowed to customize their UI to fit their needs. Allowing us to do that would be really, really simple: just allow a user CSS stylesheet, and inject said user CSS, if provided, into the web view at runtime. Simple? Yes. Benefit-to-effort ratio? Very, very high.
-
The Chat window scrolls to the top constantly when de-focused/focused. Because I use my on-demand screen reader (again, that I wrote myself, because full-time screen readers are not catered for most visually impaired users – only 1% of the world’s population is totally blind) – I have to switch focus between windows often, and to lose my position in reading the chat, which as you know, gets long quickly because AI is trigger-happy in generating gobs and gobs of text – is a terrible user experience. It’s hard to read when it keeps scrolling to the top, I look over to the window, and see conversation from 10 minutes ago, and I cannot even focus, and hit the End key or similar, to scroll to the bottom. So there are 2 issues here: a. changing context/position without user interaction (the scrolling without provocation – if that makes sense), and b. lack of keyboard accessibility. I could give you the WCAG guidelines, but everyone is so focused on WCAG, I want to give you the actual user’s point of view here without quoting the WCAG, because it really doesn’t matter. It’s about the user, not about the WCAG. I’ve seen other complains about this on here, but it impacts users with visual impairments just as much, if not more severely, than anyone else.
With all that being said, I really, REALLY LIKE and appreciate the fact that it seems I can select text in the AI chat while it is generating, and read it. VS Code did NOT allow me to do this, it kept resetting the selection with every character generated. It seems the AI chat is structured better such that it does a section, moves on to another section, and I can read the “completed” section as the rest is being generated/worked on. So thank you for this, and please keep that up when improving it.
Steps to Reproduce
These are UI issues as described above. I don’t know how to describe reproduction other than to test the UI elements and interactions listed above.
Expected Behavior
My position is always that accessibility is not a “feature”, but inherent to good design. Accessibility is not an add-on, a nice-to-have, something we can do after we become profitable, a chore, a burden, or any of these other myths. Accessibility is a subset of all UX, and you cannot have good UX without it.
Operating System
MacOS
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.6.42
VSCode Version: 1.99.3
Commit: 5911e9593196a000b1c00553aaf03b0b32042b90
Date: 2025-09-20T17:16:56.346Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0
For AI issues: which model did you use?
The scrolling/text size/editor issues are model-agnostic.
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor