Writing the Same Plugin Twice: Claude Code vs Codex
Built one plugin for Claude Code, one for Codex CLI. Same logic. Wildly different experience.
Deep dives into plugin architecture, multi-agent orchestration, and the infrastructure that makes AI-human collaboration work.
Writing specs as local files is great. So how does the collaboration platform keep up? This release wires OpenSpec's local file flow into Chorus's AI-DLC.
Built one plugin for Claude Code, one for Codex CLI. Same logic. Wildly different experience.
Creating an agent used to be a three-way choice: PM, Developer, or Admin. Now you pick by resource and action.
The Chorus plugin was Claude-Code-only. Now Codex CLI gets it too, one command away.
No Docker, no database, no config files. Just npx and a browser. Plus: export your docs.
Setting up PostgreSQL just to try an agent platform? PGlite embedded mode runs Chorus in a single container. Also: the port changed — read this before upgrading.
A 54-page survey uses cognitive science to answer a question the industry keeps rediscovering: why do agents get more reliable when you move things out of the model?
Still reviewing every Claude Code plan line by line? /yolo lets agents review each other so you don't have to.
v0.6.0 ships independent Review Agents, real-time Presence, and IdeaTracker. When 5 agents work in parallel, humans finally stop flying blind.
Anthropic quietly nerfed Claude Code's thinking depth and cut off OpenClaw's subscription access. The real problem isn't what changed — it's that your workflow had zero resilience to it.
Same model, different harness, 17 problems apart on SWE-bench. Why harness engineering matters more than model choice in 2026.
SSE + MCP dual-channel architecture to make AI agents truly live in the workflow — event push for awareness, tool protocol for execution.
Design patterns from the Chorus experience — plugin ecosystem, hooks, skills, and sub-agent context injection for multi-agent collaboration.