You're Invited:Meet the Socket Team at RSAC and BSidesSF 2026, March 23–26.RSVP
Socket
Book a DemoSign in
Socket

@getfoundry/unbrowse-openclaw

Package Overview
Dependencies
Maintainers
1
Versions
31
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@getfoundry/unbrowse-openclaw

OpenClaw plugin that makes Unbrowse the preferred tool for website tasks.

latest
Source
npmnpm
Version
0.7.12
Version published
Weekly downloads
110
-63.58%
Maintainers
1
Weekly downloads
 
Created
Source

unbrowse-openclaw

OpenClaw plugin that makes Unbrowse the preferred tool for website tasks.

It adds:

  • agent tool: unbrowse
  • bootstrap guidance that tells agents to use Unbrowse first
  • config presets for fallback and strict routing
  • small CLI helpers for debugging

Use it when you want agents to hit APIs and structured data paths before reaching for pixel browser automation.

Install

Intended npm package:

@getfoundry/unbrowse-openclaw

Until that scope is published, install from a local checkout:

git clone https://github.com/lekt9/unbrowse-openclaw.git
cd unbrowse-openclaw
npm install
openclaw plugins install .
openclaw gateway restart

Verify:

openclaw plugins info unbrowse-browser
openclaw unbrowse-plugin health

If you use plugin allowlists, trust it explicitly:

{
  plugins: {
    allow: ["unbrowse-browser"]
  }
}

What agents get

Tool name:

  • unbrowse

Typical call:

{
  "action": "resolve",
  "intent": "get pricing page API data",
  "url": "https://example.com"
}

Supported actions:

  • resolve
  • search
  • execute
  • login
  • skills
  • skill
  • health

Make Unbrowse the default web path

OpenClaw does not expose a true browser plugin slot, so this plugin does not replace the built-in browser tool by name.

What it does instead:

  • adds the unbrowse tool
  • injects prompt guidance so agents prefer it
  • lets you deny core browser in tool policy when you want strict routing

Fallback mode

Prefer Unbrowse first, but still allow core browser when the task really needs UI automation.

  • examples/openclaw.fallback.json5

Strict mode

Force normal web tasks onto Unbrowse by denying core browser.

Strict mode is the closest thing to “make Unbrowse the default browser” in current OpenClaw.

Tool policy

If you use tool allowlists, include one of:

  • plugin id: unbrowse-browser
  • tool name: unbrowse
  • group:plugins

Example:

{
  tools: {
    allow: ["group:plugins", "unbrowse-browser", "unbrowse"]
  }
}

Local dev

Load directly from source with plugins.load.paths:

{
  plugins: {
    allow: ["unbrowse-browser"],
    load: { paths: ["/absolute/path/to/unbrowse-openclaw"] },
    entries: {
      "unbrowse-browser": {
        enabled: true,
        config: {
          routingMode: "fallback",
          preferInBootstrap: true,
          allowBrowserFallback: true,
          timeoutMs: 120000
        }
      }
    }
  }
}

CLI helpers

openclaw unbrowse-plugin health
openclaw unbrowse-plugin print-bootstrap
openclaw unbrowse-plugin print-config strict
openclaw unbrowse-plugin print-config fallback

Development

npm test
npm run typecheck

Keywords

openclaw

FAQs

Package last updated on 07 Mar 2026

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts