The day’s strongest work treats coding agents as long-running systems that need session-level evaluation. SWE-Together, SWE-INTERACT, and MirrorCode make user feedback, full-program behavior, and compute budget visible…
Coding-agent teams can now add session-level checks to release and operations work: multi-turn tests that count user corrections, serving dashboards that show repeated prefix reads, and MCP gateways that block unsafe…
The day’s research treats AI coding agents as systems that need runtime evidence, meaningful tests, and harness-aware scoring.
Agent-authored code needs quality gates that inspect what tests assert, repair loops that pass targeted execution evidence back to the model, and evaluation reports that separate model, harness, environment, verifier…