An Agent’s Answer Begins in the Harness
The model only sees the task after a runtime has edited its context, carried forward state, and decided what survived the last turn—so the first question after a bad run is what the harness made it see.
More From This Edition
All editions ›Before You Blame the Model, Inspect What the Harness Made It See
Cline: the supervised editor agent growing into an SDK and CLI
Mastra: turning TypeScript application primitives into agent infrastructure
Qwen Code: when an open model and coding agent evolve together
Recent Editions
Full history ›Hugging Face Links 3D Dataset Previews to Their Mesh Files
A newly merged dataset-viewer change pairs a flat picture with a retrievable 3D asset. It connects a quick look at a dataset row to the geometry behind it—while wider “3D” labels remain a separate capability.
Unsloth Connects Existing Fine-Tuning Scripts to Multiple GPUs
Supported training scripts can now divide model work across graphics cards through a launch setting. A later change reconnects training to generation and export—with a different memory requirement at each stage.
Pi’s MCP Adapter Can Return Values Instead of Pages
Pi’s tool connector adds an optional Cloudflare reader for long replies. It sends the main agent named values, such as amounts and dates, plus a reference to the saved text.
OpenWork Adds Charts and 3D to Its Generated Apps
An agent-created interface can do more than display text and buttons. OpenWork has added a small catalogue of visual libraries it can bundle into an app—expanding what authors can build without asking them to install packages.
How AI Agents Work
The long-form map behind the daily paper: context, tools, loops, memory, delegation, safety, interface, and trust.