Story 1
OpenAI Launched GPT-5.5-Cyber and Made AI Security Patching a Real Workflow
On June 22, 2026, OpenAI expanded its Daybreak cybersecurity program with four launches at once: an updated Codex Security plugin, the full GPT-5.5-Cyber model for verified defenders, a Daybreak Cyber Partner Program, and a new open-source initiative called Patch the Planet. The announcement came from Sam Altman on the same day.
GPT-5.5-Cyber is a specialized model built to find, trace, and help fix security flaws in code. On OpenAI's CyberGym benchmark, it scored 85.6%, compared to 81.8% for the standard GPT-5.5 model. More important than the score is what the model can actually do inside a codebase: it scans commits, builds a threat model specific to that codebase, traces attack paths, validates whether a flaw is actually reachable, and generates a patch — all in a single workflow. The updated Codex Security plugin brings this directly into the Codex CLI and app, which developers already use.
The model is not available to the general public. Access requires verification through OpenAI's Trusted Access for Cyber program. For most engineering teams, the standard Codex Security plugin connected to GPT-5.5 is the practical entry point. The plugin supports SARIF exports and CodeQL queries, meaning findings can flow into existing vulnerability management pipelines without rebuilding how a team tracks issues.
Since the Codex Security research preview opened in March 2026, OpenAI reported the plugin scanned more than 30 million commits across more than 30,000 codebases. Human reviewers marked more than 70,000 findings as fixed, and more than 500,000 findings were automatically resolved.
Patch the Planet, co-founded with Trail of Bits and partnered with HackerOne, brings this capacity to open-source projects. More than 30 projects committed to participate, including cURL, Go, Python, Sigstore, and pyca/cryptography. Participating projects receive ChatGPT Pro access, conditional Codex Security access, and API credits.
500K+
Security findings automatically resolved by Codex Security since March 2026, across more than 30,000 codebases.
Source: OpenAI, June 22, 2026
Scrum Team Signal
Your team's Definition of Done probably does not include an AI security scan. It should. Add a Codex Security review step to your Sprint's done criteria before code reaches review. This is not a future practice — it is available now through the standard Codex CLI. Start with one service, run the plugin against it this Sprint, and triage findings as you would any other bug. Make the results part of your Sprint Review conversation, not a post-release surprise.
Story 2
Google Retired Gemini CLI and Made Antigravity 2.0 the Only Agentic Dev Platform
On June 18, 2026, Google shut off consumer access to Gemini CLI and Gemini Code Assist IDE extensions for AI Pro, AI Ultra, and free-tier users. The replacement is Google Antigravity CLI — a new terminal tool built in Go, designed to be faster and more reliable than its predecessor. Enterprise customers on Gemini Code Assist Standard or Enterprise licenses kept access, but Google's direction is unmistakable: Antigravity is the platform going forward.
Antigravity 2.0, announced at Google I/O in May 2026, is not just a code editor. It is a full development platform with five components: a desktop app, CLI, SDK, Managed Agents API, and an enterprise deployment path through the Gemini Enterprise Agent Platform on Google Cloud. The desktop app runs multiple AI agents in parallel and can schedule tasks to run in the background without a developer actively watching. Developers can use voice commands to direct the agents instead of typing.
The platform uses dynamic subagents — specialized AI agents that can each take a different piece of a task and run at the same time. Google stated that multi-day engineering efforts are collapsing into hours using this capability, which is available now in early research preview. The Antigravity SDK, also released at I/O, lets development teams build their own custom agents using the same underlying harness.
Google said that Gemini 3.5 Flash, the model that powers Antigravity, was itself co-developed using Antigravity — the platform built its own successor model. The new AI Ultra plan for Antigravity costs $100 per month and offers five times the usage limits of the Pro plan. The previous top-tier $250 plan dropped to $200.
4×
Gemini 3.5 Flash runs four times faster than competing frontier models, giving Antigravity agents real-time speed for agentic workflows.
Source: Google I/O 2026 developer highlights
Scrum Team Signal
If your team runs Gemini CLI in any part of your pipeline, sprint pipeline, or personal workflow, that tool stopped working on June 18. Migrate to Antigravity CLI before your next Sprint begins — the commands follow the same pattern and the Google developer blog provides a step-by-step migration guide. More broadly: this week's news signals that multi-agent orchestration in your IDE is becoming table stakes, not an advanced feature. Your team's Velocity conversation needs to account for the time developers spend learning these platforms, or you will underestimate capacity for the rest of the quarter.
Story 3
Anthropic's Claude Opus 4.8 Introduced Dynamic Workflows for Codebase-Scale Work
Anthropic released Claude Opus 4.8 on May 28, 2026, along with a feature called Dynamic Workflows that changed what AI-assisted coding can take on in a single session. The model arrived 41 days after Opus 4.7 — one of Anthropic's fastest turnaround times between major versions.
Dynamic Workflows, available in research preview for Claude Code on Enterprise, Team, and Max plans, lets the model plan a large coding task, distribute pieces across hundreds of parallel subagents, and verify the outputs before handing results back to a developer. Anthropic described the target use case plainly: codebase-scale migrations across hundreds of thousands of lines of code, from kickoff to merge, using the team's existing test suite as the acceptance bar.
One publicly named example: Jarred Sumner, CEO of Bun, used Dynamic Workflows to port the entire Bun codebase — 750,000 lines — from Zig to Rust. That kind of refactoring effort would previously require a working group and a full quarter's worth of Sprint capacity.
The model also improved honesty about its own work. Anthropic's evaluations showed Opus 4.8 is roughly four times less likely than Opus 4.7 to let a code flaw pass unremarked. Early testers at Bridgewater Associates singled out the model's tendency to flag issues with inputs and outputs that other models missed. Opus 4.8 scored 69.2 on SWE-Bench Pro, outperforming GPT-5.5 and Gemini 3.1 Pro on that benchmark. Fast mode runs at 2.5 times the speed and is now three times cheaper than it was on previous models. Standard API pricing remained unchanged at $5 per million input tokens and $25 per million output tokens.
750K
Lines of code migrated in one Dynamic Workflows session — the Bun codebase ported from Zig to Rust using Claude Opus 4.8.
Source: Anthropic, May 28, 2026
Scrum Team Signal
Large refactoring work has always been a Sprint planning headache: the scope is hard to estimate and the risk of breaking things mid-flight is real. Dynamic Workflows changes that calculus. If your backlog holds a codebase migration, a major dependency upgrade, or a large refactoring that your team keeps deferring, bring it into a Sprint conversation now. The model runs against your existing test suite, so your acceptance criteria are already written. Your Scrum Master's job is to help the team understand how to review and validate agent output rather than manage every line of the work itself.
Story 4
The A2A Protocol Is Now Production-Ready — And Your Agents Can Talk to Any Other Agent
During the week of June 15–20, Google's Agent-to-Agent (A2A) protocol and Microsoft's implementation of it came into sharp focus for enterprise development teams. The A2A protocol reached v1.0.0 in March 2026 and is now backed by more than 150 organizations including Google, Microsoft, AWS, IBM, Salesforce, SAP, and ServiceNow. On June 18, 2026, Google published a case study on A2A at scale, highlighting how it enables collaborative agents across platforms without custom integration code.
The A2A protocol defines how AI agents discover each other, exchange tasks, and coordinate work over HTTP — regardless of which company built the agent or what framework it runs on. Think of it the way HTTP made web services interoperable across different platforms and languages. An agent built on Microsoft Foundry can hand a task to an agent built on AWS Bedrock or Google Cloud and get a structured response back, with no custom adapter layer in between.
Microsoft Agent Framework 1.0, released in April 2026, shipped with full A2A v1 support in both .NET and Python. The framework now ships with .NET packages for both the client and server side of A2A, meaning any team using C# or Python can expose their agents to the open protocol or call other organizations' agents in the same way. Microsoft Foundry also added incoming A2A support at Microsoft Build 2026 (June 2–3, 2026), letting teams expose any Foundry agent as an A2A endpoint that outside agents can discover and invoke.
Microsoft's developer blog described the practical implication: a procurement agent can consult a partner's compliance agent without anyone needing to write integration code. When the partner team changes platforms, nothing breaks on your side as long as they stay A2A-compliant. The A2A SDK packages for .NET are available on NuGet today. Python support is also available.
150+
Organizations now supporting the A2A protocol, including AWS, Cisco, Google, IBM, Microsoft, Salesforce, SAP, and ServiceNow.
Source: A2A protocol project, as of April 2026
Scrum Team Signal
Your next architecture discussion needs an item about A2A. If your team is building agents — or your organization is buying software that includes them — the question is not whether agents will need to talk to other agents. They will. The question is whether you will build custom plumbing every time or adopt a standard. Add a spike Story to your backlog: investigate A2A v1 for any agent your team already owns. The Microsoft Agent Framework gives .NET and Python teams a clean starting point with the A2A NuGet packages. This is a good candidate for a two-Sprint proof of concept before it becomes a dependency in production.
Story 5
Gartner: 40% of Enterprise Apps Will Have AI Agents by End of 2026 — But 40% of Projects Will Fail
Gartner released two forecasts this year that software teams need to hold together. The first: 40% of enterprise applications will be integrated with task-specific AI agents by the end of 2026, up from less than 5% at the start of the year. The second: more than 40% of agentic AI projects will be canceled by the end of 2027, because of escalating costs, unclear business value, or inadequate risk controls.
Separately, Gartner's May 2026 worldwide AI spending forecast put total AI investment for 2026 at $2.59 trillion, a 47% increase over 2025. Within that number, agentic AI software spending alone is forecast to reach $206.5 billion in 2026 — up 139% from $86.4 billion in 2025. That is the fastest-growing slice of enterprise software spend. Gartner named 2026 the inflection year for enterprise adoption.
But Gartner's own analysts were direct about the failure risk. Anushree Verma, Senior Director Analyst at Gartner, said: "Most agentic AI projects right now are early stage experiments or proof of concepts that are mostly driven by hype and are often misapplied. This can blind organizations to the real cost and complexity of deploying AI agents at scale, stalling projects from moving into production."
Gartner also published a separate market guide on enterprise AI coding agents in June 2026, estimating the coding-agent market at $9.8 billion to $11.0 billion annualized as of April 2026. The report noted that vendors are now competing not just on code quality but on their ability to coordinate complex workflows and integrate across engineering environments. The key risk called out: organizations that adopt agents without clear operating models risk higher costs without proportional value.
40%
Of agentic AI projects are forecast to be canceled by end of 2027 — due to escalating costs, unclear value, or inadequate risk controls.
Source: Gartner, 2026
Scrum Team Signal
Gartner's failure forecast is not a reason to avoid AI agents — it is a description of what happens when teams skip the governance work. Scrum gives you the structure to avoid that failure mode. Every AI agent your team builds or buys should have a Product Owner who can articulate its value in business terms, a backlog item that defines what "done" looks like, and a Sprint Review that evaluates real outcomes — not just demos. Before your team adds any new AI agent to your stack, answer three questions in your Sprint Planning meeting: What is the measurable outcome this agent enables? Who owns the cost controls? What does the team do when the agent produces a wrong answer? If those answers are not ready, add a spike Story first.
Coming Next Week
OpenAI's GPT-5.6 is expected to launch in the June 22–28 window, with reported changes including a 1.5-million-token context window and a redesigned reward training pipeline. We will cover what that means for engineering teams working with large codebases, and whether the context window improvement actually changes how you use Codex in production.
RC
Rod Claar
Rod Claar has been teaching Scrum, Agile, Test Driven Development, and Software Design Patterns for more than two decades. He currently focuses on how AI is changing the work of software teams — what it means for the way teams plan, build, and ship. He publishes this newsletter weekly at AgileAIDev.com.