This Week in Extensibility: MCP trims to a stateless core, extensions weigh softer permission prompts, ChatGPT adds plugin governance

2026-07-03T00:00:00-04:00

Welcome to This Week in Extensibility, a weekly read on the meta layer of software extensibility: the infrastructure that decides what end users and customers can customize, automate, and modify in the software they already use. Plugin platforms, sandboxes for untrusted code, agentic-web actuation, and the policies that govern plugin ecosystems. Not individual plugins, and not generic AI tooling.

The connective standards for agent-driven software carried the week. MCP put out beta SDKs for a leaner, stateless next specification, and WebMCP moved a step closer to a formal standards venue over a browser vendor's objection, while the extension platform's community group took up a proposal to make permission prompts less disruptive.

Protocols: the agent-to-app standards advance on two fronts

MCP published beta SDKs for its next specification. On June 29, the project released betas across all four reference SDKs (Python, TypeScript, Go, and C#) implementing the 2026-07-28 protocol. The headline change is a stateless core: the spec drops the initialize handshake and protocol-level session management, so any server instance can handle any request and a remote server can scale behind a plain round-robin load balancer without sticky sessions. A second addition, Multi Round-Trip Requests, lets a tool ask the user a question mid-execution and have the client retry with the answer, rather than holding open a long-lived stream. The specification is a release candidate scheduled to launch July 28, not final.

WebMCP's community group resolved to open formal wide review. At its June 25 teleconference, the W3C Web Machine Learning Community Group adopted a resolution to "initiate wide review of WebMCP with the TAG, Privacy WG and Security IG," the procedural step that precedes any transition to a chartered Working Group. That follows last week's open question about whether to formalize the protocol at all. The venue remains contested: WebKit's standards position is still "oppose", and per the minutes Apple has suggested moving away from the current group structure. Design work continued alongside, including a new issue flagging an HTML-injection-to-agent-hijacking escalation path in the declarative tool API.

Why it matters: both protocols for letting agents drive the apps a person uses moved this week, MCP toward a cheaper hosting model and a way to pause for human input mid-run, and WebMCP toward a formal standards venue. Read the status qualifiers: MCP's spec is a release candidate, not shipped, and WebMCP is an early Community Group draft with one browser vendor on record to oppose.

Standards: WebExtensions weighs softer permission prompts

The WebExtensions Community Group took up deferrable_permissions. Per the July 2 minutes (still in an open pull request), Benjamin Bruneau proposed the mechanism as a middle ground between two existing approaches: treat added permissions as optional on update but required on a fresh install, so an extension can request new capabilities without alarming or disabling its existing users. Apple leaned toward the defer approach, Google wanted more async discussion first, and Mozilla raised how Firefox's update deferral would interact with it. The same meeting discussed making userScripts.register overwrite by default and an unresolved split over storage limits.

Why it matters: the permission prompt is the main checkpoint between an extension gaining a capability and the user allowing it, and today it shapes how developers build. To avoid the update prompt that can force users to manually re-enable an extension, developers either hold back features that would need new permissions, or over-request permissions on a fresh install so they never have to ask again. A softer update path removes that pressure, though it also changes how quietly an already-installed extension can expand what it does, so it cuts both ways for user control. This is proposal-stage, with no vendor commitment yet.

Governance: ChatGPT gives workspace admins a plugin control plane

OpenAI added a plugin management surface to ChatGPT Business. Per OpenAI's ChatGPT Business release notes dated June 26, workspace admins can now manage plugins from Workspace settings, with discovery and governance in one place: search and filters by status, installation policy, roles, and category. Admins can set whether a plugin is member-installable or installed workspace-wide by default, and see which apps each plugin uses.

Why it matters: as an AI assistant's plugin catalog grows, the governing question shifts from what a plugin can do to who inside an organization is allowed to install it. This is the admin control plane for that decision, the same shape of policy layer that enterprise app marketplaces have long had.

Also worth knowing

Wasmer shipped experimental interruptible Wasm execution on June 30, a way to interrupt running guest code in an embeddable engine used to run plugins. The same release also removed two backends and dropped x86-64 macOS, so it narrows as well as adds.

Daytona moved its open-source sandbox repo into maintenance in late June, with a notice that core development has moved to a private codebase and the public repository will get no further updates. It is a small market-map shift among the vendors selling isolation for customer and agent-generated code (E2B, Modal, Cloudflare Sandboxes, Fly Machines).

Webhook and event standards (Standard Webhooks, CloudEvents, AsyncAPI) and URL-scheme registries were quiet again, only routine maintenance plus one provisional IANA registration, the PURL pkg: scheme, which identifies software packages rather than actuating software.

On the radar

July 12–14: Local-First Conf 2026, Berlin, theme "user empowerment in an age of fluid software."
July 16: Next W3C WebExtensions Community Group meeting.
July 23: Next W3C WebExtensions Working Group meeting.
July 28: Target launch date for the MCP 2026-07-28 specification; the release candidate and beta SDKs are already out.