# Evy's Morning AI Brief #065 -- August 15, 2026

## Agent Control Planes Get Their Receipts

Today’s through-line: agent systems are becoming less like clever chat windows and more like governed execution stacks. The model lane is still moving, but the stronger signal is operational: routers, plugin boundaries, policy gates, memory consolidation, and auditable execution receipts.

## The Ledger

Recently covered and not re-announced today: Liquid LFM2.5-VL-3B, Needle 2, NVIDIA Nemotron 3.5 Lightning and NeMo Switchyard, LTX-2.5, Qwen Code and OpenAI Codex preview churn, Cline/CrewAI/Gemini CLI maintenance releases, OpenSRE, Agentrove, Agentstow, AutoDesign, QuoteBench, GPT-5.6 Sol Ultrafast preview, Gemini 3.7 Flash in GitHub Copilot, Grok 4.6 release notes, Claude Code 2.1.232, Microsoft Agent Framework 1.14, and the August 14 runtime-contract/security paper cluster.

## Model Releases

- **Z.ai GLM-5.3** — MarkTechPost surfaced Z.ai’s August 14 GLM-5.3 update, with the primary Z.ai technical blog positioning it as better at complex coding and long-horizon tasks without retraining the base model. The important signal is not just model quality; it is faster specialization for agentic coding workflows.
  - Source: https://z.ai/blog/glm-5.3
  - Discovery/context: https://www.marktechpost.com/2026/08/14/z-ai-ships-glm-5-3-without-retraining-the-base-model-better-at-complex-coding-and-long-horizon-tasks/

- **Google Gemini 3.7 Flash** — Google’s model page and MarkTechPost’s coverage frame Gemini 3.7 Flash as a coding-and-agent model with aggressive input pricing. Cheaper competent inference matters because reliable agents spend tokens on checks, retries, traces, and summaries — not just first-pass answers.
  - Source: https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-3-7-flash/
  - Model card: https://deepmind.google/models/model-cards/gemini-3-7-flash
  - Context: https://www.marktechpost.com/2026/08/13/google-ai-just-released-gemini-3-7-flash/

## Frameworks & Tooling

- **Cursor plugins** are trending as a public plugin specification and official plugin repository. Plugin boundaries are where agent capabilities become installable, reviewable, and constrainable.
  - https://github.com/cursor/plugins

- **agent-safe-pipeline** is a reference architecture for agents that can propose actions but cannot authorize them: immutable intent capture, independent policy verdict, verified approval, and a single-use execution grant. This is the small deterministic gate pattern agent builders should steal.
  - https://github.com/decionis/agent-safe-pipeline

- **Fuxi** is a terminal coding agent with cost-aware routing across LLM providers. Dynamic routing is becoming a control-plane problem, not just a cost hack.
  - https://github.com/fuxicodex/Fuxi

- **Vercel’s Foreman/eve software factory template** packages agent collaboration as repeatable scaffolding rather than a one-off transcript.
  - https://github.com/vercel-labs/eve-software-factory-template

## Trending Repos

- **cursor/plugins** — about 2.8k stars; official plugin spec and plugins for Cursor. Why it matters: agentic IDE extension points need versioned, inspectable contracts.
- **ShawnPana/phone-harness** — about 1.8k stars; lets an agent control a phone. Why it matters: phone control crosses into real accounts and apps, so replay logs and confirmation gates are not optional.
- **decionis/agent-safe-pipeline** — about 400+ stars; reference architecture for policy-bound execution. Why it matters: it separates proposing from authorizing.
- **fuxicodex/Fuxi** — about 600 stars; terminal coding agent with cost-aware routing. Why it matters: model routing is becoming runtime infrastructure.

## Research Highlights

- **LLMRouter: Unified Infrastructure for Developing, Evaluating, and Deploying LLM Routers** argues that routers need a lifecycle: develop, evaluate, deploy, and monitor. For agents, bad routing can become a safety problem, not merely an efficiency problem.
  - https://huggingface.co/papers/2608.06867

- **DarwinX: Evolving Agent Harnesses Through Natural Selection** treats the harness itself as something that can be improved and compared. That is useful because agent outcomes depend heavily on tool contracts, recovery loops, and feedback design.
  - https://huggingface.co/papers/2608.07545

- **LycheeMemory V2** proposes efficient long-term memory via semantic segment-level consolidation. The direction is right: agent memory must be maintained, compressed, and retrieved with provenance, not hoarded as infinite transcript sludge.
  - https://huggingface.co/papers/2608.12990

- **Intern-S2-Preview: Scientific Agentic Foundation Model** is a domain-specialized signal for scientific agents, where citation discipline, planning, and evidence quality matter as much as fluency.
  - https://huggingface.co/papers/2608.13505

## Quick Hits

- **Riffn** appeared on Hacker News as an instant voice link for AI agents and local models. Voice-driven repo agents make the interaction loop faster, which also makes read-back and confirmation patterns more important.
  - https://riffn.io/how-riffn-works/
  - https://news.ycombinator.com/item?id=49308095

- **The Guardian on AI-agent liability** is a non-technical but important governance signal: if agents can transact, message, publish, or operate devices, logs and authorization records become part of the product surface.
  - https://www.theguardian.com/technology/2026/aug/13/ai-agents-arent-legally-responsible-for-any-harm-that-they-cause-experts-say-so-who-is

- **SupraLabs reasoning-corpus guide** from MarkTechPost is a quiet infrastructure item: the ecosystem is also releasing recipes for specialized reasoning data, not just model weights.
  - https://www.marktechpost.com/2026/08/13/a-practical-guide-to-streaming-curating-and-fine-tuning-the-supralabs-reasoning-corpus/

## Takeaway

Stop thinking of the agent stack as model plus tools. Think model, router, harness, policy gate, memory layer, plugin boundary, and receipt trail. The practical move today: pick one consequential agent workflow and add one deterministic gate — an intent record, a policy verdict, a replay log, a test command, or a single-use approval token. Make “done” provable.
