Skip to main content

​
Disabling tools

The dashboard’s Tools page lists all 43 tools with a switch each. A disabled tool stays visible to the agent but every call returns an error:
So the agent knows exactly what to ask for instead of guessing at workarounds. Typical uses: block browser_upload and browser_download on a shared machine, block devtools_cdp and devtools_evaluate when you do not want arbitrary code run, or keep only the read-only tools for a research agent. The extension sends the disabled list to the companion whenever it connects or the list changes. The companion writes it to ~/.browspark/tools.json so the policy applies from the first call after a restart, before the extension has reconnected. The catalog itself comes from the companion on connect (tools.catalog event with name, description and companion version). If the dashboard shows no tools, the companion has not connected yet.

​
Developer browser policy

Settings → Developer browser has three positions: The setting travels with the same tools.policy message as the disabled list.

​
Emergency stop

Settings → Emergency stop detaches the debugger from every tab, clears the shared list, switches Share everything off and disconnects from the companion. The agent’s next call fails with a “not connected” status and pairing instructions. Resume reconnects with the stored token but shares nothing until you share again.