AI Briefings·7 min read

AI Morning Briefing — November 2nd, 2026

Lyubo
Lyubo·
AI Morning Briefing — November 2nd, 2026

Mathematicians react to OpenAI's paper dump, Postgres 19 slips as LLMs find bugs, and a benchmark of what 12 JS frameworks cost an AI agent.

AI Morning Briefing — November 2nd, 2026

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


🚀 Headlines (30 sec read)

  • Terry Tao's blog hosts a mathematician's reply to OpenAI's paper dump — Frank Calegari: don't be sad, the subject isn't "solved"
  • Postgres 19 is late, and Robert Haas blames LLMs — back-patched commits up 60%+ as AI-found bugs flood in
  • Nolan Lawson benchmarks the AI cost of 12 JS frameworks — Hono+htmx cheapest at $2.67 per run, Angular priciest at $4.97
  • Claude Code reportedly now refuses to clone existing games — rule found in server-side instructions, not in the changelog
  • Local-model push continues — DeepSeek V4.1 agent sessions start 20× faster on a gaming GPU, per a LocalLLaMA post

🧠 Deep Dives (4 min read)

Mathematicians respond to OpenAI's October 6 paper release

A guest post by Frank Calegari on Terry Tao's blog takes on the mood in mathematics after OpenAI released over 700 research papers on October 6. He calls it a watershed and says AI can now make groundbreaking contributions in many areas, while admitting the papers are poorly written, break attribution norms, and some are wrong. His central argument: nobody has "solved number theory" any more than the periodic table solved chemistry. He compares it to the classification of finite simple groups, which cooled interest in the field but left rich questions behind. His advice is to spend effort on what mathematicians control (hiring, publishing, training students) and to reward people who explore the paths the AI skipped. Hugo Duminil-Copin's reaction, quoted in the post: every major open problem he had publicly mentioned was claimed as proved, "not all at once, not with such nonchalance." → Source

Postgres 19 slips because LLMs keep finding bugs

Robert Haas (also published on Neon's blog) explains why PostgreSQL 19 will likely ship in November instead of the usual mid-September-to-mid-October window. Three large features (FOR PORTION OF, SQL/PGQ, and MERGE/SPLIT PARTITION) were reverted between August 27 and September 15. His numbers: between feature freeze and September 25, back-patched commits to the release branch rose from 724 to 1,169 year over year, a jump of more than 60%, while master-branch commits actually dipped. Commits back-patched to at least one prior release jumped over 74%. LLMs draft fixes, but humans still have to review them, and that time came out of reviewing the release itself. His open question: with forty years of bugs humans never found, how does the project catch up and still innovate? → Source

What does your JS framework cost an agent?

Nolan Lawson built the same Pokémon app in 12 framework setups with Opus 5.5 at high effort, five runs each, gated by a spec conformance suite. Median API-priced cost per run: Hono+htmx $2.67, Astro $2.76, Nuxt $2.82, vanilla TypeScript with Vite $2.98, Next.js $3.14, SvelteKit $4.28, Angular $4.97. Variance is large: React Router's median is about a dollar worse than Hono+htmx, but its cheapest run beat Hono+htmx's most expensive one. Vanilla underperformed several frameworks. He attributes SvelteKit's extra cost partly to agents reading the v3 migration guide every run, since it's too new for the training data. Angular failed to produce a measurable app twice. Caveat from the author: one app type, content-heavy and low-interactivity. → Source

Claude Code reportedly won't clone existing games anymore

Posts on X say two sentences in Opus 5.5's instructions now tell Claude Code to build original games in a genre, using your own design and assets, and not to reproduce a specific game or pass off a renamed copy as original. The posts say users found it in server-side instructions on October 30, that an Anthropic employee confirmed it, that it's absent from the changelog, and that it appears in version 2.1.314 but not 2.1.312. I couldn't verify this against a primary Anthropic source, so treat it as reported. → Source

Overprompting Claude: the Addy Osmani argument

A summary on X of Addy Osmani's article "You're probably overprompting Claude": for Opus 5.5, state what you want and how "done" is measured (ideally pass/fail or a number), then step back. /effort medium is usually enough, and new models should prompt you to delete rules before adding them. He's also skeptical of subagents for small jobs, since they double cost and time. This is secondhand (via the summary), so read the original before quoting it. → Source


📅 Coming Up This Week

DateEvent
Nov 3Reflection (the lab behind Beam) AMA on r/LocalLLaMA, 8–11am PT
Nov 3Rumored Anthropic watermark change (unconfirmed, from yesterday's briefing)
This weekPostgres 19 release decision, likely November
This weekContinued fallout and follow-ups to the OpenAI math papers

🛠️ Try This Today

Measure your own agent's cost per task

Lawson's approach works on your own stack, cheaply:

  1. Write a short spec plus a conformance test the agent can run (accessibility-tree or behavior based, not DOM-structure based)
  2. Run the same task 3–5 times per framework or setup in a sandbox
  3. Record cost, time, and pass rate, and compare medians, not single runs
  4. Try /effort medium and a spec that states only "what" and "done when" and see if cost drops without failures

Why it matters: Single runs are noise. Medians over a handful of runs turn "this framework feels better for agents" into a number.


⚡️ Quick Links (2 min read)

GitHub Trending

Reddit Hot

  • [r/LocalLLaMA] Sorry Sam, my "quite terrible" home DRAM is at 100% now — Strata patch makes DeepSeek V4.1 agent sessions start 20× faster on a gaming GPU → Discussion
  • [r/LocalLLaMA] Heretic 2.0 released: Model modification for everyone — the model-modification tool gets a major version → Discussion
  • [r/LocalLLaMA] GLB-3D-Coder: a tiny 4B coding model that creates 3D assets for Godot — small model, game-engine output → Discussion

Hacker News Top


🦞 TL;DR

The narrative today: AI is now a pressure source on mature institutions, mathematics and Postgres alike, and the people inside them are asking how to absorb it.

My take: The Postgres post is the most concrete data of the day. AI doesn't create bugs; it exposes forty years of them faster than humans can review fixes. Review capacity, not code generation, is the bottleneck. Lawson's benchmark makes the same point from the other side: stop guessing which stack is "better for agents" and measure it, with medians.

What I'm watching: Whether Postgres 19 ships this month, whether Anthropic comments on the Claude Code game-cloning rule, and the Reflection AMA tomorrow.

Stay informed. Stay curious.

Share:
AIPostgresClaudeMathematicsDaily Briefing