How much of your Cursor rework is the agent guessing the wrong part of a screenshot?
by•
Half the threads here are about accuracy and fewer iterations. One source of rework I rarely see named: when I paste a screenshot, Cursor has to guess which element on a busy screen I actually meant, and it edits the wrong one. Then I'm re-prompting, which is its own iteration tax.
Curious how much of your rework is this specific thing versus raw model quality. And what's your fix, crop hard, or describe the element in text?
86 views
Replies
I’ve noticed the same thing when working on larger SwiftUI screens. I usually crop screenshots aggressively or describe the exact UI element I want modified. That significantly reduces incorrect edits and saves a lot of back-and-forth iterations.
SlimSnap
@r_aghababa SwiftUI is where I feel it worst, no DOM, no Figma, so the agent has only the pixels to go on. Cropping helps but it's a tax you pay every single time, and aggressive crops sometimes cut the surrounding context the agent actually needs to place the change. Describing the element is better, but that's the part I always get lazy about mid-flow.
What stuck for me was capturing the element and the intent once as structured text, instead of re-cropping or re-describing each round. Same thing you're doing by hand, minus the by-hand. I ended up building a small tool for it (SlimSnap) since I was doing it constantly on Mac UIs.
@bickov That's an interesting approach.
There is no cropping.
It just zooms into the map perfectly.
I downladed the entire sold property db, and migrated it into a Progess db, then addded some indexes etc to speed the queries up
SlimSnap
@rosssaab Ha, sounds like a different build. When you're working on that UI in Cursor though, do you hit the wrong-element guessing, or does the map case dodge it?