Prompt text input overruns chat and glitches/blinks without stopping

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Using the Agents window the box/input displaying an executed prompt repeatedly flashes what looks like a different text wrapping. If I focus the input with a click the flashes stop but the input overruns words rendered below it in the chat. Blurring focus returns to the flashes.

Once the behavior starts it doesn’t correct itself by:

  • Resizing the window or chat pane
  • Moving the Cursor window between displays (Macbook MBP 16" (3456x2234) and external 26" (2560x1440")
  • Restarting Cursor entirely

This could be related to The Chat Text is Blinking however the “Preferences: Configure Runtime Arguments” command palette option advised there for disabling hardware acceleration isn’t returned in my palette. Not sure if something has changed in Cursor releases since that post a bit over a month ago.

Steps to Reproduce

I have experienced this issue on multiple occasions but the exact conditions leading to it are unclear. It could be the length and word mix within particular prompts.

Expected Behavior

This shouldn’t happen. It’s a glitch.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.15.6
VS Code Extension API: 1.128.0
Commit: a1f686545fd0ce8917bbd2449f733551a9bce420
Date: 2026-08-06T01:41:03.876Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report and the video, it makes the issue really clear.

What you’re describing is a rendering issue with the bubble that shows the sent prompt in the Agents Window, and it’s not something wrong with your setup. It’s not the same as the blinking thread you linked, that one has a different cause, mostly GPU or hardware acceleration on Windows. So the Configure Runtime Arguments tip doesn’t apply here, and that’s also why you might not see that command in the palette in your current layout.

I’ve passed this to the team and we’re tracking it. I can’t share a timeline or ETA yet, but I’ll reply in this thread when there’s an update.

Good news is it’s not blocking work, it’s just a visual glitch with no destructive side effects. If you notice it reproduces more reliably with certain prompts, please send an example text, it’ll help us reproduce it.