Skip to content

docs: map AGENT_BROWSER tool names across harnesses (@fehmer) - #8606

Open
fehmer wants to merge 1 commit into
masterfrom
docs/agent-browser-tool-mapping
Open

fehmer wants to merge 1 commit into
masterfrom
docs/agent-browser-tool-mapping

Conversation

@fehmer

@fehmer fehmer commented Nov 20, 2026

Copy link
Copy Markdown
Member

Summary

  • docs/AGENT_BROWSER.md: new ## Tools section at the top — the doc's gotchas name playwright-mcp tools (javascript_tool, read_console_messages, resize_window, gif_creator); the table maps each to pi-chrome's chrome_* equivalent, plus two pi-chrome specifics (5s chrome_evaluate budget → fire-and-forget + poll; console instrumentation drops on page load). No existing text modified.

Evidence

The #8603 session ran entirely on pi-chrome: the doc's 45s javascript_tool budget and the read_console_messages first-call ritual didn't apply, so the mapping was guesswork. Everything else in the doc (dev server, __mt, the rAF check, the static/ reload note) transferred fine — only the names were harness-specific.

If a full tool-agnostic rewrite is preferred over a mapping table, that's the alternative; this PR takes the smaller step.

Merge Danger

Two-way. One section added, no existing text modified.

@monkeytypegeorge monkeytypegeorge added the docs Related to Markdown files and documentation label Nov 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Related to Markdown files and documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants