As a designer I'm following the space quite closely. In the not-so-distant future, we might skip most visual software and work directly with code. Especially if we have cool transitional solutions like this

I'm still wondering about how this approach would work when conceptualizing flows, systems, or more complex interfaces

Isn't this just like Dreamweaver back in the day for people who couldn't read HTML it became WYSIWYG for them?

I'm confused by what Cursor is trying to be. They shipped plan mode and debug mode which are developer focused tools and I'm happy about them.

On the other hand, features like these are kinda distracting to me. I wouldn't mind if it wasn't for the core product and developer features getting buggier day by day.

I've been facing a number of rough edges lately. The plan mode's support for multiple plans in a single chat breaks often, todos don't get created or marked properly, the new changed files UX is atrocious (just take me to the file), it's not able to adhere to simple prompts in a low context window usage chat (Sonnet 4.5), etc.

It sucks to try different editors every few months but I might have to do that if this continues.