Skip to content

fix(browser_execute): use real helper names in tool description #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Alezander9 merged 1 commit into from
Apr 30, 2026
Merged

fix(browser_execute): use real helper names in tool description #26

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions packages/opencode/src/tool/browser-execute.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,9 @@ Execute Python code against a connected web browser via the BrowserCode harness.

This is the single tool for all browser interaction. The agent writes Python that
imperatively drives the browser using helpers preloaded into the script's namespace
(`goto`, `click`, `type_text`, `screenshot`, `js`, `cdp`, `new_tab`, `switch_tab`,
`wait_for_load`, `page_info`, `http_get`, etc.).
(`goto_url`, `click_at_xy`, `type_text`, `capture_screenshot`, `js`, `cdp`,
`new_tab`, `switch_tab`, `ensure_real_tab`, `wait_for_load`, `page_info`,
`http_get`, etc.).

Read `packages/bcode-browser/harness/SKILL.md` for the full helper surface and
recommended workflow. Read `packages/bcode-browser/harness/src/browser_harness/helpers.py`
Expand All @@ -15,14 +16,17 @@ browser. Add task-specific helpers to
`packages/bcode-browser/harness/agent-workspace/agent_helpers.py` between calls;
they take effect on the very next call.

Coordinate-based interaction is the default — `click(x, y)` rather than selector
indices. `Input.dispatchMouseEvent` passes through iframes, shadow DOM, and
cross-origin at the compositor level.
Coordinate-based interaction is the default — `click_at_xy(x, y)` rather than
selector indices. `Input.dispatchMouseEvent` passes through iframes, shadow DOM,
and cross-origin at the compositor level.

For first navigation use `new_tab(url)` (or `ensure_real_tab(); goto_url(url)`),
not bare `goto_url` — the latter clobbers whatever tab the user is on.

Output is whatever the script writes to stdout/stderr. Wrap multi-step flows in
one call when possible — that's the design.

Example:
goto("https://example.com")
new_tab("https://example.com")
wait_for_load()
print(page_info())
Loading