Capital & Compute

Coding agents

The model matters. The harness around it usually matters more: how an agent reads a repository, what it retries, how much context it wastes, and where the loop stops. Two teams running the same model see cost and success rates diverge by multiples once the scaffolding and workflow differ.

In this world
58 analyses
Field tool
Map the agent landscape ↗

Keep diving.

The featured guide stays above; the stream below moves as new analysis is published.

What this topic covers

Guides to AI coding agents, harness engineering, workflows, editors and the economics around them.

This topic collects 58 analyses, and they are written to be read together rather than one at a time: the featured guide sets out the shape of the problem, and the pieces below work through the individual numbers, tradeoffs and edge cases behind it. Every figure is attributed to a primary source at the point it is used and carries the date it was verified, because prices and benchmark results in this area go stale in weeks rather than years. Where a number is modeled rather than measured, the assumptions are stated so the arithmetic can be checked.

The topics on this site overlap by design. This one runs into AI costs and Models & benchmarks, and a question that starts in one usually ends in another: a pricing decision turns into a hardware decision, a benchmark result turns into a cost question. Follow the links inside the posts rather than treating these archives as separate shelves.

Map the agent landscapeRank agents by cost per taskBrowse skills, MCP servers and prompts