2026-09-17

AI Agents

A serving-systems paper argues agents shouldn't guess how long a tool call will run — the running tool already knows, and reporting its progress cuts p90 time-to-first-token after a call by ~20% versus LRU eviction. Alongside it: a measurement of how much the coding-agent harness alone moves benchmark scores, a paper on running workflow portfolios under compute cost, and an open-source browser agent with an indexed action space.

2 papers 2 news 0 blogs 30 appendix 501 considered

Papers

2

Ask the Tool, Don't Guess: Agent Tool Calls Hold Their Progress, and the Serving System Should Read It

arxiv:arxiv-agents — Yipeng Liu, Yingqiang Zhang, Feifei Li, Huanchen Zhang 8/10 infracost-latencytool-use
The insight is sharp: agentic requests idle for wall-clock time during tool calls while their KV cache pins GPU memory, and serving systems decide eviction by guessing call duration from name, history, or declared timeouts. The paper shows no pre-call estimate can rank durations — but the running tool already holds the answer. A harness that surfaces per-call progress recovers a readable signal across four public corpora at no benchmark cost, cutting p90 TTFT after a tool call by ~20.7% against LRU, near oracle.

Designing Agentic AI Workflow Portfolios under Imperfect Selection and Compute Cost

arxiv:arxiv-agents — Mojtaba Abdolmaleki, Stefanus Jasin, Boyu Wang 8/10 safetytool-use
Formalizes the run-many-workflows-then-select pattern as a portfolio problem: extra executions can catch answers the single best workflow misses, but they burn compute and introduce plausible distractors that degrade final selection. The authors summarize selector quality through an odds-lift index, derive bounds on the value of variety, and give LP relaxations plus a pricing-oracle method for large workflow classes. Evaluated on ABCD, Schema-Guided Dialogue, and HotpotQA; the abstract is truncated before the empirical results, so weigh the theory over the numbers.

News

2

HarnessTax: How Much Does the Harness Matter for Coding Agents?

hn:hn-agent — matt_d 7/10 code-agentsevals
A direct measurement of how much scaffolding — not the model — drives coding-agent performance. This is the practical companion to yesterday's SWE-bench convergence audit, which showed scores swinging up to 29.8 points on scaffold choice alone. The HN thread is active (136 points, 55 comments) but the linked artifact is what matters: it quantifies the harness tax rather than treating scaffold as a footnote to the model name.

Jev Ultrafast: A browser agent with a dynamic, indexed action space

hn:hn-agent — rahimnathwani 6/10 tool-useframeworks
An open-source browser agent built around a dynamic, indexed action space rather than the usual flat DOM-to-action mapping. The framing suggests the index is rebuilt per page state, which could cut the token cost of describing available actions to the model on large pages. HN discussion is thin (65 points, 4 comments), so treat the performance claims as unverified until someone runs it against a browser-agent baseline.
30 more items the ranker flagged but didn't feature

Papers

Blogs