Agent evaluation reaches ambiguous projects as reliability moves into the harness
After several days centered on executable feedback inside coding loops, today’s evidence broadens the control surface.
Topic summary
Coding Agents
Evaluation and review controls for ambiguous agent work
Agent evaluations can test reliability more precisely by locating clarification, formal verification, and specialist review at the decisions where errors become expensive to reverse.
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.
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…
Structured context and execution feedback cut coding-agent waste
The recent emphasis on controls around coding agents continues, but the strongest evidence now targets work inside the loop.
Repository-aware editing, recovery, and evaluation for coding agents
Coding-agent controls can move closer to the semantics of the work: requirement links can constrain cross-file edits, invariant violations can improve recovery decisions, and controlled code transformations can reveal…
Coding-agent output is being trimmed and checked before merge
Recent work on controls around coding agents continues, but today’s evidence concentrates on the artifacts agents leave behind.
Verification-aware cleanup of coding-agent work
Coding-agent cleanup should preserve the evidence needed to merge a change, not merely its passing status. The most useful changes are to make patch minimization coverage-aware, protect explicit obligations during…
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.
Agent controls are settling into everyday workflow surfaces
Recent momentum around engineered agent controls continues, but today’s evidence moves those controls into ordinary development and deployment interfaces.
Privacy controls for persistent, tool-using agent workflows
Pre-model PII handling does not cover every place an agent can retain or act on sensitive data. Repository traces, persistent memory, and connected applications need separate checks, while transformed identities should…