browser.*
Browser automation RPC methods
There is no browser.* JSON-RPC method in the current aleph-server runtime. The browser automation pipeline is implemented as builtin tools (browser_navigate, browser_click, browser_type, browser_snapshot, etc.) consumed by the agent loop, not as gateway RPCs. src/gateway/handlers/browser_config.rs exposes only the configuration namespace browser_config.*; the CDP driver itself lives in src/browser/.
The browser.get method, plus the action targets, scroll directions, and launch modes documented in the previous version of this page, describe the agent-side tool API (the shape of browser_navigate arguments), not a gateway RPC. A client that wants browser automation goes through chat.send / agent.run, where the agent loop dispatches the tool.
Methods
The methods below are not registered. A browser.* JSON-RPC call returns Method not found (-32601).
| Method | Description |
|---|---|
browser.navigate | (Tool) Navigate the current tab to a URL. |
browser.click | (Tool) Click an element by selector, ref, or viewport coordinates. |
browser.type | (Tool) Type text into an input element. |
browser.screenshot | (Tool) Capture a screenshot of the page or a specific element. |
browser.evaluate | (Tool) Execute a JavaScript expression and return the result. |
browser.snapshot | (Tool) Take an ARIA accessibility snapshot of the page. |
The only browser-related JSON-RPC methods are:
browser_config.get/browser_config.update— read or write the[browser]config section (mode,headless,cdp_port).browser_navigate,browser_click,browser_type,browser_evaluate,browser_snapshotare dispatched by the LLM via the agent loop, not over the JSON-RPC surface.
See Also
- Methods Reference -- All currently registered namespaces
- browser_config.* -- Browser configuration (lives under
config_handlersin this repo) - agent.* -- Where browser tools are dispatched