Today's content splits cleanly between 2 consequential topics: an AI cybersecurity arms race that's developing genuinely interesting economic dynamics, and a rare, unusually candid technical postmortem from Notion on what it actually took to ship production agents.

OpenAI's GPT-5.4-Cyber release is being framed as a direct counter to Anthropic's Mythos — and the contrast in access philosophy is real. Anthropic gates Mythos to roughly 40 trusted partners; OpenAI is opening GPT-5.4-Cyber to any verified defender who passes ID checks via its Trusted Access for Cyber program. OpenAI researcher Fouad Matin put it directly: "no one should be in the business of picking winners and losers" on who gets to defend their systems.

Simon Willison adds useful nuance here: the "democratized" framing is somewhat overstated. Getting access to OpenAI's best security tooling still requires a separate Google Form application process — not obviously different from Anthropic's Project Glasswing gating. The rhetoric of openness is ahead of the operational reality.

What's more interesting than the access policy debate is the underlying economics Willison surfaces from Drew Breunig. The UK AI Safety Institute independently confirmed Mythos completed their 32-step corporate hack simulation and found that results kept improving as long as you kept spending tokens on it — no apparent ceiling. If that holds, security work collapses to a brutal arithmetic: to harden a system you need to outspend attackers on token consumption, not outthink them. This is security as proof-of-work.

The downstream implication Breunig flags is counterintuitive: open source libraries become more valuable in this regime, not less. The tokens spent securing an open source library amortize across every user of that library. This directly counters the vibe-coding argument that cheap throwaway implementations make established open source projects obsolete — the security economics now favor shared, audited codebases. It's the kind of second-order effect that's easy to miss when the headline debate is about which company has the more capable model.

Meanwhile, SWE-Bench is reportedly saturating (Swyx notes Mythos is at 78% on SWE-Bench Pro), and GDPval rates GPT-5.4 as better than or equal to human experts in 83% of economic domains tested. Greg Brockman is claiming ~1B weekly ChatGPT and Codex users. The benchmark frontier is moving fast enough that Notion, Anthropic, and OpenAI are all independently building "frontier evals" that intentionally only pass ~30% of the time — so they can see where capabilities are headed, not just confirm they haven't regressed.

The Latent Space interview with Notion's Simon Last and Sarah Sachs is the most technically substantive piece in today's content. Notion shipped Custom Agents after rebuilding the system 4-5 times over roughly 3.5 years. The history of those rebuilds reveals more about the current state of agent engineering than most benchmark announcements.

Rebuild 1 (late 2022): A JavaScript coding agent. Give the model JavaScript APIs and let it write code to invoke tools. Failed because the models at the time were too weak at code generation to make it reliable.

Rebuild 2: Custom XML tool calling (before the standard existed), with a schema designed to losslessly map to Notion's internal block data model. The learning: they were catering to what made sense for Notion's data model rather than what the model wanted. Models don't know bespoke XML. Switch to markdown.

Rebuild 3: Notion-flavored markdown for page editing, plus SQL Lite queries for database access instead of Notion's native JSON query format. Models are excellent at SQL; they were terrible at Notion's internal JSON schema. Give models what they already know.

Rebuild 4 (current production): Tool definitions with progressive disclosure. The big architectural shift was moving from centralized few-shot prompts (where 5-6 people were the gatekeepers of a single string in the codebase, and prompt ordering mattered enormously) to distributed tool ownership. Every team now owns their own tool definitions and evals. This unlocked velocity but introduced new failure modes: two tools with the same name caused Claude Sonnet to crash but GPT-5.4 to handle gracefully. They discovered this through a production incident.

Next version (landing shortly): 100+ tools with proper progressive disclosure — the model sees a search interface into the tool library rather than all 100 definitions simultaneously. The insight that motivated this: adding any new tool risked "Nerfing" the overall model quality by causing it to over-call the new tool.

Several engineering decisions stand out as generalizable. On MCP vs CLI: Simon Last is bullish on CLI agents because CLI is self-healing — if something breaks, the agent can debug and fix itself within the same environment. If an MCP transport gets corrupted, the agent loses the tool entirely with no recovery path. MCP's advantage is tighter permissioning and determinism for narrow, well-scoped tasks. Sarah Sachs adds a pricing dimension: using a language model to call deterministic APIs via MCP repeatedly is wasteful; if you can replace it with a one-time CLI tool, you should. This shapes which integrations Notion builds natively (Slack, Mail, where they want full control and quality) versus via MCP (long-tail third-party tools).

On evaluation infrastructure: Notion runs 3 tiers. Regression tests in CI with stochastic error tolerance. Launch-quality evals with target pass rates (80-90% depending on journey). And "frontier evals" intentionally set at 30% pass rate — these exist specifically to give Anthropic and OpenAI signal on where models need to improve, and to let Notion see where the capability river is flowing. They hit a point where their production evals were saturated and stopped being useful for feedback. The solution was what they're calling "Notion's Last Exam."

The Model Behavior Engineer role is worth flagging for practitioners. It started as someone reviewing Google Sheets of model outputs (a linguistics PhD dropout and a Stanford grad). It's evolved into a function distinct from software engineering: writing evals, triaging failures, running LLM judges, understanding why a model fails in a specific domain. They're now building agents to automate the eval pipeline itself — coding agent writes evals, runs them, analyzes failures, proposes fixes. The humans supervise the outer loop.

On pricing: credits as an abstraction over tokens was necessary because tokens aren't the right unit — web search, GPU-served fine-tuned models, priority serving tiers, and sandbox compute all have different cost structures. The "auto" model selector is positioned as a robo-advisor: matching task complexity to the minimum sufficient model, not the cheapest or most powerful. Sarah Sachs is explicit that frontier labs don't currently serve the middle of the intelligence-price-latency triangle well — everything clusters at capability extremes — and Notion is filling the gap with open-source models that are reaching where reasoning models were 3-4 months ago.

Swyx surfaces something worth sitting with: agents are doing more work, everyone is working harder, and both things are simultaneously true. Aaron Levie reports AI teams are the busiest they've ever been. Tyler Cowen argues you should work harder right now regardless of which AI trajectory you believe. Simon Last described going back to sleepless nights not because of ML training runs but because of agent token anxiety — before bed, did he start enough agents to keep making progress while he sleeps?

The turkey analogy Swyx raises is pointed: based on historical data, turkeys should conclude that humanity exists to feed them well. The doomsayers are crackpots. Until Thanksgiving. Are knowledge workers turkeys? The question is whether current increasing demand for human oversight and orchestration is structural or transitional — whether the elasticity of human-in-the-loop work keeps growing, or whether there's a crossover point.

Notion's position implicitly argues for a structural role: someone has to own the outer loop. Sarah Sachs describes software engineers going through "the identity crisis every manager goes through" — realizing their ability to write code matters less than their ability to delegate and context-switch. Simon Last's framing is sharper: managing a team of humans is fuzzy and human, but managing a system of agents is a rigorous technical design problem — PRs in block status, dependency graphs, self-verification loops. The job doesn't go away; it changes shape into something that requires more technical rigor about systems design and less about syntax.

Whether that reframing holds through the next capability jump is the open question the day's content doesn't resolve.

TL;DR - OpenAI's GPT-5.4-Cyber vs. Anthropic's Mythos represent genuinely different access philosophies for dangerous-capable models, but the more durable insight is economic: AI security becomes proof-of-work, and open source amortizes the token cost of hardening. - Notion's five-agent-harness rebuilds over 3.5 years document the actual engineering path to production agents: give models formats they know (SQL, markdown), distribute tool ownership away from a central few-shot file, build progressive disclosure for 100+ tools, and treat eval-writing as a distinct engineering function. - The "everyone is working harder while agents do more" paradox is real and unresolved — Swyx's turkey framing and Notion's "software factory" vision point in the same direction but don't agree on whether the human role is structurally stable or transitionally stable.