Get the weekly radar
One short email with the freshest products, every week.
Grounded in available product and source data
A verified overview is not available yet.
These 7 comments were collected from the discovery source. ProductVisit does not host replies in Release A.
Hey all! I'm Chris, Mobile Lead at Cursor, excited to hear what you think of our new app. We'll be around to answer questions throughout the day!
6 source upvotesVoice input from the phone sounds useful, but I’d be nervous sending a messy spoken prompt straight to an agent. Does Cursor turn it into an editable brief first, or does the agent start from the raw voice request?
2 source upvotesThe mobile part I keep thinking about is the review step. Kicking off agents from a phone is easy, but merging on the go means approving diffs on a screen where you can't really read a diff, and every time we've moved approvals to a phone people start rubber-stamping. So the agent's summary of what it changed becomes the real gate, not the diff. Does the app surface anything risk-ranked, like this touched auth or deleted tests, or is review just scrolling the raw changes?
2 source upvotesThe always on cloud agents caught my attention . I'd love to hear how they're performing for people using them on real projects using them on real projects.
1 source upvotesThe mobile angle for coding agents is interesting, especially with Cursor already being associated with dev workflows. How much of the iOS experience is meant for actually editing code versus steering an agent through prompts, reviews, and approvals? I’d also be curious whether the app is optimized for existing projects or if it supports starting lightweight tasks from scratch while on the go.
Congrats on the iOS launch! 🚀 The most useful part for me is not full coding on mobile, but starting agents, checking progress, and reviewing work while away from the laptop. Curious how Cursor handles mobile review safety. Does it highlight risky changes like auth, payments, database migrations, or deleted tests before someone approves or merges from a small screen?
The phone surface makes sense if it is treated as a control plane, not a tiny replacement for the main coding environment. The useful moments are reviewing a diff, unblocking an agent, checking a dev server, or capturing context while away from the desk with repo permissions still obvious.