The IDE dissolves — into the issue tracker on one side, the browser on the other

GitHub wants you to assign tickets to an agent. Cursor wants you to click on the live page and annotate. Both are answering the same question: when the agent writes the code, what surface does the human actually need?

GitHub's Copilot Coding Agent is generally available: assign an issue, and the agent implements across files, runs CI, and opens a pull request. Meanwhile Cursor's Design Mode lets developers annotate the running UI and hand the agent precise visual targets. Two flagship releases, zero new text-editing features. The tool market has quietly concluded that the editor is no longer where the leverage is.

Asynchronous versus interactive

The two bets carve the workflow at its natural joint. Issue-to-PR owns the asynchronous backlog: well-specified work a team already tickets, delegated wholesale, governed by CI and review. Visual annotation owns the interactive session: underspecified frontend intent, where pointing at the actual element beats describing it in prose. These aren't competing for the same minutes of a developer's day — they're absorbing different ones.

The metered future

Under both surfaces, the same economic shift: usage-based billing, credits per unit of delegated work, subscriptions retired. Agents priced like compute confirm what they've become — infrastructure that does work, not features that assist it. The pricing model always tells you what a product really is before the marketing does.

The developer role this implies is neither obsolete nor unchanged: less typist, more editor-in-chief — writing specifications sharp enough to delegate, reviewing diffs instead of drafting them, and pointing, sometimes literally, at what needs to change. The tools are reorganizing around that person. The industry's job descriptions will follow.

Cosmic JS — Claude Code vs GitHub Copilot vs Cursor (2026) → · Build Fast With AI — 7 AI tools that changed developer workflow (August 2026) →