Is Cursor Only for Programmers?

Ryo Lu says Cursor is not something specific just for programmers or even for coding. The models are themselves general purpose: they have read the whole world, all the public information and knowledge, and all the repositories on GitHub. The tool should fit how a person thinks and the input method they prefer.

Focusing on one problem out of maybe 20, then building the whole concept from that single problem, will not scale and will not be as flexible. Designers love pictures and think in 2D space, sometimes drawing little boxes and sometimes making a high fidelity mock. PMs set constraints in longer text, not a short chat prompt. Coders maybe also build a prototype to set an idea. Pictures, longer specifications, and prototypes can be unified. The interface adapts to people and is not stuck in what the designer had in mind for one specific problem. It changes based on what someone does, who they are, whether they are a single person or working with a team or a big team, the piece they care about, and the form they prefer.

A terminal and CLI workflow is fine. Trying a random idea on the phone works too. All of them talk to the same agent and the same underlying structures. Cursor becomes a lingua franca, almost a new type of state machine: a surface where people with different languages and different ergonomics work on a common system and common sets of agents.