The theme this week is consolidation at the standards layer. Three of the moving parts a solo founder builds an agent on top of — the tool protocol, the agent-to-agent protocol, and the way you package a capability — all took a step toward being settled, portable, and vendor-neutral in the same seven days. That is good news for a team of one: settled standards mean less glue code, fewer bespoke integrations, and a stack you can move between vendors without a rewrite. All four items below are verified and dated, each with the single line that matters for how you ship.
1. MCP's stateless spec locks July 28 — and the Extensions are the sleeper story#
The Model Context Protocol's 2026-07-28 specification is in release candidate and locks final on July 28 — six days out. The headline everyone has repeated is that MCP goes stateless: the initialize/initialized handshake and the Mcp-Session-Id header are removed, client info and capabilities ride in _meta on every request, and any request can now land on any server instance. Two new routable headers, Mcp-Method and Mcp-Name, let a load balancer route without inspecting the request body, and MCP-Protocol-Version: 2026-07-28 is now explicit. SSE streams give way to multi-round-trip requests carrying InputRequiredResult payloads.
The under-covered part is the new Extensions framework. Extensions use reverse-DNS identifiers, live in their own ext-* repositories with delegated maintainers, and version independently of the core spec. The first two official ones matter: MCP Apps lets a server ship an interactive HTML interface that the host renders in a sandboxed iframe, and Tasks gives long-running tool calls a task handle driven by tasks/get, tasks/update, and tasks/cancel (note tasks/list was dropped — it can't be scoped safely without sessions). Authorization also hardened across six SEPs, including iss validation per RFC 9207, and Roots, Sampling, and Logging are now deprecated on a 12-month clock.
What it means: Beta SDKs for Python, TypeScript, Go, and C# are out now, and the validation window closes July 28. Run your server and client against them this week — the migration is mechanical, but only if you do it before the lock. We wrote the step-by-step in how to migrate your MCP client to the 2026-07-28 stateless spec and the extensions in MCP's Extensions, Apps, and Tasks.
2. A2A is now native in Google, Microsoft, and AWS#
The Agent2Agent (A2A) protocol, hosted by the Linux Foundation, marked its first year on April 9, 2026 with more than 150 supporting organizations and — the part that changes the calculus — native integration in all three major clouds. Microsoft embedded A2A into Azure AI Foundry and Copilot Studio, AWS added it through Amazon Bedrock AgentCore Runtime, and Google, the protocol's originator, baked it into Vertex AI. LangGraph and CrewAI ship native A2A support, so agents built on different stacks can hand each other subtasks without custom glue. A companion Agent Payments Protocol (AP2) now has 60+ organizations behind agent-driven transactions.
What it means: A2A is inter-agent plumbing, not a day-one dependency. If you run a single agent, it buys you nothing yet. But the moment your product delegates work to an agent you don't own — a partner's, a vendor's, a marketplace's — the fact that the big three clouds all speak A2A natively means you wire it once instead of building three bespoke bridges. The decision framework is in A2A just landed in all three clouds — does a solo founder actually need it yet?
3. Durable execution is now the framework bar#
The signal from the framework race is not a new release — it's an expectation that has hardened. LangGraph's durable-execution model, where agent state persists automatically and a run resumes exactly where it stopped after a restart, timeout, or deploy, has become the baseline that production agents are measured against. LangGraph reached that position on the back of a stable 1.0 (October 22, 2025) and mission-critical use at Uber, LinkedIn, Klarna, and JP Morgan; CrewAI, LlamaIndex Workflows, and Pydantic AI have all moved to answer the same requirement.
What it means: For a team of one, durable execution is the line between a background job you can start and walk away from and one you have to sit and watch. Anything in your product that runs longer than a single request — a research task, an overnight batch, a multi-step approval — belongs on a framework that checkpoints and resumes. Don't hand-roll the persistence.
4. Skills become the portable unit#
Anthropic shipped a course with DeepLearning.AI — Agent Skills with Anthropic, taught by Elie Schoppik — and the reason it matters isn't the course, it's what it standardizes. An Agent Skill is a folder of instructions (and optional scripts) that an agent loads on demand, and that runs identically across Claude.ai, Claude Code, the Claude API, and the Agent SDK. Combine Skills with MCP tools and subagents and you have a repeatable capability you author once.
What it means: Stop re-prompting your workflows. If you have a review checklist, a data-cleaning routine, or a house style you paste into every session, that's a Skill — package it once and it travels with you across every Claude surface. It's the same portability lesson as MCP and A2A, one layer up: the capability, not the vendor, is the thing you own. Start with how to publish and install an Agent Skill.
The throughline across all four: the parts of the agent stack that were bespoke a year ago — session handling, cross-vendor messaging, capability packaging — are becoming standards you adopt instead of infrastructure you build. For a solo founder, every one of those is a week of glue code you no longer have to write.
