I build agents that do the work, then write about what breaks.

Agent Plugins 1.0.0 is an open, vendor-neutral standard for packaging AI agent plugins, released 6 August 2026 and governed by a Technical Steering Committee with Core Maintainers from Amazon, Cursor, Microsoft, OpenAI and Vercel. A plugin is a directory with plugin.json, a skills/ folder in Agent Skills format, and an mcp.json describing MCP servers. This explains what the spec requires, how its governance charter enforces vendor neutrality, how it differs from MCP and Agent Skills, and what adopting it on day one cost me across a 13-skill library of testing skills for agents and a 33-skill second brain.

When Opus 5 shipped I changed the model string and moved on, like everyone does. Then I noticed my harness was fighting the model. Model upgrades do not just raise capability, they reverse direction on specific behaviors, and every workaround you wrote for the old behavior becomes a bug. This is the audit: 91 skills, 33 commands, six changes, 1,500 lines deleted, and three real defects I only found because I finally reread the files.

Claude Code and the Codex CLI can't see or touch the screen; only OpenAI's Codex desktop app has computer use. So I pointed my coding agent at the desktop app, had it reverse-engineer how the feature works (the @oai/sky helper, a unix socket, a JSON-RPC protocol), and rebuild it from scratch on public macOS APIs as computer-harness. This is what it found and what it built, dead-ends included.

Why I forked localterm into TermDeck: a self-hosted browser workspace for agent-heavy terminal work. Live grid of sessions, clickable file paths, tweak mode that sends CSS selectors back to the agent, a markdown wiki, and a tldraw canvas.