Agent-Driven Development - Two Paths, One Future - Futurum

Archived from: https://futurumgroup.com/insights/agent-driven-development-two-paths-one-future/

Retrieved: 2026-03-04T23:31:36Z

Status: HTTP 200

Skip to content
Market Coverage
News
February 5, 2026
Mitch Ashley
Agent-Driven Development – Two Paths, One Future
Software Lifecycle Engineering
Analyst(s): Mitch Ashley
Publication Date: February 5, 2026
From mid-2025 through early 2026, software platform vendors introduced new approaches to agent-driven development that are forming along two parallel paths. One path emphasizes multi-agent execution, where coordination and parallelism are primary. The other emphasizes intent-first structuring, where specifications and constraints shape how agents act. These paths are not mutually exclusive. OpenAI’s Codex app establishes a concrete baseline for multi-agent execution, providing the market with a reference point for how intent-first structure and governance can be applied as agent work moves into production environments.
What is Covered in this Article:
OpenAI’s Codex app establishes a baseline for multi-agent software development.
Two parallel paths are emerging: multi-agent execution and intent-first structuring of agent behavior.
IDE-centric tools are evolving toward multi-agent execution through different entry points and priorities.
All approaches face the same constraint: enterprise-grade governance for parallel agent execution remains immature.
The News:
In early February 2026, OpenAI announced its Codex app, a macOS desktop application designed to support AI-assisted software development using multiple agents. The app provides an interface for interacting with AI agents that perform software-related tasks, including code generation, modification, testing, and documentation across projects.
The Codex app introduces several capabilities intended to support parallel agent work. These include Skills, which define reusable agent capabilities; Automations, which allow agents to run tasks on a scheduled basis or in the background; and worktrees, which enable agents to operate in isolated environments while working on the same codebase. Agents can run for extended periods and request user approval when broader system access is required.
The application integrates with GitHub for repository access and pull request workflows and connects to the broader ChatGPT account environment. OpenAI states that Codex runs in a sandboxed environment by default, with restricted permissions, and supports configurable access controls for executing commands or modifying files.
According to OpenAI, the Codex app is powered by its Codex model family and is intended to support development tasks across multiple stages of the software lifecycle. The company positions the app as a standalone desktop experience rather than an extension of an existing integrated development environment.
Agent-Driven Development – Two Paths, One Future
Analyst Take — Two Parallel Paths Toward Agent-Driven Development:
Agent-driven development is no longer theoretical. What is unfolding across the market are two parallel paths toward the same outcome: AI agents performing execution across the software lifecycle under human direction.
The first path is multi-agent execution. In this model, developers coordinate multiple agents working in parallel, assign tasks directly, and supervise outcomes as work progresses. Anthropic’s Claude Code and OpenAI’s Codex app exemplify this approach. Both treat agent coordination, parallelism, and long-running execution as first-class workflow elements, with structure and constraints introduced as execution unfolds.
The second path emphasizes intent-first (or requirements-first) structuring of agent work. Here, explicit requirements, design artifacts, and constraints shape how agents act before execution begins. Platforms such as Amazon Web Services’ Kiro, IBM’s Project Bob, and planning-oriented modes within Google’s Antigravity initiative emphasize intent capture as the control surface for agent execution. Agents still perform the work, but within boundaries defined upfront.
These paths are complementary rather than competitive. Both assume agents execute meaningful work. They differ primarily in sequencing: whether coordination and execution come first, or whether intent and structure come first. Increasingly, both approaches coexist within the same platforms and workflows as vendors blend coordination, execution, and upfront constraint in preparation for production use.
Multi-Agent Execution Enters Through Different Entry Points
Multi-agent execution is not emerging from a single tool or workflow. Vendors are entering the multi-agent path from different starting points, emphasizing different priorities while converging on parallel agent execution as a core capability.
GitHub’s Agent HQ represents a governance-first entry into multi-agent execution. It is designed as a centralized hub for running and managing multiple agents within a single project, with a focus on guardrails, identity, approvals, and sandboxed execution. By anchoring agent orchestration in DevOps and security workflows, GitHub treats agents as long-lived actors whose actions must be governed, auditable, and constrained from the outset.
Anysphere’s Cursor represents a developer-speed-first entry into multi-agent execution. Cursor supports running multiple agents in parallel on isolated workspaces, often using separate branches or worktrees, with developers reviewing and merging agent-produced diffs. This places Cursor closer to Codex-style multi-agent execution than to IDE augmentation, even though the IDE remains the primary interaction surface.
Windsurf takes a different approach. It is best described as a single-agent-centric, agentic IDE optimized for deep context, large codebases, and long-running sessions with a powerful primary agent. While multiple agent interactions are possible across separate contexts, Windsurf does not currently emphasize first-class parallel agent orchestration as Codex, Cursor, or Agent HQ does.
These approaches illustrate how multi-agent development is forming through varied sequencing rather than a single canonical model.
Why Codex Establishes a Multi-Agent Baseline For OpenAI
OpenAI’s Codex app matters because it establishes a clear baseline for multi-agent execution. It makes coordination, parallelism, and extended agent runtime a primary workflow rather than an experimental add-on. That baseline gives enterprises and competing vendors a concrete reference for evaluating what is required next.
Intent-first approaches can layer structure, policy, and compliance on top of this execution model. IDE-centric tools can evolve toward it. Codex does not define the end state of agent-driven development, but it does provide a starting point for understanding how multi-agent systems behave in practice.
The Shared Constraint: Governance
Across multi-agent execution and intent-first structuring, the same constraint applies. Parallel, persistent agent execution introduces coordination risk without a corresponding governance infrastructure.
Observable agent behavior, runtime policy enforcement, and provenance tracking remain incomplete across platforms. A common failure scenario illustrates the issue: one agent modifies infrastructure configuration, another updates tests based on a prior state, and a third generates documentation assuming success. No individual agent is “wrong,” yet the system becomes inconsistent and difficult to audit or recover.
This is why the future of agent-driven development will not be determined solely by execution sequencing. It will be determined by how effectively governance is integrated into agent execution itself.
What to Watch:
Convergence signals: Where multi-agent execution platforms add intent capture and where intent-first platforms support more dynamic execution.
Governance integration: When enforceable policy controls, evidence generation, and audit trails become native to agent workflows.
Enterprise adoption patterns: How regulated industries sequence intent and execution differently from commercial teams.
Augmentation limits: The point at which IDE-centric approaches fail under coordination complexity.
Hybrid workflows: Whether platforms support mixing multi-agent execution and intent-first structuring within the same development lifecycle.
Read
OpenAI’s Codex app announcement
for full details.
Disclosure: Futurum is a research and advisory firm that engages or has engaged in research, analysis, and advisory services with many technology companies, including those mentioned in this article. The author does not hold any equity positions with any company mentioned in this article.
Analysis and opinions expressed herein are specific to the analyst individually and data and other information that might have been provided for validation, not those of Futurum as a whole.
Other insights from Futurum:
AI Reaches 97% of Software Development Organizations
100% AI-Generated Code: Can You Code Like Boris?
Dynatrace Perform 2026: Is Observability The New Agent OS?
Harness Incident Agent: Is DevOps Now The AI Engineers of Software Delivery?
Author Information
Mitch Ashley
Mitch Ashley is VP and Practice Lead of Software Lifecycle Engineering for The Futurum Group. Mitch has over 30+ years of experience as an entrepreneur, industry analyst, product development, and IT leader, with expertise in software engineering, cybersecurity, DevOps, DevSecOps, cloud, and AI. As an entrepreneur, CTO, CIO, and head of engineering, Mitch led the creation of award-winning cybersecurity products utilized in the private and public sectors, including the U.S. Department of Defense and all military branches. Mitch also led managed PKI services for broadband, Wi-Fi, IoT, energy management and 5G industries, product certification test labs, an online SaaS (93m transactions annually), and the development of video-on-demand and Internet cable services, and a national broadband network.
Mitch shares his experiences as an analyst, keynote and conference speaker, panelist, host, moderator, and expert interviewer discussing CIO/CTO leadership, product and software development, DevOps, DevSecOps, containerization, container orchestration, AI/ML/GenAI, platform engineering, SRE, and cybersecurity. He publishes his research on
futurumgroup.com
and
TechstrongResearch.com/resources
. He hosts multiple award-winning video and podcast series, including DevOps Unbound, CISO Talk, and Techstrong Gang.
Related Insights
March 4, 2026
Market Coverage
News
Microsoft Leaders Have an Answer To AI Gutting the Developer Pipeline
Mitch Ashley, VP and Software Lifecycle Engineering Practice Lead at Futurum, examines Microsoft leaders' warning that AI productivity gains are gutting the developer talent pipeline and how their preceptorship model...
Mitch Ashley
March 3, 2026
Earnings
Market Coverage
Elastic Q3 FY 2026: Strong Quarter, but Reacceleration Thesis Unproven
Nick Patience, VP and Practice Lead for AI Platforms at Futurum reviews Elastic Q3 FY 2026 earnings, highlighting sales-led subscription momentum, AI context engineering adoption, and agentic workflow expansion across...
Nick Patience
March 3, 2026
Market Coverage
News
Google ADK Is Not a Toolkit – It Is an Agent Execution Framework
Mitch Ashley, VP and Practice Lead of Software Lifecycle Engineering at Futurum, shares his insights on how Google ADK’s new integrations turn agent frameworks into an execution layer, connecting GitHub,...
Mitch Ashley
February 26, 2026
Market Coverage
News
IBM vs. Anthropic: A Tale of the COBOL Modernization Tape
Mitch Ashley, VP & Software Lifecycle Engineering Practice Lead at Futurum, examines the IBM vs. Anthropic COBOL modernization debate and explains why choosing the right AI tool is the wrong...
Mitch Ashley
February 24, 2026
Market Coverage
News
Claude Found 500 Zero-Days. Who Patches Them Before Attackers Arrive?
Mitch Ashley, VP & Practice Lead at Futurum, shares his insights on AI-driven zero-day discovery and why Anthropic’s Claude Code Security exposes a race condition between vulnerability discovery and patch...
Mitch Ashley
February 24, 2026
Market Coverage
News
AWS’s Deploy-to-AWS Plugin: Frictionless Deployment or Developer Honeypot?
Mitch Ashley, VP Practice Lead at Futurum, examines AWS Agent Plugins for AWS and why the deploy-to-AWS plugin is less a developer productivity tool and more a strategic move to...
Mitch Ashley
Welcome to The Futurum Group
Login to The Futurum Group
Login to Futurum Intelligence Platform
Login to Futurum Labs Research Library
Book a Demo
Newsletter Sign-up Form
Get important insights straight to your inbox, receive first looks at eBooks, exclusive event invitations, custom content, and more. We promise not to spam you or sell your name to anyone. You can always unsubscribe at any time.
All fields are required
Email*
First Name*
Last Name*
Country*
United States
Afghanistan
Âland Islands
Albania
Algeria
American Samoa
Andorra
Angola
Anguilla
Antarctica
Antigua and Barbuda
Argentina
Armenia
Aruba
Australia
Austria
Azerbaijan
Bahamas
Bahrain
Bangladesh
Barbados
Belarus
Belgium
Belize
Benin
Bermuda
Bhutan
Bolivia
Bosnia and Herzegovina
Botswana
Bouvet Island
Brazil
British Indian Ocean Territory
Brunei Darussalam
Bulgaria
Burkina Faso
Burundi
Cambodia
Cameroon
Canada
Cape Verde
Cayman Islands
Central African Republic
Chad
Chile
China
Christmas Island
Cocos (Keeling) Islands
Colombia
Comoros
Congo
Congo, The Democratic Republic of the
Cook Islands
Costa Rica
Cote D\'Ivoire
Croatia
Cuba
Cyprus
Czech Republic
Denmark
Djibouti
Dominica
Dominican Republic
Ecuador
Egypt
El Salvador
Equatorial Guinea
Eritrea
Estonia
Ethiopia
Falkland Islands (Malvinas)
Faroe Islands
Fiji
Finland
France
French Guiana
French Polynesia
French Southern Territories
Gabon
Gambia
Georgia
Germany
Ghana
Gibraltar
Greece
Greenland
Grenada
Guadeloupe
Guam
Guatemala
Guernsey
Guinea
Guinea-Bissau
Guyana
Haiti
Heard Island and Mcdonald Islands
Holy See (Vatican City State)
Honduras
Hong Kong
Hungary
Iceland
India
Indonesia
Iran, Islamic Republic Of
Iraq
Ireland
Isle of Man
Israel
Italy
Jamaica
Japan
Jersey
Jordan
Kazakhstan
Kenya
Kiribati
Korea, Democratic People'S Republic of
Korea, Republic of
Kuwait
Kyrgyzstan
Lao People\'S Democratic Republic
Latvia
Lebanon
Lesotho
Liberia
Libyan Arab Jamahiriya
Liechtenstein
Lithuania
Luxembourg
Macao
Macedonia, The Former Yugoslav Republic of
Madagascar
Malawi
Malaysia
Maldives
Mali
Malta
Marshall Islands
Martinique
Mauritania
Mauritius
Mayotte
Mexico
Micronesia, Federated States of
Moldova, Republic of
Monaco
Mongolia
Montserrat
Morocco
Mozambique
Myanmar
Namibia
Nauru
Nepal
Netherlands
Netherlands Antilles
New Caledonia
New Zealand
Nicaragua
Niger
Nigeria
Niue
Norfolk Island
Northern Mariana Islands
Norway
Oman
Pakistan
Palau
Palestinian Territory, Occupied
Panama
Papua New Guinea
Paraguay
Peru
Philippines
Pitcairn
Poland
Portugal
Puerto Rico
Qatar
Reunion
Romania
Russian Federation
RWANDA
Saint Helena
Saint Kitts and Nevis
Saint Lucia
Saint Pierre and Miquelon
Saint Vincent and the Grenadines
Samoa
San Marino
Sao Tome and Principe
Saudi Arabia
Senegal
Serbia and Montenegro
Seychelles
Sierra Leone
Singapore
Slovakia
Slovenia
Solomon Islands
Somalia
South Africa
South Georgia and the South Sandwich Islands
Spain
Sri Lanka
Sudan
Suriname
Svalbard and Jan Mayen
Swaziland
Sweden
Switzerland
Syrian Arab Republic
Taiwan, Province of China
Tajikistan
Tanzania, United Republic of
Thailand
Timor-Leste
Togo
Tokelau
Tonga
Trinidad and Tobago
Tunisia
Turkey
Turkmenistan
Turks and Caicos Islands
Tuvalu
Uganda
Ukraine
United Arab Emirates
United Kingdom
United States Minor Outlying Islands
Uruguay
Uzbekistan
Vanuatu
Venezuela
Viet Nam
Virgin Islands, British
Virgin Islands, U.S.
Wallis and Futuna
Western Sahara
Yemen
Zambia
Zimbabwe
By checking this box, you agree to our
privacy policy
and to sign up for emails from Futurum.
Subscribed
Thank you, we received your request, a member of our team will be in contact with you.