Agent prompt
Manual
Requirements
- Node.js 20.6+
- The
webcmdnpm CLI, installed globally or in the project - Cline — the VS Code extension, CLI, or JetBrains plugin
- A browser runtime; confirm with
webcmd doctorbefore browser work
Install and configure
Install Webcmd and its skills into Cline’s skill directories:~/.cline/skills/, .cline/skills/, and .claude/skills/. It loads skill metadata at startup and activates webcmd-browser on demand through its use_skill tool.
Restart Cline (or start a new task) after installing skills. In the extension, confirm they appear under the Skills tab (scale icon in the Cline panel).
Override default tools
Cline’s web surface depends on which app you are using:fetch_web and web_fetch are lossy fetches — HTTP with HTML-to-markdown conversion, no real browser session. Webcmd returns authenticated, JavaScript-rendered content and supports multi-step automation. Keep web_search. Webcmd has no search index of its own.
Cline has no per-tool deny list like OpenCode. Steer it with a rule in .clinerules/webcmd.md:
.clinerules/webcmd.md so the whole team gets the split. Toggle it on in the Rules panel (scale icon → Rules tab).
Full override (opt-in). In the IDE extension, turn off Web Tools under Cline Settings → Feature Settings. That removes web_fetch and web_search for the Cline provider — only do this if search is not needed. For a hard block on browser automation, leave Web Tools enabled but deny approval for Use the browser in Auto Approve settings.
Denying web tools does not affect the bash tool, which is how webcmd is driven.
Check for browser or scraping MCP servers in .cline/mcp.json — they overlap with Webcmd the same way native browser tools do. Disable or remove servers the user does not need.
Troubleshooting
See also
- Cline documentation — installation, providers, and the core workflow.
start.md— common setup, auth profiles and human handoff, and security.webcmd-browser— the raw browser session surface.