Skip to content
Oday Bakkour
Back to Knowledge Hub

AI Coding News: August 13, 2026 — Agent Plugins 1.0 Goes Cross-Vendor, Claude Code Hits 2.1.229

Oday Bakkour profile photo
Oday Bakkour
5 min read
Share
AI Coding News: August 13, 2026 — Agent Plugins 1.0 Goes Cross-Vendor, Claude Code Hits 2.1.229

The biggest AI coding story this week isn't a single tool's changelog — it's that six companies who normally compete on agent tooling just agreed on how agent plugins should be packaged. AWS, Cursor-maker Anysphere, GitHub, Microsoft, OpenAI, and Vercel published Agent Plugins 1.0 on August 6, with Google joining as a core maintainer the same day. On August 12, GitHub shipped support for it across VS Code, Copilot CLI, the Copilot SDK, and the Copilot app. Separately, Claude Code moved to version 2.1.229, adding self-hosted runner hooks and closing a gap where /commit-push-pr could auto-approve dangerous git flags.

Agent Plugins 1.0: the packaging standard nobody expected five vendors to agree on

Until now, if you built a skill or an MCP server bundle for Claude Code, you generally had to repackage it to make it work in Cursor, Copilot, or Codex — each client expected its own manifest layout and directory conventions. Agent Plugins 1.0 fixes that at the packaging layer, not the protocol layer: it defines a minimal, vendor-neutral directory format (a plugin.json manifest, a skills/ folder, and an optional mcp.json) that any compatible client can install and discover the same way.

Vercel initiated the proposal; AWS, Anysphere, GitHub, Microsoft, and OpenAI refined it into a 1.0 spec with a public Technical Steering Committee. Google announced on August 6 that it's joining as a core maintainer and wiring support into its own Agents CLI and Data Agent Kit. The spec, JSON Schemas, and implementer guides are published at agent-plugins.org under an open license.

This connects directly to something we covered yesterday: OpenAI's Codex CLI 0.147.0 (August 7) introduced "portable Agent Plugins" searchable across local, personal, workspace, and remote catalogs — that's the same standard, shipped by one of its own steering committee members days after the spec went public.

GitHub Copilot ships Agent Plugins 1.0 support (August 12)

GitHub's rollout is now generally available across every Copilot subscription plan, and it lands in four surfaces at once:

  • VS Code, Copilot CLI, the Copilot SDK, and the Copilot app can all install and discover plugins from the Awesome Copilot marketplace by default.
  • Existing GitHub Copilot plugins keep working with no migration required — backward compatibility was a design requirement, not an afterthought.
  • Plugin authors who want to adopt the shared format mainly need manifest changes: add a $schema reference, move skills under a skills/ folder, store MCP configuration in mcp.json, and namespace any Copilot-specific extras under com.github.copilot/.
  • Enterprises get plugin governance through the existing managed-settings.json file — controlling which marketplaces are approved and which MCP servers are allow-listed applies across every compatible client, not just Copilot.

Claude Code 2.1.229: self-hosted runner hooks, a safer /commit-push-pr, and a PR-review fix

Anthropic shipped 2.1.229 on August 12, one day after 2.1.228's reliability pass. The two most consequential changes are easy to miss in a long fix list:

  • /commit-push-pr no longer auto-approves dangerous git flags. If your team scripted around the old behavior assuming risky flags would sail through, that automation now needs an explicit approval step.
  • The Claude Code Review GitHub Action was silently failing to post reviews on PRs — fixed. If you rely on it for automated review coverage, worth spot-checking that reviews are landing again.
  • Self-hosted runner sessions can now use server-supplied Claude Code hooks, and self-hosted runners on Windows must now pass an explicit --base-dir at startup rather than inferring one.
  • Plugin marketplaces gained "command" sources with dynamic resolution, and gateway streaming responses now get SSE keepalive pings during long thinking pauses, which should reduce spurious timeouts on slow connections.
  • Other fixes address real annoyances: long responses partly disappearing mid-stream, crashes on non-string tool-call arguments, a RangeError crash in narrow terminal windows, self-hosted runners failing to start with managed MCP servers, and file-watcher handle leaks after atomic file replacements.

On the VS Code extension, the /btw side-question panel is now resizable, and the sidebar gained session groups with right-click management for people juggling several concurrent sessions.

Elsewhere: a quiet day

OpenCode's last release remains v1.18.16 from August 10, and Cursor's most recent update is the July 22 Cursor Router launch (Auto mode now routes each request to an Intelligence, Balance, or Cost-optimized model) followed by Google Workspace plugin support on August 3 — nothing dated since. Codex CLI hasn't shipped past 0.147.0. Worth noting for anyone tracking the pace: after several days of near-daily releases across the board, this is the quietest stretch of August so far outside the Agent Plugins news.

What this means if you build or use agent plugins

  1. If you maintain a skill or MCP-server bundle for one client, check agent-plugins.org before you build a second client-specific version — the manifest changes needed to go cross-client are small (a $schema reference, a skills/ folder, an mcp.json).
  2. If your CI scripts call /commit-push-pr in Claude Code expecting risky git flags to auto-approve, update to 2.1.229's behavior explicitly rather than relying on the old default.
  3. If you use the Claude Code Review GitHub Action, confirm reviews are posting again on a recent PR — the prior bug failed silently.
  4. If you run Claude Code self-hosted runners on Windows, add --base-dir to your startup command before upgrading, or the runner won't start.
  5. If you manage enterprise Copilot deployments, review managed-settings.json now — plugin marketplace and MCP allow-lists set there apply across the newly unified Agent Plugins surface.

Sources & further reading

Add Oday Bakkour as a preferred source on Google

Comments

Share your thoughts and join the conversation

Leave a Comment

Loading comments...
RELATED