The daily field guide to agent engineering

Control the
whole path.

Which skills enter context? Which memories reach the answer? Does a safety signal actually stop an action? Sunday’s research and releases put the connecting layers under scrutiny.

The 30-second take

Load skills selectively, use time as a retrieval signal, and test the gateway with the agent. Then verify that guardrails reach enforcement and that compaction and restarts preserve the work.

Today’s reading list

Showing all 6 items

01
Preprint · Sunday arXiv announcement · submitted October 16

SkillBrowser loads skills when the gap appears

The first user prompt is not always the best retrieval query.

SkillBrowser lets the agent identify a capability gap during reasoning, formulate a targeted query, and retrieve the procedural skill it needs. It avoids loading a large skill catalogue up front.

Across five models and six SRA-Bench subsets, with 26,262 candidate skills, it beats the same-backend static retriever in 23 of 30 settings, with one tie.

Evidence & limits. Submitted to ACL Rolling Review, not accepted. Author-reported results; useful skills sometimes go unrequested, the catalogue is static, and latency rises. Both query formulation and exposure timing change, so the study does not isolate selective loading alone. Its timing comparison excludes the baseline’s precomputed retrieval.

For agent builders

Evaluate skill discovery during the task, including missed invocations and end-to-end latency. A smaller prompt is useful only if the right procedure still arrives when needed.

02
NeurIPS 2026 accepted · Sunday arXiv announcement

TIDER gives memory a temporal retrieval channel

Similar events need more than semantic similarity.

TIDER combines semantic retrieval with an RL-trained 1.7B temporal-window locator, then reranks the combined evidence. Dates help decide which memories become candidates, before answer generation.

With fixed answer models and equal top-20 retrieval budgets, authors report 61.52% accuracy on LifeBench versus 52.70% for the strongest baseline, and 78.96% on LoCoMo versus 75.30%.

Evidence & limits. Acceptance is corroborated by the official NeurIPS catalogue. Experiments use synthetic English histories; LifeBench’s held-out test has 408 questions from two users. Results are three-run means, not independently reproduced. Upstream date quality matters; unanswerable and adversarial questions were excluded. Training and an extra retrieval stage add cost.

For agent builders

Preserve trustworthy timestamps and test temporal retrieval separately from semantic matching, especially for repeated events involving the same people or objects.

03
Preprint · Sunday arXiv announcement · submitted October 16

GatewayBench tests the layer between agent and tools

A gateway changes both capability and attack exposure.

GatewayBench contains 524 tasks and 11,118 tool definitions; its main study compares seven MCP gateways on 450 DTap tasks. It compares flattened tool exposure with hierarchical discovery under both benign and adversarial tasks.

Using GPT-5.4 and the OpenAI Agents SDK with no distractor tools injected, hierarchical gateways averaged 30.9% indirect-attack success versus 47.2% for flattened gateways. Benign task success was 85.1% versus 87.2%, respectively.

Evidence & limits. Author-reported preprint results, not production breach rates. Main experiments use one run per setting, default gateway configurations and two model tiers. Distractor tools have authentic schemas but mocked execution. Effects depend on the model and harness; no independently verified code release was located.

For agent builders

Make the gateway part of your deployment evaluation. Measure successful authorized work alongside attack success: a system that cannot do anything can look misleadingly safe.

04
Preprint · Sunday arXiv announcement · submitted October 16

A guardrail can run without controlling the decision

Test the path from detection to enforcement.

Monitor-Validity Failures reports 18 reproduced before-and-after failures across 11 project groups. In one NeMo case, a detector recognized prohibited content, but its positive result did not reach the blocking decision.

Fourteen cases reached enforcement boundaries: seven native actions, six configured boundaries and one synthetic consequence. The research examines how changing schemas, streams and adapters can break the path that carries safety evidence.

Evidence & limits. Targeted historical repair cases, not a prevalence estimate or evidence that current releases remain vulnerable. This is a preprint and the reproductions are the author’s. Supplementary artifacts are referenced, but a linked runnable repository was not located during this review.

For agent builders

Regression-test the resulting block, interruption or approval route, as well as whether the detector fires. A passing detector test is incomplete audit evidence for an end-to-end control.

05
Release · Letta Code v0.34.17 · October 18, 18:58 EDT

Letta composes tools and checks compaction progress

Tool-only scripts have different responsibilities from subagents.

Letta Code’s new CodeMode combines built-in and MCP calls in short JavaScript scripts without another model call or subagent. Scripts can yield and return completion to the originating conversation.

The same release hardens compaction: a summary is committed only when message count or estimated tokens decrease. Sliding-window compaction that makes no progress falls back to full compaction, then an explicit irreducible-context error. Failed resume-state reads also stop masquerading as an absence of pending approvals.

Evidence & limits. Maintainer-reported implementation and regression tests, with no independent speed or token-savings benchmark. CodeMode uses trusted node:vm execution, explicitly not a security sandbox. Nested calls requiring approval fail closed and must be invoked directly.

For agent builders

Keep approval semantics intact across tool composition, and require compaction to demonstrate progress. Test where background results return, not just whether the script executes.

06
Release · OpenClaw v2026.10.5 · October 18, 17:47 EDT

OpenClaw hardens restarts and post-approval changes

Finishing a turn includes delivering its authorized result.

Despite its version name, OpenClaw v2026.10.5 was published October 18. It packages interrupted-turn recovery, durable input handling, subagent-result delivery and recovery from malformed or stalled streams.

A separate approval fix prevents ordinary plugin hooks from substituting arguments after trusted inline approval without obtaining approval for the replacement. Transforming plugins may need migration to request that separate approval.

Evidence & limits. Project-reported tests, not an independent durability or security certification. A restart fix merged October 5; its packaging into this release is the new event. Approval tests cover the source-runtime integration path and verify no file output when replacement approval is missing, pending or denied. The separate full-CI report was not accessible for review.

For agent builders

Stage upgrades against transforming plugins. Inject restarts during cleanup and worker completion, and test argument mutation after approval. Preserving the authorization and the result’s destination are both correctness requirements.

How to read this edition

Announcement dates matter.

Coverage window: October 18, 00:00–23:59 EDT. The four papers were submitted October 16 and appear in arXiv’s Monday October 19 listing. Under its official schedule, that batch was announced Sunday evening at 20:00 Eastern. That announcement time is inferred from the schedule, not a paper-specific timestamp.

Paper results are author-reported; releases are maintainer descriptions. Nothing here was independently reproduced. TIDER’s conference acceptance is verified separately; the other three papers are preprints. Diagrams explain mechanisms and test plans, not measured performance. Do not compare numbers across these different tasks and harnesses.

Source check

Controls, without category filler.

AI Governance appears in gateway evaluation and enforcement testing. No substantive new sovereignty announcement was verified for this window; that facet remains available without padding it with a loosely related story.

AINews was checked at news.smol.ai; its visible index remained at September 9. The accessible October 17 AINews issue on Latent Space covers October 15–16. No October 18 issue was verified; no older roundup items are presented as new here.

Browse Past Editions →

Previous editions

View all editions