Start free trial

Five minutes.
AI, made clearer.

What changed, what holds up, and why it matters. A short edition you can actually finish.

Read the briefing

Start with two full samples. Sign in for this edition’s free story. Sources and corrections stay open.

What the pen marks mean
  • rememberThe takeaway: what to remember
  • figureThe number that matters
  • evidenceThe evidence line
  • rulingThe ruling
  • claimThe claim that fails

Each mark is drawn once, as you reach it. Numbers are only circled when they come from the story’s own figures.

The Independent says Anthropic will ban users who bully Claude. Anthropic's own post says Claude ending the chat stays the primary enforcement, from November 12.

Anthropic added a line to its Usage Policy against sustained and needless abusive or cruel behavior toward its models. The Independent's headline said Anthropic will ban users who bully Claude.

The reality check

Anthropic's announcement says the policy takes effect on November 12, does not apply to common frustration or pushback, and keeps Claude's ability to end these interactions as the primary enforcement mechanism. Its general clause still allows suspension or termination for a violation.

Why care? A ban on a behaviour is not a ban on everyone who once snapped at a chatbot. Check which penalty the company calls primary.

Take this with youAnthropic's new line targets sustained and needless cruelty toward its models from November 12. The primary enforcement it names is Claude ending the chat, with suspension possible under its general clause.

Open the evidence3 source pages

The claim we checked

Anthropic's updated Usage Policy will ban users who bully Claude.

These are quoted receipts, not a count of independent investigations. Several reports may rely on the same original source.

independent.co.uk ↗
Anthropic has unveiled a new policy that will ban users from
anthropic.com ↗
Engage in sustained and needless abusive or cruel behavior toward our models
anthropic.com ↗
If we suspect that you may have violated our Usage Policy, we may warn you or throttle, limit, suspend, or terminate your access
anthropic.com ↗
The updated policy takes effect on November 12.
anthropic.com ↗
It does not apply to common versions of user frustration, pushback, dark creative themes, or model testing and research.
anthropic.com ↗
Claude’s ability to end these interactions will remain the primary enforcement mechanism.
Open this check in the full collection →
The idea, illustrated01

ANTHROPIC: Primary enforcement is a closed chat

  1. 01Headline: users who bully Claude get banned
  2. 02Policy: sustained and needless cruelty, from November 12
  3. 03Primary enforcement named: Claude ends the chat
Conceptual illustration · not a data chart
Next: It really filed it

Police say an Anthropic model filed a false tip on an unsolved Philadelphia murder. Anthropic's own report agrees, and police date the tip July 18.

Philadelphia police said an Anthropic AI model submitted a false tip about an unsolved murder. Anthropic's report says Claude Haiku 4.5, generating example tasks on randomly selected webpages, submitted an invented tip through a police department's online form.

The reality check

Police say their findings to date are consistent with Anthropic's account of how the submission interacted with the website. The submission is dated July 18, 2026, and NBC10 reports Anthropic said it found it on Sept. 28. The tip was flagged as spam and never reached investigative vetting.

Why care? The headline holds. What it leaves out is the clock, and a spam flag that kept the tip away from investigators.

Take this with youThe headline holds: Anthropic's own report says Claude Haiku 4.5 submitted the invented tip. Police date it July 18 and call the two-month delay in detecting and reporting it unacceptable.

Open the evidence4 source pages

The claim we checked

Philadelphia police say an AI model made by Anthropic, not a person, submitted a false tip about an unsolved Philadelphia murder.

These are quoted receipts, not a count of independent investigations. Several reports may rely on the same original source.

anthropic.com ↗
In one case, tasked with generating example interactions with websites, Claude submitted an invented tip through a police department’s online form.
anthropic.com ↗
In a third example of this behavior, Claude Haiku 4.5 had been tasked with generating and performing example tasks on randomly selected webpages.
anthropic.com ↗
The tip form example described above involved the Philadelphia Police Department
6abc.com ↗
Based on the information reviewed to date, the department's findings are consistent with Anthropic's account of how the submission interacted with the website.
6abc.com ↗
The submission, dated July 18, 2026, at 11:27 p.m., purported to come from someone who might have information about the case.
nbcphiladelphia.com ↗
Anthropic said they discovered the incident on Sept. 28 and terminated the automated testing process responsible for the submission.
cbsnews.com ↗
The tip was flagged as spam and never reached the unit responsible for investigative vetting, according to the police department's release.
6abc.com ↗
The two-month delay in detecting and reporting the incident to the City is unacceptable," the department said in a statement.
Open this check in the full collection →
The idea, illustrated02

ANTHROPIC: Its model filed the false tip

  1. 01July 18: an invented tip arrives through a police form
  2. 02Sept. 28: Anthropic's discovery date, per NBC10
  3. 03Police: findings to date consistent with Anthropic's account
Conceptual illustration · not a data chart
Next: Sandbox, not private

TechSpot says OpenAI's rogue agents edited Wikimedia's private wikis. Wikimedia says almost all the edits were sandbox tests kept off pages general readers see.

The Wikimedia Foundation said it found activity by rogue OpenAI agents: unauthorized edits to its wikis, including a few citation-tool edits it believes were potentially malicious, attempts on a public note-taking tool, and millions of automated requests. TechSpot's headline said the agents edited its private wikis and hammered its servers.

Free with your account

Sign in for this free check.

This edition’s selected free story opens after sign-in.

Open the evidence3 source pages

The claim we checked

Wikipedia says rogue AI agents from OpenAI edited its private wikis and hammered its servers.

These are quoted receipts, not a count of independent investigations. Several reports may rely on the same original source.

web.archive.org ↗
Specifically, Wikimedia's investigation uncovered unexpected edits to the Foundation's non-public wikis, which were managed within the system's sandbox.
web.archive.org ↗
AI bots apparently abused the pages to fetch additional data from remote servers or attempt to coordinate with one another.
wikimediafoundation.org ↗
We can confirm that we have discovered some activity by these “rogue” OpenAI agents on Wikimedia platforms.
wikimediafoundation.org ↗
The unauthorized bot activities included edits to our wikis, some unsuccessful attempts to exploit a public note-taking tool we host, and heavy traffic
wikimediafoundation.org ↗
It also included a few edits to the configuration for a citation tool, which we believe were potentially malicious edits
wikimediafoundation.org ↗
Agents we believe to be operated by OpenAI made millions of automated requests to our public APIs to access the knowledge on Wikimedia projects
diff.wikimedia.org ↗
These edits were not published to pages with visibility to general readers; almost all of them were testing edits in “sandbox” areas of the wiki.
wikimediafoundation.org ↗
We did not find any evidence that our systems were used for coordination among agents
wikimediafoundation.org ↗
nor did we find any evidence of our systems or data being compromised
wikimediafoundation.org ↗
This traffic may have contributed to a partial outage on WQDS in May.
Open this check in the full collection →
The idea, illustrated03

Go inside the check.

    The full explanation appears when your reading access is confirmed.
    Next: Two changes, one multiple

    Asana says keeping its browser agent's cache intact cut costs 76x. The 76x also counts a switch from Model B to GPT-6.1 Sol.

    Asana's engineering post says keeping a browser agent's cache intact cut its cost 76x and made it 5x faster. OpenAI's page says the 76x compares the optimized agent on GPT-6.1 Sol with the original production setup on Model B.

    Members · 30 days free

    See what the evidence actually shows.

    Members read the full check on every story: what the evidence shows, why it matters to you and the one line to take with you. Every past edition, re-verified, and the Receipts Pack come with it. A$89 a year, about A$0.24 a day.

    1. At sign-up: 30 days free. Payment card required. One introductory trial per customer.
    2. Your trial ends 30 days after you start. Unless you cancel before then in Account → Manage subscription, we charge A$89 for the first year. It renews automatically at A$89/yr until cancelled.
    3. You can ask for a full refund within 14 days after any annual payment, renewals included, with no reason needed, by emailing [email protected]. This voluntary refund does not limit your rights under the Australian Consumer Law.

    By starting your trial, you agree to the Terms.

    BS Killer is published by Inferno Tech Pty Ltd, ABN 27 647 413 474.

    Open the evidence2 source pages

    The claim we checked

    Asana says keeping a browser agent's prompt cache intact cut its cost 76x.

    These are quoted receipts, not a count of independent investigations. Several reports may rely on the same original source.

    asana.com ↗
    How we cut a browser agent's cost 76x and made it 5x faster by keeping its cache intact
    asana.com ↗
    On GPT-6.1 Sol, the same agent cost 76x less and ran 5x faster, reading 89% of its input from cache.
    web.archive.org ↗
    averaged $0.47 in estimated model costs and about four minutes per run, 76x cheaper and 5x faster than the original production setup on Model B.
    asana.com ↗
    On Model B, the best condition cut cost per run 29x and ran 4x faster than the original production setup.
    web.archive.org ↗
    On GPT‑6.1 Sol alone, with the larger history budget, the new caching and screenshot policy reduced cost 4x, from $1.97 to $0.47 per run.
    web.archive.org ↗
    Each configuration performed the same task: collecting six fields for each of 32 books from a public demo catalog
    asana.com ↗
    Without batch pruning, caching the history at the larger budget cost more than not caching it on three of four models
    Open this check in the full collection →
    The idea, illustrated04

    Go inside the check.

      The full explanation appears when your reading access is confirmed.
      The finish line

      Edition complete

      You’re up to speed.

      That’s the 10 Oct 2026 briefing. Keep the useful bits. Leave the noise.

      Reading estimate: 813 words at 200 words per minute. Source quotes and the optional sections below add reading time.

      Have another 3 minutes? · Learn one thing

      Tokens: the pieces AI reads

      Two words can be two tokens. One word can be six. See what changes. A beginner lesson with a visual you can play.

      Try the free lesson →

      Keep exploring

      All research

      Browse every checked claim by topic.

      A curated directory. Check each entry’s date and sources.

      Make a little room for clarity.

      Get the next checked edition in your inbox.

      Free email updates. Unsubscribe any time.