AI Briefings·10 min read

AI Morning Briefing — August 13th, 2026

Lyubo
Lyubo·
AI Morning Briefing — August 13th, 2026

Anthropic's multiagent research finds swarms hunt bugs well but can't build software together, DeepSeek V4 Pro 0813 goes GA at rock-bottom prices, and Qwen3.8-2.4T takes over r/LocalLLaMA.

AI Morning Briefing — August 13th, 2026

Your daily digest of what's happening in AI, straight from the trenches.


🚀 Headlines (30 sec read)

  • Anthropic publishes its biggest multi-agent study yet — 45-agent swarms are genuinely good at hunting vulnerabilities together, but 80-agent teams building a game from scratch produced slow, "inscrutable" software no matter how you organize them.
  • DeepSeek V4 Pro 0813 goes GA — $0.435 in / $0.87 out per million tokens, and a leaked benchmark table's trip through a deleted Reddit post and Hacker News ASCII art became its own story.
  • Qwen3.8-2.4T-A95B ships on Hugging Face — a 2.4T-parameter MoE with 95B active, topping SWE-bench Pro and Terminal-Bench, and it's all r/LocalLLaMA is talking about today.
  • Grok 4.6 launches from xAI (now SpaceXAI), undercutting GPT-5.6 Sol on price and landing day-one in Cursor.
  • New from IndyDevDan: "Is Anthropic STEALING Your Data? (While You PAY FOR IT)" — the real answer, plus the privacy toggle you should probably flip.
  • New from Owain Lewis: "I Replaced Hermes Agent And OpenClaw With This" — a single Rust binary that turns Codex into a Telegram-native personal assistant.
  • New from AI Jason: "I was building loops wrong..." — the markdown "loop contract" behind agents that run a real company's codebase 24/7.
  • New from Cole Medin: "Every Claude Code Skill I Use to Drive My Entire Development Process" — an installable skills marketplace covering PRD to shipped code.

🧠 Deep Dives (4 min read)

Anthropic Puts Dozens of Claudes in a Room Together — Results Are Mixed

Anthropic's new research post, "Patterns and problems in multiagent systems," runs two experiments that land very differently. In the first, 45 independent agents — each with its own virtual machine, a shared forum, and an identical prompt — were told to hunt vulnerabilities across 15 open-source projects, peer-review each other's findings, and let a separate arbiter agent decide what counted as a valid, new bug. This worked well: agents specialized into informal roles and built their own tooling around the task. The second experiment was rougher. Anthropic had swarms of 10 to 80 agents spend 12 hours building a text-based, open-world fantasy game together, testing three management styles — no structure, prescribed roles (programmers, artists, testers), and a "CEO hierarchy" where one agent assigned work to the rest. None of it mattered much: every version shipped bad games — slow, confusing interfaces with steep learning curves. As agent count rose from 10 to 80, the fraction of opened PRs that actually got merged fell sharply, especially for Sonnet 4.6 and Opus 4.6, while code-sharing between agents stayed low across the board. One early run even had 18 of 30 agents independently create a branch named "mvp-game-loop." The takeaway: parallel, loosely-coupled work (bug hunting) scales with agent count; tightly-coupled creative work (building one coherent thing) doesn't, and no amount of org-chart engineering fixed it yet. → Source

DeepSeek V4 Pro 0813 Goes GA — And Its Benchmarks Had a Weird Journey

DeepSeek's V4 Pro 0813 is now generally available via API, priced at $0.435 per million input tokens and $0.87 per million output — a fraction of frontier pricing from OpenAI or Anthropic. As Simon Willison noted, DeepSeek shipped it with no official announcement page at all: the benchmark numbers first surfaced in DeepSeek's WeChat group, got copied into a Reddit post that moderators deleted as "low-effort," and were then preserved as an ASCII-art table on Hacker News — which is now the closest thing to a primary source. On X, developer Petri Kuittinen ran his own private cybersecurity benchmark and found V4 Pro 0813 out-finding every other model, including Opus 5 and GPT-5.6 Sol, on vulnerability discovery — but with a catch: only 65.6% of its reported vulnerabilities were actually valid, versus 86.4% for GPT-5.6 Sol. That pattern — strong raw capability, weaker precision, and a habit of hallucinating confidently — is becoming the recurring DeepSeek story: genuinely competitive on hard technical tasks, but you still have to check its work. → Source

Qwen3.8-2.4T Ships, and r/LocalLLaMA Can't Stop Talking About It

Alibaba's Qwen3.8-2.4T-A95B landed on Hugging Face today: 2.4 trillion total parameters, 95 billion active via a 512-expert MoE (10 routed + 1 shared), a native 262K-token context extensible to just over a million, and reasoning-mode-only inference. Benchmarks are legitimately strong for the tier — SWE-bench Pro at 67.7, Terminal-Bench 2.1 at 86.6, PaperBench at 93.0, GPQA Diamond at 92.6 — backing up Alibaba's earlier claim that it sits "second only to Fable 5" while costing roughly a tenth as much. It's the top post on r/LocalLLaMA right now with over 1,400 upvotes and 370-plus comments, alongside threads asking how anyone plans to actually run a 2.4T model locally and a pointed complaint that, for a flagship this size, it ships with no vision support at all. That gap — plus the model's qwen3.8-max license rather than a fully open one — is tempering the enthusiasm even as the raw numbers impress. → Source


New from YouTube (2 min read)

Is Anthropic STEALING Your Data? (While You PAY FOR IT) — IndyDevDan

Covers: Argues AI labs don't train on your raw prompts, but do mine aggregated, anonymized usage data for market trends — and have a track record of following the signal into your vertical (Claude Code after Cursor, Claude Design after Figma MCP usage spiked, Claude Security, Claude Life Science). Proposes a simple test: would it matter if a competitor read your full agent trace?

Example: Walks through Claude.ai's actual privacy settings (Cmd+Shift+, → Privacy → "help improve our AI models" toggle) and points to the documented 30-day mandatory data retention policy for Fable 5 as the real, non-speculative mechanism behind the concern.

Watch

I Replaced Hermes Agent And OpenClaw With This — Owain Lewis

Covers: After months running Hermes Agent as a personal assistant, argues its two headline features — a messaging gateway and self-learned memory — are now redundant, since Codex and Claude Code both ship background cron tasks and memory natively, while Hermes's auto-saved "facts" frequently go stale and mislead the agent.

Example: Built "Push," a single Rust binary that polls Telegram (no open ports) and dispatches work to an existing Codex agent. Demos it triaging 120 emails into four Todoist tasks, answering a spoken priorities question by voice, and drafting a reply — no custom backend required.

Watch

I was building loops wrong... — AI Jason

Covers: Breaks down the structure behind the autonomous "loop" agents his company runs continuously — a markdown "loop contract" (goal, boundaries, SOP) plus append-only state and logs, four trigger types (continuous while-loop, cron, event/webhook, and a cost-saving check-then-trigger combo), and a mandatory verifier stage before anything merges.

Example: Shows the actual react-doctor loop that scans the codebase daily and auto-fixes the top issue, plus a CRM loop that segments users and drafts outreach — both defined in one markdown file and run through an open-sourced tool called Loopery.

Watch

Every Claude Code Skill I Use to Drive My Entire Development Process — Cole Medin

Covers: Packages a full AI-coding workflow as an installable Claude Code skills marketplace — an "outer loop" (PRD → architecture spec → ticket-slicing) run once per feature, and an "inner loop" (prime → plan → implement → validate) run per ticket, built around writing the test strategy before any code exists.

Example: Installs the skills plugin live, runs /plan-prd to interview-generate a PRD, then /piv-slice-epic to split it into tickets — showing the actual plan template's testing-strategy section (unit/integration/edge cases, lint, typecheck, browser-automation checks) the agent must satisfy before calling anything done.

Watch


📅 Coming Up This Week

DateEvent
Aug 21Grok 4.7 could ship, per early X chatter — xAI/SpaceXAI hasn't slowed down after 4.6
OngoingDaybreak Red vetting keeps expanding GPT-5.6-Cyber access to authorized defenders
WatchingWhether DeepSeek open-weights V4 Pro 0813, as it did for prior Pro and Flash releases
Dec 2EU AI Act's AI-generated-content labeling deadline for standalone high-risk systems

🛠️ Try This Today

Put DeepSeek V4 Pro 0813 Up Against Your Daily Driver

  1. Grab a free OpenRouter API key and point your usual CLI or agent at deepseek/deepseek-v4-pro-0813.
  2. Run the same real task you'd normally hand your frontier model — a multi-file refactor or a genuinely gnarly bug, not a toy prompt.
  3. Compare the diff and the bill: V4 Pro runs $0.435 in / $0.87 out per million tokens, a fraction of frontier pricing.
  4. Weigh that against the hallucination risk developers are already flagging before trusting it with anything security-critical.

Why it matters: at these prices, "try the cheap model first" stops being a compromise — but only if you've verified it holds up on your workload, not someone else's leaderboard.


⚡️ Quick Links (2 min read)

GitHub Trending

Reddit Hot

  • [r/LocalLLaMA] Qwen3.8-2.4T-A95B Released — 1.4K upvotes and counting, the top post on the sub right now → Discussion
  • [r/LocalLLaMA] Nvidia doubles RTX PRO 6000 Blackwell's MSRP to $16,000 — up from under $8,000 at pre-order last year → Discussion
  • [r/LocalLLaMA] "Qwen 3.8Max 2.4t Open Weight NO vision?!?" — the flagship's missing multimodality is souring an otherwise strong launch → Discussion

Hacker News Top


🦞 TL;DR

The narrative today: the model layer keeps getting cheaper and more open from below — DeepSeek at pennies per million tokens, Qwen shipping a 2.4T open-weight-adjacent model, Grok undercutting on price — while Anthropic's own research shows the frontier labs still haven't solved the much harder problem of getting a lot of agents to build one coherent thing together.

My take: the multiagent paper is the most honest thing I've read from a lab all week — "our 80-agent game-building swarms made bad games no matter how we organized them" is not a sentence a hype cycle produces voluntarily. Pair that with DeepSeek's benchmark literally traveling through a deleted Reddit post before becoming a Hacker News ASCII table, and today feels like a reminder that verification is lagging capability everywhere, not just in the models — in how we even find out what they can do.

What I'm watching: whether anyone cracks tightly-coupled multi-agent coordination before agent counts scale further, and whether Qwen's vision gap gets patched or becomes this model's defining asterisk.

Stay informed. Stay curious.

Share:
AIAnthropicDeepSeekQwenDaily Briefing