chrome-agent Implementation Delta
Purpose
Two unrelated public projects use the name chrome-agent. This page separates their identities after a third-party validation error matched the Rust repository to Corey Gallon's scheduled World's Fair tool. The correction keeps the event record precise while preserving the other project as optional technical comparison context.
Corey Gallon's chrome-agent
The project connected to Corey's scheduled session is captivus/chrome-agent, a Python CLI distributed as chrome-agent on PyPI. It exposes direct Chrome DevTools Protocol access for browser launch, status, navigation, JavaScript evaluation, screenshots, protocol help, and event subscriptions. The official schedule connects Corey and this tool to The Dark Arts of Web Automation.
sderosiaux/chrome-agent
sderosiaux/chrome-agent is a separate Rust project. Its public repository presents an agent-oriented CDP workflow built around compact accessibility snapshots, stable backend node identifiers, actions, inspection, and content extraction. Its similar name and browser-agent focus do not make it Corey Gallon's work or event evidence.
Practical Difference
| Dimension | Corey Gallon's project | sderosiaux project |
|---|---|---|
| Repository and package | captivus/chrome-agent; Python package on PyPI | sderosiaux/chrome-agent; Rust crate and npm package |
| Core operating model | Name a running Chrome instance, send any CDP Domain.method, or hold an event subscription with attach. | Use an agent-oriented command vocabulary such as inspect, click, read, and extract over CDP. |
| Page-state representation | Raw CDP results selected by the caller: DOM, Runtime, Network, Page, Input, and other live protocol domains. | Compact accessibility snapshots with stable backend-node-derived UIDs, plus targeted visible-text and extraction commands. |
| Best fit | Protocol-level debugging, event observation, exact Chrome capability access, and workflows where the operator chooses the CDP primitive. | Agent navigation and extraction loops where compact state, direct UIDs, and built-in content commands reduce prompt/context overhead. |
| Interaction pattern | One-shot commands for spot work; persistent attach streams for event observation; optional Python API for in-process control. | --inspect returns state with an action; batch and pipe serve multi-command flows. |
| When not to choose it first | When an agent needs a small, opinionated page representation rather than direct protocol knowledge. | When debugging depends on arbitrary/new CDP methods or a custom event subscription model not covered by its higher-level commands. |
| World's Fair connection | Supporting implementation context for Corey's scheduled session. | None established. |
| Appropriate role in this wiki | Tool page tied to the official schedule, with repository implementation context clearly labeled. | External alternative and comparison context only. |
Selection Guide
| Need | Prefer | Reason |
|---|---|---|
| Call a CDP method that landed after a CLI release or is absent from a curated wrapper | Corey Gallon's chrome-agent | It forwards the method and parameters to the running browser, and its live help reads that browser's schema. |
| Observe selected navigation or network events while another actor uses the same browser | Corey Gallon's chrome-agent | Its persistent attach model provides isolated event subscriptions. |
| Give an LLM a small actionable snapshot of a normal web page | sderosiaux/chrome-agent | Its a11y UID model and --inspect action loop are designed for compact agent-facing page state. |
| Extract an article, a repeating feed, or a card/table collection before writing selectors | sderosiaux/chrome-agent | It supplies read and extract commands for those common shapes. |
| Investigate a complicated browser bug with DOM, runtime, input, protocol, and network tools chosen case by case | Corey Gallon's chrome-agent | The lower-level CDP-first model leaves the diagnostic method under the operator's control. |
These are implementation-level selection inferences from the two public repositories, not claims made by the World's Fair program or evidence about the scheduled talk.
Discovery And Source Boundary
The Rust repository entered the research path because an earlier third-party validation matched a shared project name without confirming the repository owner. This page records that error explicitly so it is not repeated. The official schedule is canonical for the session, speaker, and conference association; the GitHub repositories and PyPI package support implementation comparison only. No AIE source establishes a relationship between sderosiaux/chrome-agent, Corey Gallon, or the event.