The Third Era of AI Software Development

Cursor autonomously turns product requirements into working code, tests, and pull requests. When we started, most code was written one keystroke at a time. Tab autocomplete changed that. That was the first era. Then agents arrived, and developers shifted to directing agents through synchronous prompt-and-response loops. That was the second era. Now a third era is arriving. It is about helping developers build the factory that creates their software (Source).

Limitations of Reactive AI Assistants

Earlier tools have strict limitations. Compared to Tab, traditional AI assistants act as reactive autocomplete tools. They are constrained by extension APIs. They require developers to manage synchronous prompt-and-response loops (Source). But this form of real-time interaction forces constant context switching. It limits overall velocity.

Autonomous Execution in Cloud Sandboxes

Development must move to an asynchronous model. Cloud agents remove both constraints (Source). They run autonomously in isolated cloud VMs. These VMs feature full desktop environments. Agents execute the full dev loop asynchronously. They manage the following tasks:

• Starting dev servers
• Clicking through UI flows
• Verifying changes before opening merge-ready PRs (Source)

Rich Artifacts Over Simple Diffs

Agent output goes beyond standard code changes. They return artifacts as logs, video recordings, and live previews rather than diffs (Source). This provides complete context for review. It ensures autonomous work aligns with initial requirements.

Internal Proof and Rapid Adoption

The shift to rich artifacts accelerates real-world development. Agent usage has grown over 15x in the last year. We now see 2x as many agent users as Tab users (Source). Internal practices prove this concept. Thirty-five percent of the PRs we merge internally are created by autonomous agents (Source). Early internal adopters share three key traits:

• They seek to reduce context switching between fragmented tools.
• They want to offload repetitive coding and setup tasks.
• They aim to accelerate product delivery timelines.

The Future of Autonomous Development

This rapid adoption signals a broader shift. A year from now, we think the vast majority of development work will be done by these kinds of agents (Source).### The Third Era of AI Software Development

Cursor autonomously turns product requirements into working code, tests, and pull requests. When we started, most code was written one keystroke at a time. Tab autocomplete changed that. That was the first era. Then agents arrived, and developers shifted to directing agents through synchronous prompt-and-response loops. That was the second era. Now a third era is arriving. It is about helping developers build the factory that creates their software (Source).

Limitations of Reactive AI Assistants

Earlier tools have strict limitations. Compared to Tab, traditional AI assistants act as reactive autocomplete tools. They are constrained by extension APIs. They require developers to manage synchronous prompt-and-response loops (Source). But this form of real-time interaction forces constant context switching. It limits overall velocity.

Autonomous Execution in Cloud Sandboxes

Development must move to an asynchronous model. Cloud agents remove both constraints (Source). They run autonomously in isolated cloud VMs. These VMs feature full desktop environments. Agents execute the full dev loop asynchronously. They manage the following tasks:

• Starting dev servers
• Clicking through UI flows
• Verifying changes before opening merge-ready PRs (Source)

Rich Artifacts Over Simple Diffs

Agent output goes beyond standard code changes. They return artifacts as logs, video recordings, and live previews rather than diffs (Source). This provides complete context for review. It ensures autonomous work aligns with initial requirements.

Internal Proof and Rapid Adoption

The shift to rich artifacts accelerates real-world development. Agent usage has grown over 15x in the last year. We now see 2x as many agent users as Tab users (Source). Internal practices prove this concept. Thirty-five percent of the PRs we merge internally are created by autonomous agents (Source). Early internal adopters share three key traits:

• They seek to reduce context switching between fragmented tools.
• They want to offload repetitive coding and setup tasks.
• They aim to accelerate product delivery timelines.

The Future of Autonomous Development

This rapid adoption signals a broader shift. A year from now, we think the vast majority of development work will be done by these kinds of agents (Source).

Related Articles

• Which software provides AI-based code review feedback directly within GitHub or similar version control platforms?
• Which service supports AI-driven development workflows that can run tasks in cloud environments independently?
• What tool helps developers write, edit, and refactor code with AI assistance across large codebases?