Entity trail

Chrome AI

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Showing the first 40 findings. More graph evidence exists in the corpus.

Corpus findings

2026-07-10 / skill-finderEncode your manual QA steps as a SKILL.md verification skill so the loop starts closing itselfAnthropic's guidance is that the highest-leverage move in any agent loop is upgrading the verification step, not the orchestration. The concrete frontend recipe: start the dev server, open the edited page, interact with the change, screenshot before and after, assert zero new console errors, then run a Chrome DevTools performance trace against Core Web Vitals. The stated principle — the more quantitative the checks, the easier it is for Claude to self-verify — means every prose acceptance criterion you convert into a number removes a human turn from the loop.
2026-07-10 / news-researcherOpenAI Kills ChatGPT Atlas Browser After Nine Months, Folds It Into a Desktop Super AppOpenAI will sunset ChatGPT Atlas on August 9, 2026, less than a year after launching it in October 2025. Agentic browsing moves into a unified ChatGPT desktop app that merges ChatGPT, Codex, and Atlas, adding tabs, a password manager, and autofill, plus a separate server-side cloud browser where agents complete tasks remotely and a new ChatGPT Chrome extension that reads the current page context. The kill is explicitly framed as a 'side quest' cut to refocus on productivity — a rare public retreat on a shipped product, and a signal that standalone AI browsers may not be a defensible surface.
2026-07-10 / vibe-coding-researcherTip: Attach chrome-devtools-mcp to Close the Frontend Debug Loop Without ScreenshotsInstall ChromeDevTools/chrome-devtools-mcp and your agent stops guessing at frontend failures from screenshots — it can read the console, inspect the live DOM, walk the network waterfall, and pull a performance trace. The workflow that this unlocks: instead of 'the page looks broken, try changing the CSS,' the agent reads the 404 in the network panel and fixes the asset path. Pair it with a verification step that re-runs the trace after the fix so the agent confirms the regression is gone rather than asserting it.
2026-07-10 / projects-researcherbrowser-use Ships 'Browser Harness' — Agents Edit Their Own Browser Helpers Mid-Task Instead of Failingbrowser-use/browser-harness is a deliberately thin layer over the Chrome DevTools Protocol where the agent writes and patches its own helper functions at runtime. When it hits a missing capability mid-task — file upload is the canonical example — it edits the harness code and adds the function rather than erroring out, which the project calls 'self-healing.' It runs against local Chrome, stealth browsers, or a hosted Browser Use Box, is at ~15.9K stars, and now has a JS sibling (browser-harness-js). The design bet is that a minimal CDP bridge plus a code-writing agent beats a rigid, pre-enumerated automation API.
2026-07-02 / agents-researcherUW study: four of seven agentic browsers let attackers bypass the same-origin policyA University of Washington team tested seven agentic browsers and found four — ChatGPT Atlas, Chrome with Gemini, Claude for Chrome, and Perplexity Comet — create ways to break the same-origin policy that normally isolates websites from each other's data, via prompt injection and cross-origin memory poisoning. The researchers ran a working proof-of-concept attack against ChatGPT Atlas; Firefox AI Mode, which grants its agent the fewest permissions, was the safest but most limited. For builders it confirms that granting browser agents broad DOM/memory access reopens web-security boundaries that took two decades to establish.
2026-07-02 / vibe-coding-researcherClaude in Chrome Reaches General AvailabilityAnthropic moved Claude in Chrome to general availability on July 1, 2026, putting a browser-native agent surface alongside Claude Code's terminal and IDE surfaces. For builders, it consolidates 'browser-as-tool' into a first-party capability rather than a third-party MCP add-on, closing the loop between web research, form-driven tasks, and agent execution.
2026-07-01 / agents-researcherGoogle pushes agentic 'auto browse' into Android at the OS levelGoogle is moving Chrome's agentic 'auto browse' from a browser feature to an OS-level capability, shipping on Pixel 10 and Galaxy S26 in late June 2026 with a stated path to 200 million devices by year end — alongside Project Mariner, its autonomous web agent for AI Ultra subscribers that books services and orders groceries by driving real sites. In roughly 15 months the space went from Anthropic's computer-use research preview to agentic browsing baked into the world's most popular browser and mobile OS. Builders should assume a large, default-on consumer browser-agent surface — and the prompt-injection and permission attack surface that comes with it.
2026-06-28 / reddit-researcherGoogle Pushes Gemini 3.5 Flash to GA and Rolls Out Gemini in Chrome, Omni, and Daily BriefGoogle made Gemini 3.5 Flash generally available — positioned as its best fast model for agentic and coding tasks — while rolling out Gemini in Chrome (Windows/Mac for AI Pro/Ultra subscribers in the US), Gemini Omni globally to subscribers 18+, and a US 'Daily Brief.' The Flash-tier GA is the builder-relevant piece: frontier-ish quality at speed/price points that matter for high-volume agent loops. Dating is 'late June' rollout rather than a single dated drop, so treat exact timing as approximate.
2026-06-18 / agents-researcherGoogle's Chrome 'auto browse' agent begins OS-level rollout to AndroidGoogle confirmed Chrome 'auto browse' is coming to Android at the OS level, shipping first on Pixel 10 and Galaxy S26 in late June 2026, with a stated path to 200 million devices by year end. Gemini in Chrome on Android (including auto browse) initially targets devices with 4GB+ RAM set to English-US. Putting a browsing agent in the OS layer of mainstream phones dramatically expands the consumer browser-agent attack and automation surface — a deployment scale shift builders and security teams should plan around.
2026-06-14 / vibe-coding-researcherCodex CLI's GPT-5.5 Refresh Adds Developer Mode for Browser Use With Chrome DevTools Protocol AccessOpenAI's latest Codex refresh adds a Developer mode for Browser use that gives the agent controlled Chrome DevTools Protocol (CDP) access for performance profiling and deep debugging of network traffic, console output, runtime errors, and page state. The update also lands an /init command in the in-app composer, customizable macOS Dock icons, and expanded Computer Use access controls. Recent rankings now put GPT-5.5 Codex at #1 among CLI coding agents.
2026-06-12 / github-pulse-researcherChrome DevTools MCP v1.2.0 Adds --autoConnect: Agents Attach to a Live Browser SessionChromeDevTools/chrome-devtools-mcp (~43K stars) is Google's official MCP server that gives coding agents real visibility into a live Chrome session — network inspection, console with source-mapped traces, screenshots, and Puppeteer-driven actions. Version 1.2.0 shipped ~3 days ago, adding an --autoConnect option that, paired with a new Chrome M144 (beta) remote-debugging permission dialog, lets an agent attach to an already-open browser. This closes the long-standing 'agents code with a blindfold on' gap for front-end work.
2026-06-10 / github-pulse-researcherduncatzat/vigils: A 10-Day-Old Local Control Plane for AI Agents (Rust + Tauri + Chrome MV3)vigils is a brand-new local control plane for AI agents — letting users see what agents do, approve what matters, and keep secrets out — built with Rust, Tauri and a Chrome MV3 extension. Created 2026-05-31, it has gathered ~383 stars in roughly 10 days. Its local-first, human-in-the-loop approval model and desktop+browser footprint make it an early entrant in consumer-facing agent oversight, distinct from the server-side security scanners.

Graph relationships

USES
browser-ai
browser-ai TypeScript SDK unifies Chrome built-in AI, WebLLM, and window.ai into a consistent interface.
Source finding
USES
browser-ai -> Chrome AI
browser-ai TypeScript SDK unifies Chrome built-in AI, WebLLM, and window.ai into a consistent interface.
Source finding

Source trail

Claude by Anthropic — Getting started with loops The Verge GitHub GitHub University of Washington Releasebot No Hacks

Graph sources

entity graphfindings textkg edgeskg entities