Agent prompt
Manual
Requirements
- Node.js 20.6+
- The
webcmdnpm CLI, installed globally or in the project - Pi (
@earendil-works/pi-coding-agent), running in a terminal session - A browser runtime; confirm with
webcmd doctorbefore browser work
Install and configure
Install Webcmd and its skills:webcmd skills add prompts, choose the agents provider. It links skills into ~/.agents/skills/ (user) or .agents/skills/ (project), both of which Pi scans for skills on startup alongside its own ~/.pi/agent/skills/ and .pi/skills/ directories. Pi then surfaces webcmd-usage and webcmd-browser as skills.
To install into Pi’s own skill directories instead, pass a custom path:
.pi/skills and .agents/skills load only after the project is trusted. Accept Pi’s trust prompt on first run in the project, or set defaultProjectTrust to always in ~/.pi/agent/settings.json. Restart Pi after installing skills so the new skill descriptions are picked up at startup.
Override default tools
Pi ships seven built-in tools —read, write, edit, bash, grep, find, ls — and no web, search, or browser tool at all, so there is nothing built in to turn off. Webcmd works through bash as soon as the CLI is on PATH. Do not reach for --no-builtin-tools: it strips read/write/edit/bash, and bash is how Webcmd runs.
Pi is the harness where competing tools are most likely to come from what the user installed, since every web capability it has is an extension or skill. Check for these and ask before removing any:
Extensions that mix search with extraction are the awkward case: the search half is worth keeping, and only some expose a config toggle to split them. When there is no toggle, steer Pi with instructions instead of removing the extension.
To remove one outright, delete its folder — for example
~/.pi/agent/skills/pi-skills/browser-tools — and restart Pi.
Troubleshooting
See also
start.md— common setup, auth profiles and human handoff, and security.webcmd-browser— the raw browser session surface.webcmd-usage— adapter-first usage rules.