July 2026 Summaries

The 2026 State of Software Delivery Q2 Pulse report highlights the growing disparity between top-performing engineering teams and the rest, as AI-driven code generation increases but efficient code shipping remains challenging. Analyzing over 20 million CircleCI workflows, the report notes that while code production is up, elite teams are successfully navigating the complexities of software delivery by focusing on operational habits that enhance speed and reduce costs, such as maintaining a low Merge Efficiency Ratio (MER) and integrating fast feedback in development loops. These teams demonstrate significantly higher throughput, achieving up to 2,165 main-branch workflows per day compared to the median's 1.7, by effectively managing code validation and integrating AI tools like Chunk sidecars to streamline processes. The report suggests that shifting validation tasks earlier in the development process can markedly reduce delivery costs, exemplified by the potential $700,000 savings for a 50-developer team. The document underscores the transition from code generation to validation as the primary bottleneck and encourages teams to adopt strategies that accommodate the increasing code volume driven by AI advancements.

CircleCI has introduced a new 1.0 version of its CLI, rewritten from scratch in Go, aiming to enhance the developer experience by allowing them to remain in the terminal for CI tasks. The overhaul addresses technical debt and usability issues of the previous iteration, prioritizing design principles such as consistent JSON, stable exit codes, and structured error messages, which make the CLI more user-friendly for both humans and coding agents. Key features include a simplified login process via OAuth, a markdown-styled output that provides structured information without relying on flat tables, and a built-in MCP server that integrates with editors like VS Code for seamless operation without additional installation. The CLI also supports theming, interactive debugging, and built-in --jq for JSON manipulation, while maintaining compatibility with environmental settings like NO_COLOR and TTY detection. Currently in beta, CircleCI invites user feedback to refine these features and ensure the CLI meets its high standards.

The text compares the Agent Client Protocol (ACP) and Model Context Protocol (MCP), two complementary protocols that facilitate communication between AI coding agents, editors, and tools. ACP connects code editors to AI coding agents, allowing developers to use various agents with different editors while maintaining their workflow, similar to how the Language Server Protocol (LSP) standardizes language tooling. It enables seamless interaction between the editor and agent, ensuring real-time updates and permission control over code changes. MCP, on the other hand, enables AI agents to access tools and data, with servers that facilitate actions like CI/CD operations by exposing tools, resources, and prompts. These protocols work together to enhance the functionality of AI coding agents, with ACP focusing on editor integration and MCP on tool and data interaction. They are designed to operate simultaneously, providing a robust framework for AI-driven coding environments by ensuring that agents can efficiently communicate across different platforms and contexts.