Model APIs ate the coding harness — own policies, memories and evals instead

rseroter · x · 2026-11-20

Model APIs have absorbed most coding-harness behavior — thinking state, implicit caching, structured outputs, server-side state, hosted loops and sandboxes — while open specs (AGENTS.md, SKILL.md, MCP) standardized the outer contract across Claude Code, Codex and Antigravity. Swapping harnesses is now near-zero cost, so teams debating frameworks miss the point. What you should still own: policies (sandboxes, approvals, caps), code (repos, worktrees), memories (rules, skills, repo context) and evaluation (stop hooks, log audits). Understanding and influencing model behavior is where engineering value lives.

Original post →

More from coding & agent

coding & agent channel →