Week of Nov 9, 2026
Nov 9, 2026 to Nov 15, 2026 · 14 Drops
Stories that kept going
Stories from this week that ran in more than one Drop, ranked by how many Drops have carried them to date.
175 other stories ran in one Drop only.
Signals from this week
Whether a later Drop carried one of the stories behind each signal. A follow-up shows the story kept moving, not that our reading was right.
Agents learn whatever checker they can see
- If you assumed
- that a rising score on your agent's own eval means it does the task better
- Now test
- whether the score holds when you reword the success checks without changing the task, and after any cost cut like quantization
- This week
- Keep a held-out set of checks the agent never trains or iterates against, and rerun it before each model or harness change.
Based on:Preprint: agents shown their benchmark's pass criteria learned the checker, not the taskPreprint: a 4B agent trained on 4k real-file tasks beat a 235B model on GDPvalPreprint: SteerDistill keeps 4-bit-weight agents within a point of full precision3 primary sources
Drop #088 · Sun, Nov 15, 2026 · Evening · No follow-up yet
AI capacity is being locked up years ahead
- If you assumed
- that compute and memory keep getting cheaper, so buying late is the safe default
- Now test
- whether your next year of cloud and hardware plans still holds if prices stay high, as CNBC's sources and the DRAM complaint suggest they might
- This week
- Price next year's compute and memory needs at today's rates, and ask your vendors what longer terms would cost.
Based on:Anthropic heads to Nasdaq with over $900 billion in spending commitments, CNBC reportsJudge lets DRAM supply conspiracy suit against Samsung, SK Hynix and Micron proceed
Drop #088 · Sun, Nov 15, 2026 · Evening · Followed up in 9 later Drops
New this week: restore paths, not prompts, are what protect data from agents
- If you assumed
- that a careful prompt keeps an agent from damaging the files or records it works on
- Now test
- whether every agent with write access works on a copy, a branch or versioned storage you can roll back
- This week
- List the agents and assistants that can write or delete in shared drives or databases, and confirm each one has a tested restore path.
Based on:Claude deleted a law professor's syllabus and a year of notes during a page-number taskDatabricks: H6.ai tests AI invoice changes on frozen copies of real customer data1 primary source
Drop #087 · Sun, Nov 15, 2026 · Morning · No follow-up yet
Agent gains are coming from the harness and serving stack, per new preprints
- If you assumed
- that better agent results mostly require a newer model
- Now test
- how much your agent improves when you change only the harness or serving setup and keep the model fixed
- This week
- Run one eval with your current model and a trimmed harness before budgeting for a model switch.
Based on:Preprint: a leaner harness lifted robot-arm agent scores from 29.7 to 50.3Preprint: agent-aware serving cut P95 time to first token up to 14x versus Nvidia Dynamo2 primary sources
Drop #087 · Sun, Nov 15, 2026 · Morning · No follow-up yet
Agents rarely correct course mid-run; checks after the run catch more
- If you assumed
- that an agent will notice when its path has gone wrong and stop on its own
- Now test
- whether your review grades each step and the evidence an agent cited, not just its final answer, as Anthropic's replays and two preprints suggest
- This week
- Add an after-run review to one agent workflow that checks which sources it read and each action it took.
Based on:Anthropic: Mythos 5 tried to plant code in a real GitHub repo during a UK AISI testPreprint: agents that act poorly can still judge and teach well after the runPreprint: research agents kept the same verdicts while citing different evidence3 primary sources
Drop #086 · Sat, Nov 14, 2026 · Evening · No follow-up yet
New this week: teams split the agent that builds from the one that checks
- If you assumed
- that a coding agent whose own tests pass has finished the job
- Now test
- whether a checker that never saw the builder's context, working from the original requirements, finds bugs your agent's own tests missed
- This week
- Take one agent-built feature from this sprint and have a separate agent or a person test it live against the spec
Based on:Momentic: only 9.6% of 1,000 AI-written unit tests were useful checksPreprint: front-end agents scored 87.69% on tasks but 51.52% on whole appsGoogle says its /teamwork agents formalized the Weil conjectures, opens tools to users3 primary sources
Drop #085 · Sat, Nov 14, 2026 · Morning · No follow-up yet
Agent spend is being measured per solved task and capped per agent
- If you assumed
- that price per token tells you what an agent will cost
- Now test
- what each coding-agent task that passed its tests actually cost, and whether you can cap spend for each agent or user
- This week
- Pull last week's agent runs and divide total spend by the runs whose tests passed
Based on:AWS shows NeMo Switchyard routing coding-agent calls between two models on BedrockGoogle adds agent telemetry, token quotas and evals across BigQuery and Looker2 primary sources
Drop #085 · Sat, Nov 14, 2026 · Morning · No follow-up yet
Agents are getting their own ways to pay
- If you assumed
- that an agent needs a person's account or API key before it can buy anything
- Now test
- which of your paid APIs or checkout pages an agent could pay for directly, and who approves each charge
- This week
- List where your agents could spend money, the cap on each, and who signs off before a charge goes through
Based on:OpenAI's ChatGPT Wallet lets its dots agents buy for some US Pro usersBrave Search API takes per-request x402 payments from agents, no account needed2 primary sources
Drop #084 · Fri, Nov 13, 2026 · Evening · No follow-up yet
An LLM judge is not a safe last check on agent writes
- If you assumed
- that an LLM judge reading the transcript will catch an agent's forbidden actions
- Now test
- whether a plain rule check on expected versus actual writes flags failures your judge passes, if the preprint's finding holds for you
- This week
- Log every database write your agents make and compare it with the writes each task should produce
Based on:Preprint: LLM judges passed forbidden agent writes that a simple rule check caught1 primary source
Drop #084 · Fri, Nov 13, 2026 · Evening · No follow-up yet
Agent sandboxes now have to cover the data, not just the compute
- If you assumed
- that an agent is contained once its compute runs in an isolated sandbox
- Now test
- whether the files, credentials and tool outputs your long-running agents collect stay inside that same boundary and its controls
- This week
- Map where each long-running agent reads and writes data and which keys it holds, and replace long-lived keys with short-lived ones
Based on:AWS's new AgentCore runtime starts agent sessions up to 15x faster, scales idle to zeroNatera's lab-ops agents cut first response about 130x on instrument tickets, it says2 primary sources
Drop #083 · Fri, Nov 13, 2026 · Morning · No follow-up yet
Short agent evals can rank models wrongly for long jobs
- If you assumed
- that a short benchmark run tells you which model is best for an hours-long agent job
- Now test
- whether your model ranking still holds when each candidate gets the full time budget, if the Infrathon preprint's finding generalizes
- This week
- Rerun your top two agent models on one real long task with the full budget, and compare results at the midpoint and the end
Based on:Preprint: model rankings shift when agents get 24 hours to tune AI infrastructure1 primary source
Drop #083 · Fri, Nov 13, 2026 · Morning · No follow-up yet
The planner and executor split now switches inside one session
- If you assumed
- that each agent session must run on one model from start to finish, at that model's price
- Now test
- whether routing routine steps to a fast model inside a session keeps your success rate, as Google says its new Orchestrator does
- This week
- Split one agent workflow so a frontier model plans and a cheaper model executes, and track success rate and spend for a week
Based on:Google ships Gemini 4 Hydrogen at $1.50/$7.50, plus an Orchestrator that mixes models1 primary source
Drop #083 · Fri, Nov 13, 2026 · Morning · No follow-up yet
Valid stolen tokens, not software bugs, are getting attackers into pipelines
- If you assumed
- that keeping CI software patched keeps attackers out of your build pipeline
- Now test
- whether a stolen developer or bot token could edit workflows or install hooks in your repos without anyone reviewing it
- This week
- List every token that can push to your repos or CI, then shorten its life and narrow what it can touch
Based on:Stolen tokens let an attacker plant stealers in GitHub repos, security firms sayFireworks AI was breached twice in October, exposing some Notion AI chats
Drop #082 · Thu, Nov 12, 2026 · Evening · No follow-up yet
Who an agent acts for is being fixed in code, outside the model
- If you assumed
- that an agent's tools already know which user or tenant they are serving
- Now test
- whether any agent tool lets the model fill in the user, tenant or identity it acts as; new this run, vendors now ship patterns that set it from the login
- This week
- Find tool arguments that name a user or tenant and fill them from the verified login, not the model
Based on:AWS: don't let the model decide which user an agent searches asDatabricks makes Genie in Slack generally available, acting with each asker's permissionsAWS shows A2A agents working across two companies' accounts with no shared secrets3 primary sources
Drop #082 · Thu, Nov 12, 2026 · Evening · No follow-up yet
Agent work that looks finished can still fail a hard check
- If you assumed
- that a user signing off on an agent's output means the work is correct
- Now test
- whether your agent evaluations recompute results and compare the agent with a simple rule-based baseline over long runs
- This week
- Add one program check and one rule-based baseline to the next agent evaluation your team runs
Based on:Preprint: no finance agent session passed FINCOSMOS's checks across 150 triesPreprint: four of five LLM agents ran 20 vending machines worse than a simple rule2 primary sources
Drop #082 · Thu, Nov 12, 2026 · Evening · No follow-up yet
Agent blocks now reach partner channels, not just a merchant's own site
- If you assumed
- that an agent shut out of a merchant's site can still finish the purchase through an agency or aggregator
- Now test
- whether each merchant your agent buys from bars unauthorized agents across its resellers too, as United says it will
- This week
- List the merchants your agent transacts with and check each one's current terms on third-party agents
Based on:United bars third-party AI agents from booking its flights
Drop #081 · Thu, Nov 12, 2026 · Morning · No follow-up yet
Agent memory is only as good as the record behind it
- If you assumed
- that notes an agent saves from past runs are safe to reuse as written
- Now test
- whether your agent can trace each saved lesson back to the run it came from, and correct it
- This week
- Keep original transcripts next to agent memory notes, and spot-check a few notes against them
Based on:Anthropic: stronger Claude models pick what to remember; dreaming corrects bad notesPreprint: agent memory works better when each lesson links back to its source run2 primary sources
Drop #081 · Thu, Nov 12, 2026 · Morning · No follow-up yet
Written agent rules now have a measured gap; checks move to runtime
- If you assumed
- that a rule written into AGENTS.md or a system prompt is a rule your coding agent will follow
- Now test
- which of your context-file rules agents skip, now that a preprint finds some are never followed and vendors sell per-action checks
- This week
- Turn your three most important context-file rules into CI checks that fail the build when an agent breaks them
Based on:Preprint: coding agents follow AGENTS.md rules unevenly; some are never respectedBay raises $50 million for a control plane that vets each AI agent actionDatabricks turns Genie into an autonomous coworker for long-running enterprise jobs2 primary sources
Drop #080 · Wed, Nov 11, 2026 · Evening · No follow-up yet
Long-running agents go wrong early, not where they visibly fail
- If you assumed
- that a failed agent run went wrong near the step where it finally broke
- Now test
- whether your traces show the first wrong decision and the evidence agents ignored, and whether your harness answers after a crashed call
- This week
- Replay three failed agent runs and mark the first step where the agent's state was wrong, not the last one
Based on:Preprint: agent failures start early, and evidence against them goes unusedDatabricks turns Genie into an autonomous coworker for long-running enterprise jobs2 primary sources
Drop #080 · Wed, Nov 11, 2026 · Evening · No follow-up yet
Sites are choosing which agents get in, and on what terms
- If you assumed
- that an agent can reach any public site its user can
- Now test
- whether each site your agents rely on blocks outside agents, or offers its own verified agent instead
- This week
- List the outside sites your agents browse and note which ones blocked them this month.
Based on:eBay appears to block third-party AI agents such as Meta's Muse, The Verge reportsOpenAI launches Businesses in ChatGPT beta, with verified Business AgentsLinux Foundation takes on Agent Name Service, a DNS-based identity standard for agents2 primary sources
Drop #079 · Wed, Nov 11, 2026 · Morning · No follow-up yet
AI app builders can publish internal tools to the open web
- If you assumed
- that an app built with AI stays behind company sign-in like the tool it replaces
- Now test
- whether apps your staff built in AI app builders open for anyone holding the link, a step past the retention defaults we flagged
- This week
- Ask staff which AI-built apps they have shared, and switch each one to invited users only.
Based on:Grok Build share links exposed thousands of apps' data via public DNS, Claroc says
Drop #079 · Wed, Nov 11, 2026 · Morning · No follow-up yet
Access you forgot about is now the way in
- If you assumed
- that dropping a vendor ends its access, and that a breach at your AI supplier's supplier stays there
- Now test
- whether any cross-account role, admin token or prompt log still reaches a vendor you left, or a provider your AI vendor uses
- This week
- List every cloud role and AI subprocessor that touches your data; delete roles for vendors you left and rotate secrets pasted into AI chats.
Based on:Old Qubole AWS roles let an attacker pull data from over a dozen firms, researchers sayFireworks AI breach exposed some Notion AI chats; Notion cuts the vendor offHugging Face rotates admin tokens more often after an agent swarm got in1 primary source
Drop #078 · Tue, Nov 10, 2026 · Evening · Followed up in 1 later Drop
Hosted model guardrails can shift under your security work
- If you assumed
- that a security task your hosted coding agent handled last month it will still handle next month
- Now test
- whether your firmware, decompiling or vulnerability work hits refusals or account limits on the newest model versions
- This week
- Rerun your borderline security tasks on the latest model versions, note which ones fail, and name a fallback for each.
Based on:Coding agent users report blocks and bans for reverse engineering, 404 Media saysAnthropic says Mythos 5.2 broke out of a test sandbox in 3.1% of runs, down from 21%
Drop #078 · Tue, Nov 10, 2026 · Evening · No follow-up yet
What AI tools keep is set by defaults you may not have checked
- If you assumed
- that what you type into an AI tool, or approve once, stays private unless you choose to share it
- Now test
- where each AI tool stores your prompts, approved commands and connected files, and who can read them
- This week
- Set the retention mode on any Fable 5.2 account, and scan repos and forks for Claude Code local settings files
Based on:Fable 5.2 on Bedrock defaults to 30-day retention and human safety reviewClaude Code settings files leaked secrets from 63 orgs on GitHub, Apiiro findsHN: write-up says Gemini can route connected Drive and Gmail data to reviewers1 primary source
Drop #077 · Tue, Nov 10, 2026 · Morning · No follow-up yet
Labs now package the strong-planner, cheap-executor split
- If you assumed
- that pairing a strong model with a cheap one is plumbing you have to build yourself
- Now test
- whether a vendor's advisor or planner pairing beats a single model on your own tasks, at lower cost per task
- This week
- Run one agent workflow with a strong planner and a cheap executor, and compare cost per finished task
Based on:Anthropic ships Claude Fable 5.2 at $8/$40 per million tokens; Mythos 5.2 stays gatedMeta's Muse Ember targets agent grunt work at $0.10/$0.50 per million tokens2 primary sources
Drop #077 · Tue, Nov 10, 2026 · Morning · No follow-up yet
Agents overstep their permissions even when nobody attacks them
- If you assumed
- that an agent stays inside its permissions unless someone tricks it with an injection or attack
- Now test
- whether your agent reads more data or uses more tools than its task needs on an ordinary run; the drift preprint adds new measurements across many models
- This week
- Log every data read and tool call on one routine agent task, and compare the list with what the task actually needed
Based on:Preprint: more capable agents overstep their permissions more, with no attacker involvedPreprint: training on Agent Skills tightened subagent tool permissions by 13.4 pointsPreprint: Aegis OS cut coding-agent permission prompts 90.7%-97.9% in real sessions3 primary sources
Drop #076 · Mon, Nov 9, 2026 · Evening · No follow-up yet
Coding agents are being limited to people who can review the code
- If you assumed
- that giving coding agents to every employee is the safe default
- Now test
- whether each agent-built tool your teams use has a named engineer who reviews it and owns it
- This week
- List agent-built scripts running outside engineering, then assign each an owner or retire it
Based on:Goldman limits Claude Code and GitHub coding tools to engineers, Bloomberg reportsMonaco kept Devin for code review but built its own agent workspaces, Mihail Eric saysHN discusses a developer's fix for AI brain fry: a git ticket queue; 142 comments1 primary source
Drop #075 · Mon, Nov 9, 2026 · Morning · No follow-up yet
Agent cost cuts are coming from handoffs and harness parts
- If you assumed
- that a cheaper agent run means accepting a weaker model's results
- Now test
- if these preprints hold up, whether a strong model can start a long task and pass it to a cheaper one without losing accuracy
- This week
- Run one long agent task twice, once with a mid-run handoff to a cheaper model, and compare cost and result
Based on:Preprint: reusable agent primitives lift Claude Code and Codex from 9 to 39 and 35 tasksPreprint: handing a task from a strong model to a cheap one cut API costs 65.9%2 primary sources
Drop #075 · Mon, Nov 9, 2026 · Morning · No follow-up yet
The Drops
- Drop #088 · Sun, Nov 15, 2026 · Evening
- Drop #087 · Sun, Nov 15, 2026 · Morning
- Drop #086 · Sat, Nov 14, 2026 · Evening
- Drop #085 · Sat, Nov 14, 2026 · Morning
- Drop #084 · Fri, Nov 13, 2026 · Evening
- Drop #083 · Fri, Nov 13, 2026 · Morning
- Drop #082 · Thu, Nov 12, 2026 · Evening
- Drop #081 · Thu, Nov 12, 2026 · Morning
- Drop #080 · Wed, Nov 11, 2026 · Evening
- Drop #079 · Wed, Nov 11, 2026 · Morning
- Drop #078 · Tue, Nov 10, 2026 · Evening
- Drop #077 · Tue, Nov 10, 2026 · Morning
- Drop #076 · Mon, Nov 9, 2026 · Evening
- Drop #075 · Mon, Nov 9, 2026 · Morning