Trend Shift

Coding Wins Move to the Tool Shell

Multiple sources indicate that coding-agent performance increasingly depends on the harness, context management, and workflow.

Competition in coding agents is shifting from “which model is stronger” to “which tool shell organizes the model better.” Several signals today point in the same direction: the same model can perform very differently across harnesses, while development workflow, context isolation, and agent orchestration are becoming decisive variables.

Benchmarks put the harness in the foreground

Tomasz Tunguz cited Endor Labs Agent Security League results showing GPT-5.5 at 61.5% functional correctness in Codex and 87.2% in Cursor; Claude Opus 4.7 reached 87.2% in Claude Code and 91.1% in Cursor. He also noted that input tokens account for 86% to 98% of OpenRouter traffic, meaning harnesses influence most of the bill through caching discipline.

Workflow, context, and products reinforce the point

GitHub AI & ML published “harness is all you need mostly,” emphasizing a GitHub Copilot process for prototyping, planning, implementation, and review rather than chasing every new tool. Martin Fowler relayed Rahul Garg’s view that the real value of sub-agents is keeping information out of the orchestrator’s context and protecting working memory. Product Hunt’s Task Monki places coding agents inside a full development workflow, showing that the market is also productizing the process layer.

Differentiation shifts after model commoditization

At the factual level, multiple sources are focusing on the execution layer beyond the model: benchmarks, Copilot workflow, sub-agent context, and full-process development tools. The editorial inference is that as model capability gaps narrow, the harness may become a defensible user entry point. It may also change cost structure, because input tokens and caching strategy directly affect usage bills.

What to watch next

Watch whether major IDEs and code platforms publish more same-model cross-harness evaluations, and whether enterprises add cache-hit rates, context isolation, and review workflows to coding-agent procurement criteria.

Sources