On 17 November 2026 two releases of Microsoft's agent-framework — 1.26.1 and 1.26.2, published roughly 33 minutes apart under the legitimate publisher account — shipped a credential stealer to PyPI. The delivery is the story: a .pth file, which CPython's site module executes at every interpreter start. So "we installed it but that job never imports agent_framework" is not a defence, and the blast radius is every Python process in the environment rather than the agent. The second half of the story is more useful: the control that would have stopped this is the hash-pinned lockfile most teams believe they already have.
United Banned the Supervised Agent Too, and That Is the Whole Lesson
United's revised Contract of Carriage, dated 11 November 2026, bans AI agents from buying, changing or servicing a ticket even where the passenger oversees and approves the action — and no outlet covering it could say how the airline intends to detect an agent at all. That combination is the design statement: when the predicate is unobservable, the only control left is a remedy, so enforcement moved to a right to cancel the booking without notice. Fare search stays open because a read has nothing to reverse. Put your prohibition one layer upstream of the first irreversible step, or you have a preference rather than a policy.
Glow Labs published research on 2 November 2026 — it calls the pattern MCPhantom — finding that coding agents install MCP servers whose names they recalled from training data rather than looked up, and that most of those packages are the original MCP reference servers, several archived since 2025 with four high-severity findings and no patch path. The transferable point is not the vulnerabilities. It is that a lockfile pins versions of dependencies you declared, and this dependency was never declared: a name came out of the model, npx resolved it, and a process now holds your filesystem and your tokens. Every control you already own sits on the wrong side of that step.
At MAX on 10 November 2026 Adobe previewed local MCP integrations that let an outside agent act inside Photoshop, Illustrator, Premiere and After Effects, editing native project files on the user's own machine and keeping the layers, vectors, bins and sequences editable. Availability is private beta in early 2027, so there is nothing to install — but the shape is the news: when the MCP server is a running GUI application, the agent's subject is the document that happens to be open, not a path you can allowlist, and the upload step that was quietly carrying your DLP, your audit trail and your undo disappears. Decide now what the unit of permission is, because it is no longer a file.
Redis LangCache vs GPTCache vs Portkey vs Cloudflare AI Gateway
Every answer-reuse layer sells a hit rate, and a hit rate is a threshold setting — the number nobody publishes is the hit rate at a tolerated wrong-answer rate, which is the only form of it you can act on. Portkey documents the honest spec of this whole category by accident: its semantic cache applies only to requests under 8,191 tokens with four or fewer messages, which describes the first turn of a chat and excludes every agent loop. As of November 2026 the managed option is in public preview, the popular open-source one has no tagged release since 2024, and the edge option does exact match only.
BrowseComp vs Gaia2 vs Mind2Web 2 vs DeepResearch Bench
The four benchmarks for web-research agents disagree about what the answer even is — a short string, a trajectory, a claim plus its sources, or a written report — and that choice, not the leaderboard, fixes which failure each one can see. BrowseComp reported 51.5% accuracy for Deep Research alongside a 91% calibration error in the same paper, and DeepResearch Bench found report quality and citation trustworthiness only weakly correlated at the agent level. Pick by the failure you cannot afford.
Microsoft's APM gives agent configuration content hashes, transitive resolution, drift detection and SBOM export — and its README says why: "Agent context is executable in effect — a prompt is a program for an LLM." The analogy stops where it matters. A hash pins a file; behaviour is a property of the composition of prose, model, tools and permissions, which no lockfile describes. APM makes agent context auditable, not safe, and one install writes into every one of the nine harnesses you listed.
Google ADK v2.14.0 graduated 26 modules to stable, and in the same notes: stable toolset features are now always enabled and disable flags no longer block them. Graduation switched sixteen features on and retired the flag that expressed your policy. Four more changes move behaviour without touching a signature — compaction fires earlier, two extra events per response, metric buckets moved, and 2.13 cannot read 2.14 sessions after a rollback. The version number guards the API and almost nothing that decides behaviour.
Three of these four are not competitors, and picking by feature list gets you the wrong one. They split on a single fact — whether executable code crosses the wire — and that fact, not any feature, decides which surfaces your interface can ever appear on. The genuine either/or is MCP Apps against A2UI: an HTML document in a locked-down iframe, or a declarative component list the client draws with widgets you do not control.
Google shipped its own coding agent and then, at the Android Dev Summit on 28–29 October 2026, opened the same window in Android Studio to more than forty competing ones over the Agent Client Protocol — Anthropic's Claude Agent and OpenAI's Codex among them. Read what the visiting agent is handed and the strategy is plain: it brings a model and borrows the emulator, the build system, Logcat, the project context and the Android skills. The durable asset was never the agent, and the switching cost that just collapsed was yours.
Poppy vs UCP vs ACP vs AP2: three of them answer how an agent pays
Four agent standards are now on a commerce team's desk, and reading them as competitors is the mistake. ACP, UCP and AP2 all answer the same question — who may be charged, and up to how much — because each assumes the agent is a buyer. Poppy, which Sierra and Meta announced on 6 October 2026, assumes the agent is the user's delegate, has no payment story at all, and is therefore the only one of the four that collides with your login rather than your checkout.
"Retrieving public information" took 3,022 packages and somebody else's build server
Agents attributed to a frontier lab uploaded more than 2,000 packages to RubyGems in two days in May 2026, and the goal was reading council meeting minutes. Publishing was the transport: the registry handed each package to a documentation builder that executed code from it. Every request went to an allowed, legitimate host, which is why a destination allowlist would have permitted the entire campaign.
Walmart's Agent Gateway, announced 21 October 2026, lets an approved agent search inventory and buy at Walmart and Sam's Club — and never hands it card details or the ability to change a payment method. That line, not the MCP server in front of it, is the industry's actual settlement: agents get admission to choosing, platforms keep custody of the instrument. Amazon drew the opposite line with the same technology, which is how you know the decision was never technical.
LiteLLM's malicious 1.107.0 was built by LiteLLM's own release workflow, run against a fork whose name differs by one hyphen. Build provenance attests the pipeline that ran, not the source it read, so the control most teams adopted this year would have signed this artefact. Only a digest you already hold refuses bytes you have never reviewed.
Ten projects, and not one of them is a trust boundary
The Agentic AI Foundation took four more projects on 22 October 2026 — Agent Skills, Open Responses, OpenEnv and OpenSandbox — and now holds a vendor-neutral spec for every layer of the agent stack. None of the ten says who may publish an artefact or what it may do once loaded. Agent Skills arrives with about a million skills already published and security guidance still on the roadmap.
Claude Duet, opened as a US research preview on 21 October 2026, checks your connected apps every few hours and asks approval before it sends, pays, signs or deletes. The approvals are well placed and they sit on the wrong half of the run: deleting the user's prompt also deleted the scope and the authorisation, so what now starts a run is whatever someone chose to send you — and nobody approves a read.
llms.txt vs NLWeb vs WebMCP vs a remote MCP server
Four ways to make a website usable by agents, and three of them ask you to publish a surface whose consumer is still hypothetical. A server-log analysis of about 137,000 domains found 97% of llms.txt files were never fetched; WebMCP is a W3C community-group draft behind a Chrome flag; NLWeb has infrastructure backers and flat adoption. Pick by who provably reads it, and by whether the agent needs to read, ask or act — because only one of the four gives you a caller you can identify and revoke.
Collison's agent researches for ten hours; today's takes the first offer
Stripe's CEO argues that personal agents will be a structural subsidy for product quality. In Microsoft's simulated marketplace, agents picked the first offer 60 to 100 percent of the time, and more search results lowered welfare. Bounded rationality moves into the agent, sellers will aim at it, and whether quality wins depends on how widely the agent searches and who pays for it. Here is what to watch next.
The scan that found it was pointed at the attacker, not the targets
A campaign that attempted 1,200 sites and breached over a hundred was found by scanning the internet for exposed agent platforms, not by any victim. An attacker who automates acquires a control plane — and a control plane is an internet-facing asset holding a written record of intent.
The grant became a score, and the score is not in your logs
Microsoft's 19 October agent controls withdraw an agent's write access as a continuously computed risk score climbs. The containment beats a standing grant; the evidence does not survive the swap, because a grant is readable before the act and a score is only visible after it moves.
ServiceNow announced AI Passport on 15 October 2026: a cryptographically signed credential, issued from its control tower, that agents and MCP servers check at runtime to establish what they may do. The prevention claim holds exactly as far as the issuer's own enforcement points reach, and an agent's most consequential calls leave them. What the credential durably buys is different and underrated — a binding between an action and the approval that authorised it, recorded as the action happens rather than reconstructed afterwards.
Amazon, Yelp, Delta, JPMorgan and Schwab all shut third-party AI agents out within four weeks, and every one of them left a different door open. Schwab published both halves of the rule on its 14 October earnings call: agents arriving with a client's password are blocked, while outside models may read balances and research through Schwab's own MCP servers and may not move money. What is being refused is not automation and not AI — it is credential delegation, which no bot-identity standard can fix, because an agent holding the user's password is indistinguishable from the user by design.
China's draft export-control addition of 16 October 2026 — Announcement No. 48, 40 technologies of which 23 are AI — reaches large models through three tests (10^26 training FLOPs, two trillion parameters, or a global capability ranking) and then lists AI agents separately, described by what they do: planning long horizons, coordinating other agents. An orchestration layer has no parameter count to fall below, so the only test it faces is a description. Meanwhile hosted API access is reported as not an export and open-source publication is excluded, which makes publishing the fast track and a private overseas install the controlled act.
The directory entry was the announcement, not the email address
Google's enterprise agent, announced 8 October, is reported to give each agent its own Workspace account — an address on an agents. subdomain, a calendar, Drive storage, a directory entry, and actions logged against a cryptographically attested agent identity. The attestation fixes the shared robot-user problem and buys attribution, not authorisation; the directory entry makes the agent a principal that every group-based share silently includes, and the mailbox makes it the first agent identity a stranger can write to without a credential.
Personal Agent Protocol draft 0.1 spends its rigour on identity — client keys, DPoP-bound tokens, an issuer that must match the discovery document — and then describes what the agent may do with two scopes plus whatever each company invents. Three access surfaces carry three credential strengths and one shared authorisation vocabulary, so "Poppy-compliant" says almost nothing about the blast radius.
Of everything Wikimedia attributed to OpenAI’s agents on 5 October 2026, exactly two actions were called potentially malicious — and both were the same move: make somebody else’s feature fetch a URL for you. Your egress allowlist is a list of other people’s fetchers, and the sanctioned bulk path existed the whole time.
GTIG reported on 30 September 2026 that exactly 50% of AI-discovered vulnerabilities yield remote code execution against 26% of everything else — but publishes no sample size, and its attribution method selects for the few vendors currently pointing agents at memory-unsafe systems code. The number worth acting on is four sections down: 782 CVEs in agent frameworks and orchestration in eight months, against 97 for frontier models.
A dropped subscription looks exactly like a quiet week
OpenAI shipped plugin automations on all plans on 29 September 2026 against MCP Events — a draft with no SEP number, in a repository whose README calls its contents exploratory. The draft gets the webhook hardening right and makes the two envelopes that report absence optional, so a revoked permission, a lost buffer and a genuinely quiet upstream all reach your agent as the same empty stream.
At DevDay on 29 September 2026 OpenAI paired always-on Dots agents — each with its own cloud computer, browser and thousands of connectors — with ChatGPT Space, where employees, ChatGPT, Codex and those agents work from one shared context. The permission model people will reason about is per-connector OAuth scope. The boundary that decides what happens is who may write into the context, and nobody is enforcing that one.
NVIDIA split agent enforcement into a kernel sandbox on the host CPU and a watchdog on a DPU the host cannot reach. The sandbox is Apache-2.0 on GitHub today; the watchdog has no ship date. The split is not a release accident — the layer far enough away to be tamper-proof is too far away to understand what the agent was trying to do.
Amazon opened the back office and closed the storefront in the same week
On 21 September Amazon cut off Meta's Muse agent; two days later it handed outside AI agents its Seller Central APIs. The variable is not the agent — it is whether a delegation exists that the platform can verify, scope and revoke, which the seller side has had for a decade and the buyer side does not have at all.
The ad brought its own agent — OpenAI split the conversation instead of the ranking
Everyone predicted a bought ranking; OpenAI bought the conversation instead, and that is the better design — for exactly as long as the two conversations stay apart. Sponsored Agents put an advertiser-operated agent behind a labelled ad slot and keep it out of the assistant's answer. But the separation is a property of the session, and what actually moves between the two lanes is claims, carried by the person, with no field anywhere saying a paid party said it first.
Four reads and one write — Google Home MCP gated the half nobody was worried about
Google blocked the thing everyone asked about: an agent connected through Home MCP cannot unlock your door. But four of the five tools are reads, and list_home_history hands a third-party agent a queryable record of motion, presence and door events over any window — with no equivalent gate, because nobody has written down what a sensitive read is. Actuation is bounded, legible and reversible. The read side is none of those.
Meta built Muse assuming the injection lands — and priced the rest at $130,000
The per-user VM is the headline and the least interesting layer. Everything load-bearing in Muse sits downstream of a successful prompt injection — brokered credentials the model never sees, a gatekeeper process the agent cannot argue with, kernel-level taint on anything that read your data — and the bounty schedule says so out loud. The residual risk is not exfiltration; it is the harmful action that travels over an approved channel to an approved destination.
CPE is a join key, not a score — NIST is putting an agent inside the NVD
NIST presented its AI agent enrichment workflow for the National Vulnerability Database on 17 September, and the open question is not whether the model is accurate. Enrichment produces three fields that fail in three incompatible ways: a wrong CVSS score gets argued about, a wrong CWE degrades analytics, and a wrong CPE returns no rows at all. One of those failures is silent, and the record format has no field in which a machine can say it was not sure.
Target selection just became free — 395 organisations, 48 countries, one operator
GreyNoise published a PaperCut campaign that ran hundreds of AI agents in parallel and reached 440 servers at 395 organisations in 48 countries, 11 of them inside the first 26 seconds. The speed is not the finding. The finding is that choosing who to attack now costs the same as choosing one — which deletes the obscurity discount every mid-size security programme has been quietly spending, and puts the least-resourced sector, education, at the front of the list with 204 victims.
WebMCP makes your page an API, and the session is the only auth it has
WebMCP lets a page hand an AI agent a list of callable tools, and Chrome is shipping it behind a flag while the W3C community group draft is still moving. The part worth arguing about is not discovery but authority: a registered tool executes as your page's own JavaScript, inside the session the logged-in user already established, so your server sees a request it cannot distinguish from a click. You are publishing an API whose only credential belongs to someone who is not the caller.
The coordinator is the requester now — and nobody scoped the grant
Cursor put Projects into beta on 10 September: a coordinator agent that plans, delegates to thousands of subagents, and — the part worth arguing about — watches a Slack channel, a schedule or all your PRs and acts without waiting for a prompt. The fan-out is the visible change; the invisible one is that a pull request now arrives with no human who asked for it. Every control the field has built assumes a request exists, and a trigger list is a standing grant with no scope, no expiry and no named principal.
The Agents API sells you the harness — compaction included
OpenAI opened the Agents API in public beta on 10 September, putting the managed Codex harness — sessions, subagent orchestration, recovery and context compaction — behind one API call, with no fee beyond tokens and containers. The compaction step is the part worth arguing about: it is the transformation that quietly rewrites what your agent is trying to do, and it now runs on a version you cannot pin, diff or roll back. Your eval numbers stop describing a system you control the moment you adopt it.
Excessive Agency climbing to third is the headline and the least useful part. The Agent Control Standard is the change: a hook contract a framework fires before a tool call, a memory write or a sub-agent, with an allow/deny/modify verdict behind any policy engine — which turns security advice into something you either implement or do not, and moves the audit boundary into your runtime. It also exposes the number nobody reports: the share of your agent’s effects that pass a hooked call site at all.
In four days three vendors shipped the same admission: nobody knows what agents are running. CrowdStrike put discovery in the endpoint sensor, AIR raised $50M for an inline firewall at the context boundary, and Tenable and OpenAI put a review in front of a registry. Each answer is complete about one place and silent everywhere else — and every governance regime you are being audited against assumes an authoritative register, not an estimate. The number to start tracking is the gap between the two.
On 4 September Docusign said its MCP server opens to every agent on 30 September — Claude, ChatGPT, Gemini, Copilot, Slack, any MCP client — governed by account-level admin controls. The law has allowed an automated agent to bind its principal since 1999, on one condition: the act must be attributable to that person. A per-account toggle attributes a class of acts, which is what carried deterministic scripts and is exactly what a model that negotiates strains. Closing that gap is the deployer’s job, and nothing in MCP does it for you.
One in ten outages is now AI. That number is not about agents.
The AI share of disclosed outages rose from 1.7% to 10.7% in three years, and agents are not in that denominator — it counts incidents published by AI companies against incidents published by anyone, so it climbs as the sector grows. The figure in the same research that is about agents: 188 of 344 verified enterprise AI incidents had no attacker at all, and the nine documented production deletions share one stage, a credential that outlived the phase it was granted for.
MHS vs SiLA 2 vs OPC UA LADS vs ROS 2: the wire format was never the problem
Lab and factory interoperability has been standardised three times already — SiLA 2 since 2019, OPC UA LADS since January 2024, ROS 2 as robotics middleware — and instruments still ship with vendor SDKs, so a fourth spec is not obviously the answer. What Anthropic's Model Hardware Standard adds is the thing none of the three tried: a device that describes its own limits in language a model can read, and a driver that enforces them whichever model is driving. Useful, and not a safety function — keep those apart.
n8n vs Dify vs Langflow vs Flowise: the licence names the moat
Flowise archived itself on 13 August 2026 and its maintainers named the reason: coding agents now handle the complexity that a rigid low-code workflow hits a wall on. The three still standing are not surviving on the canvas either — each is defending something underneath it, and each licence says exactly what. n8n forbids offering it to others, Dify forbids multi-tenant operation, Langflow forbids nothing and is owned by IBM. Read the clause before the feature list.
Enterprise Frontier Safeguards, announced 1 September 2026, resolves a real contradiction: zero data retention forbids the history that cross-session misuse detection requires. Anthropic's fix is to keep the classifier and put the corpus in your own S3, Azure Blob or GCS bucket, under your keys — with alerts routing to you and human review yours by default. That is not only a privacy upgrade. It is a transfer of duty, and the artefact it creates is a discovery-visible record of your own employees' prompts that nobody has written a retention rule for yet.
McKinsey's 2026 survey found 32% of organisations declined at least one software purchase because agentic coding tools could build it internally. That number was recorded at the cheapest possible moment — after build cost collapsed and before any run cost existed — in the same survey where AI's contribution to EBIT stayed flat.
Temporal surveyed 554 engineers in April and May 2026 and found daily agent use at 80.8%, up from 47.3% a year earlier, with 91.1% reporting improved productivity and 85.5% trusting agent output at least somewhat — alongside 41.1% hitting agent-related issues daily or more and 9.0% continuously. Both sets of numbers are probably accurate, and together they describe a failure rate nobody would accept from a database. The report reads the gap as a state-tracking problem, which is a durable-execution vendor’s reading of a durable-execution question. The more useful reading is that the error handler is a person, and no dashboard has a line for them.
Claudeforce runs in two directions, and only one keeps the record inside Salesforce
Salesforce and Anthropic announced one partnership on 26 August 2026 containing two integrations with opposite governance properties. Claude moving into Agentforce keeps the model inside a boundary that already has row-level permissions and an audit log; Salesforce moving into Claude as a plugin moves the session outside it, where the deliberation that produced a write is no longer in the system of record. Both are reasonable products. Buying them as one thing is how a company discovers the difference during its first e-discovery request.
Sharing a coding-agent session: every handoff that works throws the transcript away
Claude Code, Codex and Gemini CLI all persist sessions as append-only JSONL, so moving one to another agent looks like a file-conversion problem. It is not. An assistant turn is a claim conditioned on a system prompt, a tool schema, a model and a warm cache that the receiving agent does not have — replay it verbatim and you hand over a false memory. The one converter in the wild strips tool calls into prose on purpose, Anthropic documents its own transcript format as internal and unstable, and Claude Code refuses to resume a hand-copied transcript at all. Four transfer layers, and the useful ones all trade fidelity for something the receiver can re-verify against the repo.
The AI AGENT Act Asks for a Record Your Stack Does Not Keep
S. 5051 would require an agent acting for a person to keep real-time records, stay inside its granted authority, and never sub-delegate without explicit permission. Traces record behaviour; all three duties are about permission — which is why the bill hands NIST the job of finding a delegation protocol that does not exist.
Microsoft Priced Agent Governance Per Human. Your Fleet Has No Meter.
Agent 365 costs $15 per user per month and nothing per agent, so the one layer of your stack that exists to control fleet growth is also the only layer whose bill ignores it. Two more things do not line up: the licensing unit assumes every agent has a human sponsor, and the inventory can see far more machines than the block button can reach.
A2A Moved In With MCP. The Identity Layer Stayed Outside.
On 20 August Google moved A2A into the Agentic AI Foundation, so both protocols in the standard agent stack now share a board, a roadmap and a trademark holder. What they still do not share is a delegation primitive — and the identity work that would supply one is being stewarded at a different foundation entirely.
Skill Scanners Read a Different File Than the Agent Runs
Trail of Bits bypassed the detectors on three skill-distribution platforms in June, a July study packed 1,613 malicious skills past all eight scanners tested, and on 17 August OWASP gave poor scanning its own entry in the first Agentic Skills Top 10. The scanner inspects a file at rest; the agent constructs a program from it at run time — and the attacker picks where the two disagree.
Slack Code puts the approval in a channel — name one approver anyway
Slack shipped the review surface, not the agent: five partner coding agents you buy separately, working inside a channel with a plan tab, a diff tab and a live preview, and a human approval before anything ships. That is the right bottleneck to build for — and a shared approval is the one thing a terminal got right that a channel does not.
MCP Registry vs Smithery vs Docker MCP Catalog vs PulseMCP: four indexes, one missing signal
You can look an MCP server up in four places and get four different kinds of answer: who owns the name, who will host it, who built the image, and what exists at all. Only one of them makes a claim about the artefact you are about to run — and none of them has read the tool descriptions, which is where an MCP server actually attacks you.
The 2026-07-28 MCP spec deleted the initialize handshake and the session-id header, so a server can now run behind a plain round-robin load balancer. That operational win is real — but statelessness is a transport property, not a system property. The session did not disappear; its bookkeeping moved onto every request, and the durability that long-running agents actually need came back in through the AWS-contributed Tasks extension as explicit handles. Read the two together before you celebrate a simpler protocol.
A payments company paid a reported $7 billion for the layer that counts AI usage, seven months after buying the layer that invoices it. Routing was never the scarce asset — the scarce asset is one normalised record of what every model call cost and who it was for, and if that record lives in your request path you are paying a percentage on every step your agents take.
August’s Worst Agent CVEs Were Authorization Bugs, and There Was No Patch to Apply
Two agent vulnerabilities scored above 9.0 this month and neither involved a language model. CVE-2026-62830 hit 9.9 because a missing authorization check let a low-privileged caller ride Azure SRE Agent’s managed identity — and the fix shipped service-side, so the only lever you ever held was the grant you made months earlier.
GPT-5.6-Cyber Is Gated Because It Refuses Less, Not Because It Knows More
OpenAI's offensive-security model loses to plain GPT-5.6 Sol on both evaluations that score the work product, and wins the one that scores whether it answers at all. Daybreak Red gates a refusal policy, not a capability — which makes patch latency, not model access, the number that should have moved on 10 August.
x402 vs AP2 vs ACP vs MPP: The Only Difference That Changes Your Risk
Four agent-payment standards, usually compared on rails. The axis that matters is where the spending cap is stored — a pre-funded wallet, an issuer rule, a one-checkout token, or a mandate the user signed — because that fixes how much a prompt-injected agent can spend before anything else gets a vote.
Generative UI Has Two Standards, and They Split Over Who Owns the Catalog
A2UI sends JSON and MCP Apps sends sandboxed HTML — the least consequential difference between them. One has the agent compose components you own, moving the review into your design system; the other installs an interface someone else wrote, moving it to the server boundary. Sort your surfaces by whether you can enumerate them, then pick.
Half of Enterprises Scaled Back Their Agents. Seven Percent Can Compute the Ratio.
KPMG found 49% of leaders scaled back an agent deployment over cost and 7% report established ROI — so nine in ten of the organisations that cut did it without a denominator. Cost is metered by a vendor that needs to bill you; value stays at zero until someone builds it. The measurement you cannot add later is the pre-agent baseline.
AgentCore vs Foundry vs Vertex AI Agent Engine vs Cloudflare Agents: Nobody Is Selling You the Loop
Two of the four bill the agent loop at about nine cents per vCPU-hour and their prices are 3.6% apart; the other two do not charge for it at all. What each is actually selling is a place to keep the conversation — and AWS closing Bedrock Agents Classic to new customers on 30 July 2026 is the clearest evidence yet about which half of a managed runtime you can afford to rent.
Agent Plugins 1.0 Standardises the Bundle and Leaves Trust to Whoever Installs It
Five rival vendors agreed on a directory layout on 6 August, and explicitly declined to agree on install, distribution, permissions, sandboxing or provenance. The format makes one bundle of instructions plus credentialed tool access portable across six clients — which is exactly why the compensating controls are now yours.
DeepSeek Is Building a Harness, and the Benchmark Score Already Includes the Scaffold
DeepSeek reported a DeepSWE result produced by a harness it had not released, and 712 open-source projects signed up for the beta in three days. Agentic scores stopped being model measurements some time ago — read every published number as a model-and-harness pair, and compare models by holding your own harness fixed.
Google's Agent Calls the Store, and Every Protocol Guarantee Falls Off
Google's shopping agent now phones local shops to check stock — a channel that carries none of the signed identity, scoped authorisation, replay protection or verifiable receipts that AP2 and its rivals were built to provide. The phone is not a stopgap on the way to universal protocol adoption; it is the permanent floor of agent commerce, covering the merchant tail that will never implement an API, and it has no trust primitives at all.
Agent Security Just Picked a Layer, and It Is the One You Own
NVIDIA and the Linux Foundation launched the Open Secure AI Alliance on 27 July 2026 with 37 founding members and without OpenAI, Google, Anthropic or Meta. The published scope — identity, isolation, guardrails, logs, model formats, scanning, the agent harness — is entirely runtime infrastructure, which means the standards coming out of it are things you implement rather than things a model vendor ships you.
Atlas Shuts Down on 9 August. Agentic Browsing Just Split Into Three.
OpenAI is retiring the ChatGPT Atlas browser nine months after launch and moving its capabilities into a Chrome extension, an in-app browser and a server-side cloud browser. That is not a retreat from agentic browsing — it is the admission that a browser agent never needed a browser. What it needed was proximity to an authenticated session, and the three replacement surfaces are three different answers to whose session it borrows.
The 28 July specification retires the initialize handshake and the Mcp-Session-Id header, and every write-up so far has framed that as plumbing. It is not. Dropping the held-open connection forced Sampling, Roots and Logging onto a twelve-month deprecation clock — and those were the features that made an MCP client a peer rather than a caller. The protocol just settled what it is.
MCP at 97 Million Downloads: How the Model Context Protocol Won — and What's Still Broken at Scale
Two years from Anthropic's launch, MCP isn't a debate — it's a dependency. Every frontier vendor, every major IDE, and one Pinterest team saving 7,000 engineering hours a month all ship against it. The interesting question is no longer *should you use MCP* — it's what fails at this scale and how the 2026 roadmap plans to fix it.