Automated code repair is not a single action but a sequence of decisions. Each choice an agent makes — where to look, what to change, when to stop — steers the repair trajectory and directly affects how many tokens the next model request will consume. A new paper on arXiv, JevCoder, frames this as a cost-management problem: not every decision needs the same level of reasoning.

The paper asks which repair decisions can be delegated to a low-cost model. The abstract notes that these decisions shape repair trajectories and influence the token cost of successive requests, suggesting that some choices are cheap to automate while others may be too consequential to offload.

The central tradeoff is economic: delegating a decision may save tokens, but if it leads to a poor repair step, the agent may need extra requests to recover. JevCoder appears to target exactly this balance, though the abstract does not yet reveal the full results or the conditions under which delegation wins.

For teams building coding agents, the work points to a practical design question: rather than treating every repair step as equally expensive, an agent could route only high-stakes decisions to a powerful model and leave routine choices to a cheaper one.