docs: benchmarks + Chrome/Edge compatibility#9
Merged
Conversation
Two additions the public docs were missing:
1. Benchmarks section in README. Cold + warm numbers from
docs/BENCHMARK.md as a compact table (ghax vs gstack-browse /
agent-browser / playwright-cli), plus the real-world Wikipedia
warm-loop gap (6.6x vs playwright-cli, 9x on text extraction) and
the binary size / daemon-bundle size. Links to the full methodology
doc for anyone who wants the reproduction steps.
2. Browser compatibility section in README, because Edge and Chrome
are not interchangeable:
- Edge honors --remote-debugging-port on its default profile; the
quickstart works verbatim.
- Chrome 113+ silently ignores --remote-debugging-port on the
default user-data-dir. Must pass --user-data-dir=<path>
explicitly. This was inline in the quickstart already but not
called out as a Chrome-specific limitation.
- Chrome's faster update cadence means CDP-protocol changes and
anti-automation heuristics land there first; Edge is typically a
week or two behind on the same change.
- Both browsers set navigator.webdriver when launched with
--remote-debugging-port; --disable-blink-features=
AutomationControlled mitigates it. Cross-linked to the full
Known-browser-quirks section in CONTRIBUTING.md instead of
duplicating it.
llms.txt also updated: the first-time-usage pattern now surfaces the
Chrome-specific launch command alongside the Edge one, since an agent
following the install steps top-to-bottom needs to pick the right one
for the user's browser.
kepptic
added a commit
that referenced
this pull request
Apr 24, 2026
docs: benchmarks + Chrome/Edge compatibility
kepptic
added a commit
that referenced
this pull request
Apr 24, 2026
docs: benchmarks + Chrome/Edge compatibility
kepptic
added a commit
that referenced
this pull request
Apr 24, 2026
docs: benchmarks + Chrome/Edge compatibility
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Performance section (compact cold+warm table, 6.6x warm-loop gap on real content, link to full BENCHMARK.md) and a Browser compatibility section calling out the Chrome v113+ default-profile CDP restriction. llms.txt gets the Chrome launch command inline so agents pick the right one for the user's browser.