Executable feedback is outperforming prompt-only coding workflows
The recent run of work on coding-agent controls continues, but today’s evidence makes the control signals more task-specific.
Topic summary
Repository Context
Executable controls for code optimization and generated tests
Performance and test-generation workflows can make model output more dependable by combining complementary executable signals: runtime profiles to prioritize static optimization matches, semantic mutations to challenge…
Coding-agent controls gained precision through targeted context and executable evidence
This week strengthens the three-week run of evidence that coding-agent performance depends on the system around the model.
Coding-agent controls tied to verification failures and harness changes
Repository exploration can be deferred until verification identifies a concrete knowledge gap, reducing unnecessary context while preserving a path to deeper repair.
Coding-agent gains now come from engineered context and executable checks
The strongest daily signal continues the recent focus on controlled agent workflows, now with better measured evidence. ACQUIRE improves issue resolution by answering repository questions before editing.
Repository context checks for coding-agent workflows
Repository context should be tested as an operational dependency. The practical changes are fault injection for retrieval, security-specific context gates before code completion, and explicit escalation when…
Coding agents are being judged as controlled production software
This week’s research treats large language model (LLM) agents as production software. The strongest work ties task success to context recovery, artifact delivery, cost accounting, permission boundaries, and credential…
Coding Agent Release Gates
Coding-agent work is moving into the same review path as other production software: repository context has to be measured, agent configs need ownership and permission checks, and evaluation needs to cover follow-up…
Full operating loops define agentic coding evaluation
The day’s strongest signal is operational evaluation for coding agents. Papers test feedback rounds, harness repair, stateful memory, and repository knowledge under deployment-like conditions.
Coding Agent Feedback Loops
Coding-agent evaluation is becoming more useful when it records the whole operating loop: the request, the trace, the feedback, the harness change, and the next attempt.
Coding agents are being tested as controlled executions
Current emphasis: coding agents are judged by how they run, repair, and stay inside bounds. A-ProS shows gains from stateful judge feedback. ProcBench scores process defects inside traces.
Coding agent execution controls
Coding-agent teams can test runtime scope, trace quality, and file selection as separate parts of the execution path.