Skip to content
LiveNext 12:46:24
Today's five/N°14 · Monday, October 19, 2026/Filed 04:48 ET

AI news today: Meta blames a Claude tool for No Kings ban, Anthropic pledges 5%

Agents now act in your name, and this weekend a platform, a court and a bank pitch each decided what that costs you.

The five · ranked by consequence

Permalink ↗
  1. Meta blames a Claude tool for No Kings Instagram suspension

    Meta says a Claude tool reading profiles, posts and hashtags at about four times the normal rate tripped its bot defenses and got the No Kings Coalition's Instagram account suspended Saturday. If your agent browses while logged in as you, Meta judges you by its pace.

    Why it matters An agent you run inside your own accounts borrows your identity and spends its reputation. Meta just showed what happens when the pace looks automated: the account goes dark first and gets reviewed later. Slow your agents down, or move their reading off the accounts you can't afford to lose.

    SRCBloomberg (via Yahoo Finance)

  2. Anthropic commits 5% of its shares to a public benefit fund

    Anthropic says it will commit 5% of its shares to a new Public Benefit Fund, subject to stockholder approval, and its board can add 2% for every 50% rise in company value. The pledge is real. The rules that decide what the fund does are not written yet.

    Why it matters If Claude is part of your work, some of the value your usage builds is now promised to labor market programs and payments to affected groups. Judge the pledge by the governance and milestones Anthropic says it will publish in the coming months. The percentage is the easy part.

    SRCAnthropic

  3. German court holds Google liable for AI Mode's answers

    A court in Aachen barred Google from repeating false AI Mode statements about a doctor, on pain of fines up to €250,000 per violation, and said Google is responsible for the answers its AI generates. In Germany, an AI's answer is now its operator's statement.

    Why it matters If your product writes about real people, two German regional courts have now treated the operator as the speaker. What turned a bad answer into a court order was a removal request Google declined to act on. Build the path from complaint to correction before a court builds it for you.

    SRCAachen Regional Court (Landgericht Aachen)

  4. World ID for banks lets AI agents prove a human sent them

    World launched World ID for banking and finance at Money20/20 on Sunday, bundling human verification, Zoom checks and AgentKit, a beta that lets an AI agent prove it acts for a real person. No bank has signed on publicly yet.

    Why it matters Banks are about to decide whether an AI agent can move your money, and what it must prove first. World wants its proof to be the answer. Until a bank adopts it, treat AgentKit as a design worth studying, and keep your agent's money moves behind your own approval.

    SRCWorld

  5. Gemini 4 Argon agents beat Minecraft in 27 hours

    Four Gemini 4 Argon agents killed Minecraft's Ender Dragon after 27 hours and 14 minutes with no human help, a new paper says, writing 2,783 programs and dying 605 times. The dragon is the headline. The stamina is the result.

    Why it matters The jobs you most want to hand to agents need them to hold a plan for a day, split the work and recover from hundreds of failures. This run shows that working, on easy settings, for about $1,040 in model time at standard prices. Price your own long jobs the same way: per finished task, failures included.

    SRCarXiv

Prompt of the day

Map every account your AI agents touch, and set their speed limits

› I use AI agents and tools that act inside my online accounts (browsing, reading, posting or buying for me). Help me find where they could get an account flagged or locked by a platform's bot defenses.

My agents and tools: [list the agents, browser extensions or automations you use]
The accounts they can reach: [list platforms and accounts, e.g. Instagram business page, Gmail, bank, Shopify]
Accounts I can't afford to lose for a day: [list]

Do this:
1. Make a table: account, which agent touches it, what it does there (read, write, buy), and how fast it likely acts compared with a person doing the same task.
2. Flag every pairing where an agent reads or acts in bursts on an account I can't afford to lose.
3. For each flag, recommend one fix: a separate account, the platform's official API, a slower pace with a concrete limit (actions per minute), or keeping the task human.
4. Tell me what you know about each platform's rules on automated access, and mark anything you are unsure of so I can check it myself.
5. Write a short recovery plan for each critical account: how to reach the platform, and what proof of ownership to keep ready.

If my lists are too vague to do this well, ask me questions first.

Works in any AI chat. In Magai, run it against several models at once.

Every day, on the record.

Each square is an edition. Click any day to read the five that mattered then.

Editions
14
Stories ranked
70
Topics tracked
10
Terms defined
62
AprJunJulAugSepOct
EditionNo editionTodayFull archive →

Speak fluent AI.

Every term our stories use, defined in plain English and linked wherever it appears.

The glossary →