Skip to main content

​
Agent prompt

​
Manual

​
Requirements

  • Node.js 20.6+
  • The webcmd npm CLI, installed globally or in the project
  • Claude Code (claude), installed globally or in the project
  • A browser runtime; confirm with webcmd doctor before browser work

​
Install the plugin

This installs all seven bundled Webcmd skills. Do not also add those skills with webcmd skills add; running both leaves two copies that can sit at different versions. Plugin updates are version-gated, not commit-gated. Run claude plugin update webcmd@webcmd to pick up a new release; it is separate from webcmd update, which upgrades only the npm CLI.

​
Install and configure without the plugin

Install Webcmd and its skills:
When webcmd skills add prompts, choose the claude provider. It installs into ~/.claude/skills/ (user) or .claude/skills/ (project), which Claude Code reads on startup. Claude Code then surfaces webcmd-usage and webcmd-browser as skills when a task matches their descriptions. Restart Claude Code (or start a new session) after installing skills.

​
Override default tools

Claude Code ships two native web tools — WebFetch (fetch a URL) and WebSearch (search) — both permission-gated by default. Deny WebFetch. It is lossy by design: a small, fast model runs an extraction prompt against the page and Claude receives that model’s answer, not the page. Webcmd returns the real content. Add to the user or project settings file (.claude/settings.json in the project, or ~/.claude/settings.json):
Or per invocation:
Keep WebSearch. It returns result titles and URLs without fetching the pages, which is exactly the step Webcmd does not cover — Webcmd has no search index. Let Claude Code search, then let Webcmd read what it finds. If the desktop app’s Browser pane is in use, its tools are MCP-named (mcp__Claude_Browser__*) and can be denied the same way:
Only deny those if the user does not use the Browser pane for their own app — it is wired into the local dev loop. There is also a browserExternalPageTools: "disabled" setting, but it applies to managed settings only. Denying these tools does not affect the Bash tool, which is how webcmd is driven.

​
Troubleshooting

​
See also