1 min lesson
Where Tab actually sits now
Use "Where Tab actually sits now" to explain each part and the role it plays.
Step 1 of 2
Where Tab actually sits now
Tab is Cursor's original signature feature - it put Cursor on the map - but the world has moved to agents: Cursor now sees roughly 2x as many agent users as Tab users, and ~15x agent-use growth across customers over the past year.
Use that stat to steer where a team invests learning effort: Tab is still the everyday speed layer, but the durable value (and the thing a CTO has heard about) lives in Agent and the async surfaces.
The full surface map an SA should be able to name
- Desktop IDE / editor view
- The classic editor; Tab, inline edit and the agent pane
- Agent window (Cursor 3 / Glass)
- The agent-forward default; manage many local and cloud agents at once
- Web + mobile / PWA
- Run Cursor as a PWA on a phone; kick off and review agents away from the laptop
- CLI
- The full harness in the terminal, pipeable into any workflow or CI
- JetBrains (IntelliJ / PyCharm)
- Cursor's agent loop inside JetBrains IDEs via the ACPAgent Client Protocol. An open standard that lets any IDE host any coding agent; Cursor uses it to run inside JetBrains/IntelliJ and Android Studio. Press Enter for the full definition. partnership
- Cloud agents, Bugbot, Agent SDK
- Async agents on their own VMs, AI PR review, and programmatic agent access
You don't demo all of these - but naming them is what separates "editor" from "SDLC platform" in the buyer's head.