The strongest work this day treats agentic coding as a controlled workflow: formal specs need faithfulness filters, test repair needs executable artifacts, and coding assistants need local context with safety gates.
Generated-code workflows should add executable checks at the point where an agent claims completion: formal-spec assistants need faithfulness and clarification gates, test agents need coverage and assertion-preservation…
Executable evaluation remains the baseline for this period. The strongest claims come from model-external pieces: SWE-Edit’s read/write split, Agentic Harness Engineering’s rollout-driven harness edits, and SAFEdit’s…
The concrete openings are in the code-editing path around the model: narrower read results, dedicated patch execution, test-backed repair loops, versioned harness changes, and ranked reports from uncovered code.
This period’s strongest work tightens the link between generation and executable evidence. KISS Sorcar, AgentEval, and ClawMark all score systems on what they can finish, trace, or survive in live workflows.
Executable evidence is moving into everyday engineering workflows. The clearest openings here are agent CI that points to the failing step, requirements-grounded test generation for business logic, and profiler-guided…
The clearest work on this day makes software agents easier to score, easier to rerun, and easier to block when they fail checks.
The most actionable work here pushes software agents into loops with hard execution checks. The clearest near-term builds are a repository repair worker that edits tests alongside code, a compiled workflow tool for…
Today’s research is strongest where software work can be checked by execution. The main emphasis is stricter evaluation for coding agents, plus better test generation for code and APIs.
Production-facing software-agent work is getting concrete in three places: private replay benchmarks for coding agents, deterministic testing for tool-call failure and recovery, and requirement-driven API test…