Anna Silman's Wall Street Journal investigation puts it plainly: AI-generated manuscript submissions are now overwhelming literary agents, with one WME agent comparing the flood to something that makes "Fifty Shades of Grey look like Tolstoy." The same week, a water engineer asked Claude Opus 5 to model a storm drain system and got back a self-contained, visually striking 3D renderer in a single 2 MB HTML file, no hand-written code, beating dedicated CAD tools on aesthetics. Both are real. Both are happening this week. The gap between them is the bind.

One group is using AI as a volume machine: more submissions, more noise, more undifferentiated output flooding acquisition pipelines and squeezing the authors who depend on commercial writing to fund serious work. The other is using it as a leverage machine: a single engineer collapsing a professional toolchain into one artifact. The first group is compressing the signal-to-noise ratio across entire industries. The second is compressing entire workflows into a single file. Those two strategies don't end in the same place, and the publishing industry is already finding out which one wins when they collide.

Top developments

  • Claude Opus 5 generates a sci-fi interactive 3D storm drain renderer as a single 2 MB HTML file: Water engineer elaifresh asked Claude Opus 5 to model a storm drain system and got back a self-contained, visually striking 3D renderer in one 2 MB HTML file, beating dedicated professional CAD tools on aesthetics and interactivity with no custom code written by hand. Anthropic released Claude Opus 5 on July 24, 2026, as its new flagship everyday model optimized for coding and knowledge work.

  • AI Has Plunged the Book Publishing Industry into Utter Chaos (paywalled): A Wall Street Journal investigation by Anna Silman finds that AI-generated manuscript submissions are overwhelming literary agents and editors, with one WME agent quipping that some AI-written queries "make 'Fifty Shades of Grey' look like Tolstoy." The flood is degrading the signal-to-noise ratio across acquisitions pipelines and squeezing authors who depend on commercial writing work to fund their literary careers.

  • OpenAI 'will be a public company in 2027' or sooner, CFO Friar tells employees: At an all-hands meeting on August 19, OpenAI CFO Sara Friar told staff the company will go public in 2027, or sooner if "our business continues to inflect," framing the IPO as "not a finish line, it is a milestone, another fundraise." OpenAI confidentially filed its IPO prospectus with the SEC in June and raised $122 billion in March, giving it flexibility on timing. The message came with Anthropic also deep in IPO preparations, and observers note the public pledge signals concern about retaining talent against rivals who can offer better near-term liquidity.

  • Merck and Moderna's personalized mRNA cancer vaccine succeeds in first-ever Phase 3 trial for melanoma: The jointly developed vaccine, intismeran autogene, uses machine learning to identify tumor-specific neoantigens and generate a custom mRNA sequence for each patient. Combined with Merck's immunotherapy Keytruda, it met both recurrence-free survival and distant metastasis-free survival endpoints in the INTerpath-001 Phase 3 trial for resected high-risk melanoma, marking the first time an mRNA cancer vaccine has succeeded at this stage. The vaccine is not yet approved and targets treatment, not prevention.

  • Japan to require AI firms to disclose training data: Japan's government panel has broadly approved a "comply or explain" code that would press generative AI companies to publish what training data they use and how it was collected. The code is nonbinding: firms that decline to disclose need only explain why they won't, which critics say makes meaningful enforcement unlikely.

Videos worth watching

Announcements & releases

Worth reading

  • Building Customer Support AI Agents at 100M-User Scale: An Evaluation-Driven Framework: Nubank's engineering blog describes how they built and deployed production customer-support agents across a 131-million-user base. The post covers the full stack: offline evaluation methodology, context engineering, LLM fine-tuning, and online measurement, showing how to close the gap between lab benchmarks and real-world impact. A useful reference for anyone building customer-facing agents at scale. The accompanying paper goes deeper on the evaluation-driven framework.

  • Bypassing Figma and Building a Knowledge Product: How Little Plains Built Their AI-Powered Studio Site: Little Plains designer and entrepreneur Emmett Shine published a technical breakdown of how his studio turned two years of internal work into a searchable, AI-powered knowledge center, including the retrieval architecture, models used, how they shipped without Figma, and an eight-step guide for building your own knowledge product on top of existing material.

  • Chain-of-Thought Reasoning In The Wild Is Not Always Faithful: A paper from researchers including Neel Nanda and Arthur Conmy shows that LLMs can produce superficially coherent but contradictory reasoning traces even on plain, non-adversarial prompts. When asked "Is X bigger than Y?" and "Is Y bigger than X?" separately, models sometimes answer Yes to both, generating plausible-sounding arguments for each, suggesting the visible chain-of-thought reflects implicit yes/no biases rather than genuine reasoning. Replacing thinking tokens with filler or training on corrupted traces causes only modest performance drops, which further undermines the idea that token-level reasoning traces are semantically meaningful.

  • Stop Anthropomorphizing Intermediate Tokens as Reasoning/Thinking Traces: A position paper from ASU's Subbarao Kambhampati and colleagues argues that labeling LLM intermediate token output as "thinking" or "reasoning" traces is a harmful metaphor, not a harmless one. The paper shows only a loose correlation between those tokens and solution correctness, meaning the traces don't reliably expose what the model is "doing." Treating them as interpretable windows into model cognition can breed false trust and mislead users and researchers alike. The authors propose viewing intermediate tokens instead as learned prompt augmentations, a framing with fewer misleading implications.

  • Universality of Gradient Descent Neural Network Training: A 2020 paper by G. Welper proves that if any algorithm can find good weights for a classification task, you can always redesign the network so that plain gradient descent finds those same weights. The result is theoretical rather than practical, but it sheds light on the fundamental power of gradient descent and has implications for understanding meta-learning approaches.

  • Building Shared Memory for AI Agents in Notion: Notion engineer Hesham Salman explains how tribal knowledge gets siloed inside individual agent sessions and outlines Notion's approach to giving AI agents a shared, persistent memory layer so learnings can survive across sessions and team members. A practical read for anyone building multi-agent or long-running agentic workflows.

  • How to build an eval set you can maintain: Langfuse's Academy guide walks through picking the right metrics for LLM evaluation, organizing them into three buckets: goal metrics (is quality improving?), guardrails (things that must never regress), and operational metrics (cost and throughput). The advice to keep the set small and seeded from real production traces rather than synthetic data makes this practical for teams moving beyond prototype evals.

Discussions & takes

  • Agents ignore MCPs and CLIs, creating a silent churn risk for SaaS products: Scope founder Anand Paj argues that AI agents don't look for the "right" integration surface: they just try to finish the task, which can mean spinning up a full UI instead of hitting a simple API. If an agent fails on your product it quietly moves on to a competitor, meaning you can lose a customer before you ever know you were being tried.

  • Feature request asks Claude Code to support AGENTS.​md, the cross-agent instruction file convention: Different coding agents read different files for project-level instructions: OpenAI Codex reads AGENTS.​md, Claude Code reads CLAUDE.​md, and so on. A GitHub issue filed against the Claude Code repo asks Anthropic to also recognise AGENTS.​md so developers don't have to maintain duplicate instruction files per agent. The issue was quickly closed as fixed by a third-party pull request, but the underlying debate about fragmentation and lock-in remains lively, with some arguing that agent-specific files are unnecessary if projects maintain good README and CONTRIBUTING docs to begin with.

  • Extensible Software in the Age of LLMs: Engineer Jeremy Morrell argues that LLMs have quietly created a new opening for extensible web software. Most apps serve the top of the demand curve and leave a long tail of niche needs unmet, LLMs are now good enough to generate custom plugins and personal tools for those gaps. He sketches a path where web apps ship sandboxed extension runtimes (using V8 isolates or microVMs) so users, or their agents, can bolt on behavior that the core product would never prioritize. Some observers push back on whether web delivery is even necessary when a local LLM-generated native app would do the job just as well.

  • OpenAI's Unraveling Has Begun, argues Gary Marcus: NYU professor emeritus and AI critic Gary Marcus argues that OpenAI is entering its opening stages of collapse: public trust has evaporated (Sam Altman's August 18 announcement pausing frontier RL training for safety reasons was met with near-universal skepticism), its planned IPO faces headwinds, and its burn rate keeps worsening. Skeptics note Marcus has been predicting AI industry collapse for years, and that his recent posts rely heavily on curating others' tweets rather than original analysis.

  • OpenAI's API returns parallel tool calls in two inconsistent formats: Flyweight.​io co-founder Chris Cook discovered that OpenAI's API can respond to parallel tool call requests in two distinct shapes: either as multiple separate function_call items (one per tool), or as a single function_call named "parallel" with all calls nested inside a tool_uses field. Code that only handles one format will silently break on the other, and this split behavior is not clearly documented.

Worth noting

Funding & deals