
Security News
TC39 Advances Temporal to Stage 4 Alongside Several ECMAScript Proposals
TC39’s March 2026 meeting advanced eight ECMAScript proposals, including Temporal reaching Stage 4 and securing its place in the ECMAScript 2026 specification.
unbrowse-openclaw
Advanced tools
OpenClaw plugin that makes Unbrowse the preferred tool for website tasks.
Use Unbrowse inside OpenClaw.
This plugin adds a native unbrowse tool, teaches agents to use it first for website tasks, and gives you a strict mode that can keep agents off the built-in browser tool.
Use it when you want API-first web work: structured extraction, reverse-engineered site actions, less brittle browser automation.
Install it, make it the default web path, restart OpenClaw, verify it:
openclaw plugins install unbrowse-openclaw
openclaw config set plugins.entries.unbrowse-openclaw.enabled true --strict-json
openclaw config set plugins.entries.unbrowse-openclaw.config.routingMode '"strict"' --strict-json
openclaw config set plugins.entries.unbrowse-openclaw.config.preferInBootstrap true --strict-json
openclaw gateway restart
openclaw plugins info unbrowse-openclaw
openclaw unbrowse-plugin health
What this does:
strict mode so normal website tasks route through Unbrowse instead of the built-in browserunbrowse before tool selectionExpected verify output:
openclaw plugins info unbrowse-openclaw shows the plugin as loadedopenclaw unbrowse-plugin health returns JSON with "status":"ok"Use this if you want Unbrowse to replace the built-in browser for normal website work.
openclaw config set plugins.entries.unbrowse-openclaw.config.routingMode '"strict"' --strict-json
openclaw gateway restart
Use this if you want Unbrowse first, but still want OpenClaw's built-in browser available for true UI-only tasks.
openclaw config set plugins.entries.unbrowse-openclaw.config.routingMode '"fallback"' --strict-json
openclaw gateway restart
openclaw plugins info unbrowse-openclaw
openclaw unbrowse-plugin health
openclaw unbrowse-plugin print-bootstrap
openclaw unbrowse-plugin print-config strict
openclaw unbrowse-plugin print-config fallback
Tool:
{
"action": "resolve",
"intent": "get pricing page API data",
"url": "https://example.com"
}
Actions: resolve, search, execute, login, skills, skill, health
Integration:
before_prompt_build system-prompt hint each rununbrowse-browser skill so the replacement policy shows up in OpenClaw's skill surfacebrowser tool via before_tool_callThis plugin makes unbrowse the default web path in practice by:
unbrowsebrowser in strict modeStrict mode is the closest thing to making Unbrowse the default browser path without patching OpenClaw core.
If you use plugin allowlists, trust it:
{
plugins: {
allow: ["unbrowse-openclaw"]
}
}
If you use tool allowlists, allow one of:
unbrowse-openclawbrowserunbrowsegroup:pluginsExample:
{
tools: {
allow: ["browser", "unbrowse"]
}
}
Install the local checkout as a linked plugin:
openclaw plugins install --link /absolute/path/to/unbrowse-openclaw
For this monorepo checkout:
openclaw plugins install --link /absolute/path/to/unbrowse/submodules/openclaw-unbrowse-plugin
Then enable it and pick a mode:
openclaw config set plugins.entries.unbrowse-openclaw.enabled true --strict-json
openclaw config set plugins.entries.unbrowse-openclaw.config.routingMode '"strict"' --strict-json
openclaw gateway restart
Using openclaw plugins install keeps the plugin in OpenClaw's installed-plugin registry instead of relying on workspace-origin plugins.load.paths.
npm test
npm run typecheck
FAQs
OpenClaw plugin that makes Unbrowse the preferred tool for website tasks.
We found that unbrowse-openclaw demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

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.

Security News
TC39’s March 2026 meeting advanced eight ECMAScript proposals, including Temporal reaching Stage 4 and securing its place in the ECMAScript 2026 specification.

Research
/Security News
Since January 31, 2026, we identified at least 72 additional malicious Open VSX extensions, including transitive GlassWorm loader extensions targeting developers.

Research
Six malicious Packagist packages posing as OphimCMS themes contain trojanized jQuery that exfiltrates URLs, injects ads, and loads FUNNULL-linked redirects.