Google's own ChromeDevTools/chrome-devtools-mcp (50k stars) lets coding agents drive a real Chrome instance for performance profiling and debugging; abhigyanpatwari/GitNexus replaces 'guessing at code by reading it' with a pure browser-side knowledge graph; mksglu/context-mode targets coding agents' context-window waste; google/skills is Google's own official Agent Skills package library; livekit/agents keeps shipping actively for voice agents. On the framework side, pydantic-ai v2.36.0 adds `@durable_operation`, opening a pluggable slot for third-party durable-execution engines.
Three papers today strike at the capability boundaries of AI coding agents from three angles: **ICAE-Bench** tackles interactive development under ambiguous requirements, exposing how current benchmarks lag behind the vibe-coding era; **EvoAgentBench** reveals the pitfalls of agent self-evolution ability transfer, where a mainstream method causes a −12.3 point negative transfer; **PERFOPT-Bench** opens the new track of performance optimization as an agentic task and finds that framework choice often matters more than model choice. The takeaway: production agent evaluation is far harder than existing tools suggest, and the field urgently needs benchmarks closer to real-world scenarios.
Today's common theme: **the way we evaluate agents is itself broken**. The first paper audits major tool-calling benchmarks and finds nearly 20% of scores are wrong; the second uses replay analysis to show which benchmarks can be stopped early for reliable conclusions (SWE-bench is the exception); the third introduces the first multimodal web agent benchmark that jointly evaluates task completion and guide generation — screenshot input, dual-objective scoring, and even the strongest models complete less than 40%. Read all three for a complete picture of the crisis in agent evaluation and where to go from here.
Three papers tackle AI Agent platforms from practical angles: the first exposes stealthy security threats in multi-agent systems and proposes activation-space detection of malicious agents (F1 +0.55 over graph methods in async settings); the second improves coding agent retrieval by introducing procedural similarity — finding code with similar solution steps rather than surface resemblance; the third is a wake-up call: the same LLM in different harnesses produces significantly divergent mid-task judgments, meaning harness design is never neutral.
Three papers today attack the same core question from different angles: **how to make agent workflows truly reliable in production**. Mnemosyne brings the database Transaction concept into agent workflows, requiring every LLM output to pass admission control before taking effect. PaperPilot shows how to train a 9B model to plan multi-turn search workflows as DAGs and dynamically revise them based on user feedback. SEA lets agents self-improve on the fly while issuing auditable safety certificates. Together, the three papers nearly cover the full reliability stack for agent systems: execution-layer protection, training-layer workflow learning, and update-layer safe evolution.
Three papers converge on one core question: **how do we actually evaluate whether an agent is good enough?** SWE-Explore isolates the most overlooked middle step of coding agents — understanding the codebase — and benchmarks it independently; Claw-SWE-Bench reveals that harness design (the adapter) is the real lever behind coding agent score jumps, with the same model leaping from 19% to 73% by swapping adapters; Red Queen Gödel Machine (Cambridge × NVIDIA) goes further by co-evolving the evaluator alongside the agent, breaking the ceiling of static benchmarks. Read together: **evaluation infrastructure is becoming the most critical competitive moat for agent platforms**.
Three papers dissect the challenges of making agents production-grade infrastructure: Agent libOS addresses what an agent runtime should look like underneath; Autodata (Meta FAIR) shows how agents can manufacture and continuously improve their own training data; GAIE proposes tiered oversight for coding agents under regulatory constraints. Together, they sketch a complete blueprint showing that agent platforms need redesign across architecture, data, and governance.
Three papers, three angles on agent platforms: AgentFugue demonstrates that peer agents sharing a reasoning scratchpad can break through long-task collaboration bottlenecks; Can Agent Benchmarks Support Their Scores? reveals systematic flaws in current agent benchmark scoring mechanisms, urging us to re-examine leaderboard numbers; VibeServe lets agents auto-generate complete LLM serving stacks that outperform hand-tuned vLLM in niche deployment scenarios while matching it in standard ones. Together they answer: how can agents collaborate better, can we trust the evaluation numbers we rely on, and can agents build infrastructure for engineers?