Cursor 3.7 Lets Developers Point at UI and See Every Token Spent

Cursor's agents have been able to build interactive dashboards and internal tools inside the IDE for a while now, using a feature called Canvas. But until now, iterating on those artifacts meant typing descriptions into a chat box and hoping the agent understood which element you meant. The 3.7 release changes that in two meaningful ways: you can now point directly at UI elements to edit them, and you can finally see exactly where all your tokens are going.

Point, don't describe

Design Mode is now available in canvases. You can select and annotate UI elements directly in a canvas to guide Cursor's edits, just as you would in the browser. Instead of describing the change in text, you can point to it, provide feedback, and iterate more quickly.

This is the same interaction model that already existed in Cursor's integrated browser for live web apps, now extended to agent-generated canvas artifacts. Design Mode is Cursor's visual editing layer: instead of describing a UI change in text, you point at a live element in the running app and the agent receives its code identity and a screenshot as context. The key detail is what gets sent under the hood -- the agent receives the element's code identity and a screenshot for spatial context, including layout, surrounding elements, and the exact page state.

The 3.7 update also adds multi-select to Design Mode in the browser. Selecting multiple elements together gives the agent their code, surrounding layout, and visual relationships on the page simultaneously, so it can make one match the other, remove repeated content, or adjust a group of components at once. You can also queue edits by voice while an agent is still working. The microphone remains available while an agent is still working, so you can queue the next change by voice before the current one completes.