Skip to content
LiveNext 12:52:42
Today's five/N°4 · Friday, October 9, 2026/Filed 04:49 ET

AI news today: Claude builds live dashboards, Google launches its Gemini agent

Two launches worth judging by their controls, one Claude policy to read before November 12, and a revenue number that was never a scoreboard.

The five · ranked by consequence

Permalink ↗
  1. Claude now builds live dashboards from your warehouse

    Anthropic put Claude Dashboards into beta for paid plans on Thursday, connected to Snowflake, BigQuery, Databricks and Redshift, plus Motion explainer videos for Team and Enterprise. Dashboards is the one to try, because every number opens to the query behind it.

    Why it matters If you rebuild the same numbers every Monday, this is the first Claude feature that can take that job, and you can audit every chart down to its query. Docs, Slides and Design also left beta on every plan, Free included.

    SRCAnthropic

  2. Google launches Gemini agent, and it runs Claude too

    Google Cloud unveiled the Gemini agent on Thursday, one agent for chat, long-running tasks and code that routes each job to Gemini or Anthropic's Claude models. Google gave no price and no general availability date, so plan for it but don't budget for it yet.

    Why it matters If your company runs on Workspace, Google just described the agent that will sit in your Gmail and Docs, with spend caps that pause it at a budget line. Get the preview terms from your Google account team before you sign another agent contract.

    SRCGoogle Cloud

  3. Anthropic's new Claude rules ban surveillance tools

    Anthropic published a revised Usage Policy on Thursday, effective November 12, that bans building surveillance tools, extends the weapons ban to arming drones and adds a rule against cruelty to its models. The cruelty rule got the headlines. The surveillance and policing rules are the ones that can end a product.

    Why it matters If your Claude app tracks people, flags them for investigators or drives hardware, read the new text before November 12. If you build campaign tools, one door opened: the blanket ban on personalized vote and campaign targeting is gone.

    SRCAnthropic

  4. OpenAI's revenue run rate is near $50B, not $70B

    OpenAI told investors its annualized revenue is approaching $50 billion, the Financial Times reported, per TechCrunch on Thursday, about $20 billion below the figure that circulated a week earlier. The gap comes from how the number was counted, and it makes every AI run-rate comparison suspect.

    Why it matters If you pick an AI vendor partly on who looks like they're winning, stop using run rates as the scoreboard. OpenAI and Anthropic count partner sales differently, so their headline numbers can't be lined up side by side.

    SRCTechCrunch

  5. CrowdStrike says an AI pentest agent hit Korean banks

    CrowdStrike says a likely Chinese-speaking, financially motivated actor ran ARTEX, an open-source agentic pentest tool, against South Korean financial firms from late September, and cites industry reports of breaches at two banks. The model under it was swappable, and that is the warning.

    Why it matters The attacker didn't need one lab's best model: ARTEX ran mainly on DeepSeek, with GLM and Grok in other sessions. If you run internet-facing services, assume agent-speed reconnaissance and shorten the gap between a patch shipping and a patch applied.

    SRCCrowdStrike

Prompt of the day

Turn your weekly hand-built report into a dashboard spec

› I want to replace a report I build by hand every week with a dashboard that updates itself. Here is the report and how I make it now:

[paste the report, or describe it: the numbers, the charts, where each number comes from, who reads it]

Do four things:
1. List every number in the report. For each one, write a plain-English definition, the system or table it comes from, and the exact filter and time window. Flag any number whose definition is ambiguous and ask me one question about it.
2. For the three numbers my reader cares about most, draft the query. If you don't know my database, write the query as plain steps I can hand to whoever does.
3. Propose a layout: what sits at the top, which chart type for each number, how often it should refresh, and what the "last refreshed" label should say.
4. Write a checklist I can run against last week's manual report to prove the dashboard matches before I trust it.

Be blunt about which parts of my current report shouldn't be automated, and why.

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
4
Stories ranked
20
Topics tracked
10
Terms defined
14
AprMayJunJulAugSepOct
EditionNo editionTodayFull archive →

Speak fluent AI.

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

The glossary →