Agent screen captures are not in sync

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The agent captured screenshots, modified the UI, and posted new screenshots, but the new images still show the old UI. When I check the website in my browser, the new screenshots correctly reflect the updated UI.

Steps to Reproduce

  • Ask cloud agent to capture a screenshot.
  • Ask cloud agent to modify the UI.
  • Ask Claude agent to take a new screenshot.
  • Cursor is still displaying the old screenshot inside of the new one (code is good, and web IDE is displaying the new one)

Expected Behavior

  • Displaying the same screenshot as in the web IDE.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.23.12
VS Code Extension API: 1.128.0
Commit: 2d29876d567da1607532b23bbf2cd5ddbca496f0
Date: 2026-10-01T04:41:16.627Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.6.0

Additional Information

It’s a long-term issue happening already months ago.

Also, I just noticed in the web IDE’s conversation that the original screen captures are also replaced by the new one, and they should not be because at this point in the thread history, the UI fix asked did not exist.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @Blaydator, thanks for the report and the video.

What you’re seeing isn’t intended. In that conversation, the agent saved the second screenshot over the first one, using the same file name. Both messages point to that single file. The web view then shows the newest version in both places, which is why the earlier screenshot looks replaced. The desktop app keeps showing the copy it loaded first, which is why both images there still show the old UI.

We’ve let the team know, and this is an issue we’re tracking. I’ll post here when there’s an update.

Until then, asking the agent to save every new screenshot under a new file name keeps the two captures from sharing one file. To make that more likely to stick, one option is to add a line like “When taking screenshots, always save them under a new, unique file name and never overwrite an existing one” to your repo’s AGENTS.md. Cloud agents read that file: Rules | Cursor Docs