Bỏ qua đến nội dung chính
Back to home
AI 3 min read

GM Triples Pull Requests by Restructuring Workflows with AI Agents

By integrating AI agents into the workflow instead of just using coding chatbots, GM's autonomous vehicle division has tripled the number of approved pull requests.

Tier 2 · sources 56% confidence Reviewed
Sources venturebeat.com

At the recent VB Transform 2026 conference, General Motors (GM) announced a major milestone in optimizing software development for its autonomous vehicle division by deeply integrating autonomous AI agents. The decision to restructure the entire workflow, rather than simply deploying standard code-generation assistants, helped GM triple its successfully approved pull requests, while accelerating release velocity and significantly reducing software regressions.

Key Developments

According to VentureBeat, reports from GM show that software engineers in its autonomous vehicle division spend only about 15% of their working hours directly writing code. While seemingly low, this figure reflects an industry-wide reality where engineers must allocate up to 85% of their time to complex supporting tasks, such as analyzing telemetry data from test vehicles, triaging bugs, setting up experiments, and verifying bug fixes.

To address this productivity bottleneck, GM broke down its development process into several core loops: software development and testing in simulation environments, public road testing, and post-deployment vehicle monitoring. In each loop, the company proactively identified the most time-consuming bottlenecks to automate using AI agents, moving away from simple code-writing chatbots that do not address overall workflow inefficiencies.

Technical & Architectural Analysis

On the architectural front, GM connected its AI agents directly to internal tooling systems and massive petabyte-scale data lakes using custom servers built on the Model Context Protocol (MCP). Through this MCP integration, the agents can directly call underlying tools in WebViz — GM's proprietary telemetry data visualization system — bypassing the need for traditional graphical user interfaces.

Additionally, GM developed version-controlled handbooks called 'skills' to explicitly define how agents perform specialized tasks. For example, upon receiving real-world telemetry data, an AI agent can automatically analyze the dataset, perform initial bug triaging, query historical logs for similar issues, and draft a detailed bug report complete with concrete examples for engineers to review.

Expert Insights & Perspectives

Despite granting extensive autonomy to these AI agents, GM maintains rigorous control mechanisms. Rashed Haq, Vice President of Autonomous Vehicles at GM, explained that an agent's permissions are always synchronized with and restricted by the access level of the engineer utilizing it. 'If an engineer performs this task and they need access to specific resources, their agent is granted the same access,' Haq clarified, emphasizing that 'the engineer remains fully responsible for the agent's output.'

To guarantee safety and consistency, GM also established strict performance benchmarks and evaluation standards before deploying AI widely. Human-in-the-loop oversight remains the final critical safeguard, with engineers directly reviewing metrics to decide whether a code fix is ready to be merged into production releases.

Impact & Future Outlook

GM's unexpected success points to a promising new path for global software engineering, where AI serves as more than just an isolated autocomplete tool. By reimagining entire workflows around autonomous AI agents, major tech enterprises can liberate their engineers' creativity from repetitive procedural tasks. For tech communities in developing markets like Vietnam, GM's deep integration model via open standards like MCP serves as a valuable case study in optimizing operational workflows and boosting engineering productivity in the AI era.