GPT-5 makes sense when the goal is breadth, not an IDE-specific workflow. As a generalist model, it can switch between coding, product thinking, writing, troubleshooting, and planning without requiring a dedicated editor fork or a particular developer setup.
Compared with Cursor’s repo-indexed, multi-file editing experience, GPT-5 is often the simpler choice for quick iterations: ask, refine, and move on. It’s especially useful when the task is conceptual—API design, trade-off analysis, data modeling, or explaining a bug—before committing changes to the codebase.
It also works well as a consistent “one model” layer across many tools and contexts: docs, tickets, emails, and code snippets. That flexibility can matter for cross-functional teams who don’t live inside a single IDE all day.
The trade-off is that you’ll typically rely more on careful prompting and manual context management than you would with a repo-indexing editor, but you gain a broadly capable assistant that fits almost any workflow.