Loading the edition…
· Past edition · 11 stories
Retrospective edition reconstructed from later captures. Paper versions may include later updates; coverage labels describe the evidence used.
Agent frameworks & orchestration
An agent’s own finish signal is not enough: the harness needs an independent gate, bounded repair, and a spend ceiling enforced during each attempt.
Why it matters: For harness designers, the key distinction is enforcement: a declared limit or trusted discipline is not enough unless the harness checks the gate and enforces the ceiling inside an attempt.
Agent frameworks & orchestration
Open each story in the reader. Summaries are shown when available; some sources provide an abstract only. With an account you can keep your own notes.
The article describes a production-agent stack: tools operate software, skills supply task-specific expertise, and files carry documents and outputs through the workflow.
Why it matters: The division of work makes it possible to combine software interaction, reusable team procedures, and document handling in one agent workflow, while multi-action turns can reduce the number of model calls.
Agent frameworks & orchestration
Thinkingbox tests whether agents can reliably produce the right persistent business state—not merely make one plausible response or valid tool call.
Why it matters: A successful run, clean tool call, or plausible response is not enough to establish reliable completion. Evaluating terminal state and unintended effects can reveal failures that surface-level signals miss.
Agent frameworks & orchestration
A trace study examines how coding agents use documentation.
Why it matters: Observed agent behavior can guide which documentation is maintained.
Agent frameworks & orchestration
A benchmark studies when relevant memories mislead agents.
Why it matters: Remembered context can influence reasoning even when it is faithfully retrieved.