Just four months after coming out of stealth, Onyx Security raised a $113M Series B led by Bessemer Venture Partners at roughly a $640M valuation. The bet: a control layer that watches every step of an agent's reasoning and intercepts actions before they take effect is the next generation of security infrastructure.
Zenity closed a $125M Series C led by Norwest Venture Partners, with SoftBank Vision Fund 2, Hitachi, and LG Technology Ventures joining. Norwest's thesis: the agent is the new perimeter — traditional network-boundary security no longer works against autonomous agents, and a governance platform has to be built for agents from the ground up.
Self-hosting an agent that runs 24/7 means opening something on your own network that must be reachable from outside and must never sit on the public internet. This post takes apart what each Tailscale mechanism actually solves: the tailnet for reachability, subnet routers for private resources, tags plus ACLs for the permission boundary, and seconds-fast policy propagation plus Tailnet Lock for revocation. Pricing checked 2026-08: Personal is free, up to 6 users, unlimited user devices, 50 tagged resources included.
ActBench red-teams cowork agents via execution traces, finding ASR of 73.7%–94.4% even when swapping harnesses; Agent Behavioral Contracts II shows co-failure rates hit 90% for same-model two-stage pipelines, breaking the conditional independence assumption; Graph-Based RL Drift Diagnosis uses a small-model recovery graph to detect drift and auto-rollback without retraining the primary agent
PIMiner uses a transferable strategy library to push prompt injection ASR to 76–87% at ~$20 query cost; Agent Skills Can Be Harmful finds that seemingly relevant skills are more likely to derail tasks than obviously unrelated ones, with excessive procedures accounting for 62.6% of efficiency degradation; Order 66 scenario analysis uses a compositional threat model to show that dormant implants, post-hoc memory poisoning, and peer-to-peer diffusion are individually non-fatal but can sustain self-propagation when combined
EvoGraph-Mem uses a failure-aware editable graph to let agent memory self-correct, preventing stale insights from poisoning decisions; MAP-Graph turns provenance tracking from post-hoc audit into real-time access control, achieving 95% success across 2,700 synthetic tasks; MaSRead shows multi-agent KV cache sharing is possible but requires content-addressed reading instead of positional addressing
ToolLIFT lifts tool trajectories to function-level workflow graphs and consistently beats SOTA on three OOD benchmarks; SkillTV-Bench uses 681 cases to show skill-aware judge skills boost agent evaluation accuracy by 14.8pp; TRIO-20's prespecified equivalence study finds zero unauthorized calls from GPT-5.6 across 840 trajectories, but higher reasoning effort increases rule-probing rate by 14.3pp
Three papers examining AI Agent capabilities and limits from different angles: AutoMem shows memory management is a learnable skill — optimizing memory alone lifts a 32B open-source model to top commercial model levels; Shadow Evaluation tests whether frontier Agents can do open-ended AI research using real NeurIPS submissions — the answer is no, Agents can engineer but cannot research; Adaptive Adversaries reveals that existing safety benchmarks severely underestimate threats — adding adaptive multi-turn attackers jumps ASR from 0–1% to 14%. Together, these three papers deliver a sobering lesson: know where Agents can automatically improve, where they cannot, and that your security testing is probably insufficient.
Three papers tackling multi-agent platform challenges from three angles: organizational design, security isolation, and user-level authorization. IMACS decomposes multi-agent systems into three independently swappable layers (organization, coordination, collaboration algorithm), letting framework designers mix and match agent roles and strategies like building blocks. APPA uses context branching to break the usability bottleneck of IFC (Information Flow Control), cutting prompt injection exfiltration rates from 31–50% down to 0–7% across 4 models. A UW survey of 21 agent authorization proposals finds that nearly all systems offer only developer-defined global policies — user-level personalized authorization is virtually absent. Together, the three papers outline the gaps agent platforms must close on the road from prototype to production.
Three papers tackle 'what goes wrong when agents hit production' from different angles: ProACT addresses when an agent should speak up in multi-user collaboration (an Agent UX design problem); the second uses real GitHub data to reveal that coding agents clash with their own PRs (a platform ops pain point); the third surveys five vulnerability classes of cyber-capable agents, using July 2026 HuggingFace/OpenAI incidents as case studies. Together, they form a crash course in post-deployment agent headaches.
Three papers today converge on infrastructure reliability for production multi-agent systems: the first compares how MCP and A2A divide responsibilities (complementary, not competing); the second benchmarks capability degradation across 12 top models after tool version updates, finding 13-14% drops even in frontier models; the third reveals that chaining safe models into a pipeline does not yield a safe system — defenses actually rely on cloud-provider server-side filters. Together they answer three questions every platform engineer faces: how to connect tools, whether tool upgrades break things, and whether chained agents stay secure.
Three papers examining real-world challenges for AI coding agents: the first systematically demonstrates how coding agents can be tricked into supply-chain attacks via manipulated READMEs, with defenses depending more on the harness than the model; the second introduces BPO, a reinforcement learning algorithm that branches only at high-entropy decision points for more efficient agent training; the third shows how MCP can serve as a standard protocol for connecting agents to domain-specific simulation tools in industrial settings like power grids, providing a replicable template for vertical-domain agent deployment.
Three papers tackling three core agent-platform challenges: MyAG introduces a graph-theoretic decomposition of agent systems into component / workflow / search layers; a self-improvement survey unifies the entire 'how agents evolve from experience' landscape under one formula; and MemPoison reveals persistent memory as the most vulnerable attack surface, with a 1,227-case benchmark. Together they cover: how to architect → how to evolve → how not to get compromised.
Three papers tackle production-grade agent reliability from different angles: MemCon models memory operations as an RL problem so agents learn when to store, retrieve, and forget — up to +15.2 points on 6 benchmarks; AgentCheck turns MCP servers into a debugging surface for reproducing tool faults and verifying fixes, filling a long-standing gap in the MCP ecosystem; AgentAbstain uses 263 paired tasks to show that even the strongest frontier models score below 60% on 'should-not-act' scenarios, and abstention ability barely correlates with task-solving ability — swapping in a stronger model won't fix this.
Three papers illuminate the AI agent landscape from very different angles: LHTB benchmarks 46 long-horizon terminal tasks and finds even the best model solves only ~28%; a second paper reveals a fragmentation effect in multi-agent systems that defeats per-agent monitoring; a third argues that in-process memory retrieval—1000× faster than cloud vector stores—fundamentally changes agent reasoning quality.
Three papers tackle AI Agent platforms from practical angles: the first exposes stealthy security threats in multi-agent systems and proposes activation-space detection of malicious agents (F1 +0.55 over graph methods in async settings); the second improves coding agent retrieval by introducing procedural similarity — finding code with similar solution steps rather than surface resemblance; the third is a wake-up call: the same LLM in different harnesses produces significantly divergent mid-task judgments, meaning harness design is never neutral.
Three papers today revolve around two themes: **security** and **evaluation**. Prismata blocks cross-site prompt injection at the page level; aiAuthZ establishes a cryptographic identity-bound authorization gateway at the tool-call level — together they argue the LLM itself should never be the security boundary, and platforms must enforce defenses at the architecture layer. The third paper, UniClawBench, moves agent evaluation from sandboxes into the real world, diagnosing failures by 'capability dimension' instead of 'task scenario' — giving platform engineers a sharper tool for model selection and failure analysis.
Three papers today converge on one question: how can Agent systems operate reliably? STRACE tackles noisy optimization inputs — precisely identifying root causes from massive noisy failure traces so automatic optimization stops getting derailed by redundant cases. The Blind Curator exposes an unsettling silent failure mode — the skill retirement mechanism in self-evolving Agents completely breaks down beyond a certain LLM judge bias threshold, and no amount of additional data can fix it. Severity Scale transforms 'how bad was this Agent attack' from binary success/failure into a seven-level action-harm score, finally giving security evaluation the granularity it needs. Read together: optimization quality, self-evolution soundness, security evaluation precision — three different layers, all pointing toward Agent trustworthiness.
Three papers sound the Agent security alarm from different angles: FARMA silently corrupts Agent reasoning memory with 100% success rate bypassing all defenses; Vera tests 4 production Agent frameworks (including Claude Code) with 93.9% average attack success rate; PiSAs reveals cross-user information leakage in shared Agent environments as a severely underexplored problem. Together, they represent the security reality that those deploying Agent platforms must confront.
All three papers today center on making agent systems safer, more predictable, and less failure-prone. The first two come from the same research group and take a static-analysis angle: one systematically uncovers why and how often agents get stuck in infinite loops, while the other builds dependency graphs for entire agent codebases to enable security audits and component inventories. The third targets multi-agent software development, introducing LLM confidence scores into the collaboration flow to prevent early hallucinations from cascading downstream.
Three papers each expose an evaluation blind spot in agent systems: memory makes agents more sycophantic yet rarely gets tested (MemSyco-Bench); existing safety benchmarks flatten every failure into pass/fail, obscuring root causes (Adversarial Pragmatics); LLM agent collectives, communicating in natural language, are actually more interpretable than black-box neural networks (Conversable Complexity). The combined message: the way we evaluate agent systems needs a comprehensive upgrade.
Three papers exploring the boundaries and breakthrough paths of agent capabilities. Sakana Fugu (Sakana AI) trained a 0.6B orchestrator model that learns to dynamically coordinate a pool of frontier LLMs, achieving public SOTA on SWE-Bench Pro and other benchmarks — the core thesis is that the orchestrator itself can be trained rather than hard-coded by engineers. NatureBench uses 90 real research tasks from Nature journals to ask: can coding agents actually make scientific discoveries? The best configuration only surpasses published SOTA by 17.8%, mainly by translating problems into familiar ML tasks rather than truly inventing new methods. Finally, Rising from the Ashes — six security researchers systematically map how agentic AI can take over five categories of labor-intensive tasks that have long plagued defenders, with 16 case studies as deployment references.
Three papers targeting three critical infrastructure layers of Agent platforms: HarnessX introduces a 'harness as evolvable component' framework that turns static Agent scaffolding into a self-optimizing system (+14.5% average across 5 benchmarks); the second studies skill-conditional trust routing in multi-agent collaboration, revealing when fine-grained trust actually helps and how attackers can hijack it; OCELOT tackles security with a 'posterior leakage budget' mechanism to prevent Agents from gradually leaking user privacy to external services. Together they cover framework design, multi-agent governance, and privacy security — exactly the three pitfalls most commonly hit when shipping Agent platforms to production.
Today's three papers center on **security boundaries and capability optimization for coding agents**: SABER introduces the first executable-workspace benchmark and finds even the best models have 54%+ dangerous operation rates; the second paper has 100+ real developers collaborate with a secretly sabotaging AI agent for five hours — 94% never noticed; SePO shows that auto-optimizing system prompts alone (no model changes) yields an average 4.49-point gain across five benchmarks. Together they remind platform builders: agent safety is harder to measure and harder to catch than assumed, yet low-cost improvement paths exist.
Three papers on three deep agent-system questions: **memory architecture** (which design generalizes?), **self-evolution** (can AI build agents autonomously?), and **security blind spots** (how domain-dependent is CUA safety?). AutoMEM shows agents that actively manage their own memory generalize better than those relying on external pipelines; Meta-Agent Challenge reveals that frontier models still fall well short of autonomous agent development; Domain-Conditioned Safety finds Claude Sonnet 4.6 has 0% prompt-injection ASR on web tasks but 100% on code tasks — all three challenge core design assumptions in agent platforms.
Three papers tackling core agent platform pain points from different angles: the first proposes compiling LangGraph-style orchestrator logic directly into small model weights, cutting per-conversation cost by 128–462×; the second, from IBM Research, builds a three-level automated evaluation framework that solves the 'agent broke but which step failed?' problem; the third, from Microsoft, proposes a portable memory protocol enabling memory handoff between Claude / GPT-4 / Gemini without losing state. Together they cover three critical dimensions: deployment efficiency → behavior evaluation → memory portability.
Three papers at three different layers: BenchTrace ran 1,821 agent failure episodes and found GPT-4.1 and Qwen3-32B pass less than 30% on diagnosing their own failures — reflection is far weaker than assumed; Beyond Autonomy distills a three-tier governance architecture from enterprise SaaS production, filling the missing 'governance' piece in current agent frameworks; Insuring Every Action prices every agent action using actuarial concepts and introduces reserve capital budgets, creating an entirely new runtime risk vocabulary. The common thread: the core challenge of enterprise agent deployment has shifted from 'can it do the job' to 'what happens when it fails, who reviews it, and how do you quantify the damage.'
Three papers tackle AI Agent practice from three angles: a design language, a security map, and cognitive limitations. The first builds a two-axis classification framework giving engineers and researchers a shared vocabulary for agent architecture trade-offs; the second systematically catalogs safety and privacy risks across tool calls, memory, and multi-step execution in agentic AI; the third is the most impactful — a large-scale experiment with nearly 40,000 AI-generated ideas reveals that AI research agents tend to circle existing literature rather than genuinely broadening scientific exploration.
Three papers today point to three gates agents must pass on the road from demo to production: AgentTrust adds a runtime interception layer before tool calls, filling the gap between static blocklists and post-hoc benchmarks; Hermes scans 600 production endpoints and finds existing REST API docs almost universally unfit for MCP agents (4 issues per endpoint on average); PARPO pushes personalization from the prompt layer down into RL training so agents behave differently per user instead of being 'okay for everyone.' Together they outline how much hard work remains on the security gate, API readiness, and personalization fronts for production-grade agent systems.