The daily field guide to agent engineering

Done needs
evidence.

Check completed work. Give execution a boundary and files a durable home. Ask whether memory earns its compute. Six developments with their limits in view.

The 30-second take

Verify finished work before accepting it. Separate durable workspaces from execution. Audit memory benefits against compute, rather than assuming a more elaborate structure explains the gain.

Today’s reading list

Showing all 6 items

01
Preprint · Announced October 15

Probe-and-Resume

Spend extra compute where the agent says it is done.

A completion-time critic checks disposable copies of the current and initial environments. If it rejects the result, the original agent resumes work.

Across 89 TerminalBench 2.1 tasks and five trials, reported success rises from 63.4% to 72.4%, a 9-point gain with a reported confidence interval of 5.6–12.6 points. The MCTS comparison reaches 64.0%; model cost is 2.2× the baseline.

Evidence & limits. No significant benefit was established for the stronger Astra/Opus configurations. Forking an environment does not isolate external databases or services; destructive checks need additional isolation. Submitted October 14 EDT, then announced in the October 15 evening batch.

For agent builders

Evaluate a completion audit against repeated partial judging, including the extra compute and the safety of the checks themselves.

02
Preprint · Submitted October 15

Memorilla

Compress documents into a small learned memory.

Query-relevant, reusable document embeddings are compressed into 16 latent memory tokens for a frozen language model.

The method beats the best tested baselines on five of eight benchmarks. On FactKG, it scores 84.33 versus 80.43 for full context while using 108× fewer document-representation tokens. TextWorld rises from 18.6 to 24.2.

Evidence & limits. The roughly 194-million-parameter memory module is trained, with benchmark-specific fine-tuning. The experiments use Qwen encoders and decoders; cross-family transfer and coding use are unproven. Fine details can be lost. The token reduction is not a total-cost claim.

For agent builders

Treat latent memory as a learned component with training and information-loss tradeoffs, rather than a training-free replacement for retrieval.

03
Preprint · Submitted October 15

Rethinking Tool Graph Memory

Is the graph helping, or is the extra compute?

A study of ToolNet and H-EPM tests nine open models on ToolSandbox and BFCL v4, with three runs per setting.

Reliable H-EPM gains appear in only four settings. On ToolSandbox, it averages 2.72× the language-model calls and 2.21× the tokens. Random or absent next-tool suggestions preserve much of the gain.

Evidence & limits. Lightweight textual situational insights perform better in most settings with almost no extra inference calls, but offline construction still costs compute. The critique concerns tool nodes and transition edges, not every entity graph or state graph.

For agent builders

Use compute-matched baselines and randomized controls before attributing a memory system’s gains to its structure.

04
Open-source release · October 15

Perplexity SPACE

Put a clear boundary around long-running execution.

SPACE exposes Firecracker microVM infrastructure for agent execution, including lifecycle management, pause, resume and recovery.

The Apache 2.0 release separates network control and credentials from the untrusted sandbox. The implementation is inspectable infrastructure for long-running agent workloads.

Evidence & limits. Perplexity reports zero host escapes across 108 attempts, but initial network bypasses were found and fixed. A vendor-reported test is not a guarantee of isolation across deployments or future attacks.

For agent builders

Inspect where credentials and network policy live, then test the boundary with the workloads and external services your agent actually uses.

05
Generally available · October 15

Vercel Drives

Keep the workspace after the sandbox is gone.

Drives provide persistent files independent of a Vercel Sandbox, with forks for parallel agents. General availability covers Hobby, Pro and Enterprise plans.

A Drive supports one writable mount. Read-only mounts are point-in-time snapshots, and the Drive and Sandbox must be in the same region.

Evidence & limits. Forks do not merge back automatically. Persistent storage solves workspace lifetime; coordination, conflict resolution and integration remain application responsibilities.

For agent builders

Separate durable workspace state from execution lifetime, and make the orchestrator own the merge strategy before parallelizing work.

06
Release · October 15 · Paper October 13

Sakana Agentic Scientist

Research agents still need a validity check.

Parallel coding agents work from hypotheses and evaluation rubrics. They share successes and failures at cycle boundaries, reset context during handoffs, and produce ablations and claim-to-evidence mappings.

The system keeps human questions and validity judgments in the loop. The release illustrates how structured experiment cycles can preserve useful findings across parallel work.

Evidence & limits. Author-reported research includes observed reward hacking. The scope is computational machine learning; literature search supports writing rather than ideation. This is an October 15 release with an older October 13 paper, not a new paper that day.

For agent builders

Preserve both negative and positive results, and review whether each claimed improvement survives ablations and a check for metric exploitation.

How to read this edition

Compare claims on their own terms.

The first three items are preprints with author-reported results, not independently replicated findings. The chart compares methods within Probe-and-Resume’s evaluation only. Diagrams are explanatory abstractions, not measured system traces.

Release descriptions establish what was announced, not reliability in your deployment. Security tests are bounded evidence. Compression ratios describe the stated representation, not end-to-end cost savings.

Source check

Dates and evidence stay separate.

The October 16 arXiv listing corresponds to the October 15 evening announcement batch in EDT. Probe-and-Resume was submitted October 14 EDT; it is included for that announcement. Sakana’s October 15 release accompanies an October 13 paper.

The October 16 AINews issue, covering October 14–15, was used for discovery via its newsletter; the public page could not be fetched. The main AINews index still showed September 9. Claims here are grounded in the linked primary sources. Sakana’s announcement date was corroborated through an embedded reproduction because direct access to its X post was blocked.

Browse Past Editions →

Previous editions

View all editions