| title | Codex CLI |
|---|---|
| sidebarTitle | Codex |
Fetch and follow https://raw.githubusercontent.com/agentrhq/webcmd/main/start.md to set up Webcmd end to end.
- Node.js 20.6+
- The
webcmdnpm CLI, installed globally or in the project - Codex CLI (
codex), installed and authenticated - A browser runtime; confirm with
webcmd doctorbefore browser work
Pick one of the two paths below. Do not use both — the plugin already carries the skills, and installing them again leaves duplicates.
Add the marketplace and install the plugin:
codex plugin marketplace add agentrhq/webcmdcodex plugin add webcmd@webcmdcodex plugin add takes PLUGIN@MARKETPLACE, or a bare plugin name with -m webcmd. Pin a version with codex plugin marketplace add agentrhq/webcmd --ref <tag>.
The same flow is available in the TUI: run /plugins, choose Add plugin marketplace, and enter agentrhq/webcmd or https://github.com/agentrhq/webcmd.
The plugin bundles exactly one skill, webcmd-browser, and installs the npm CLI on first use if webcmd is missing. Start a new task after installing.
Useful follow-ups: codex plugin list, codex plugin remove webcmd, codex plugin marketplace upgrade. All accept --json.
npm install -g @agentrhq/webcmd
webcmd doctor
webcmd skills addWhen webcmd skills add prompts, choose the agents provider. It installs into ~/.agents/skills/ (user) or .agents/skills/ (project), which Codex CLI reads on startup. Codex then surfaces webcmd-browser as a skill.
Restart Codex (or start a new session) after installing skills.
Nothing to disable. Codex CLI has no fetch tool and no browser tool, so Webcmd does not displace anything — it adds the surface Codex is missing. Codex drives it through the shell tool.
Its one web tool is web_search, set by the top-level web_search key in ~/.codex/config.toml. Keep it enabled. Webcmd has no search index of its own, and search is how a question becomes URLs for Webcmd to read.
One change is worth recommending. web_search defaults to "cached", an OpenAI-maintained index with no external web access, so results can be stale. Switching to "live" pairs better with Webcmd:
web_search = "live"Accepted values are "disabled", "cached" (default), "indexed", and "live". Ask before changing it — "live" means real network egress from the user's machine.
If the user has installed a browser or scraping MCP server, that does overlap with Webcmd. Individual MCP tools are denied per server:
[mcp_servers.some_browser_mcp]
disabled_tools = ["navigate", "screenshot"]| Symptom | What to try |
|---|---|
webcmd doctor is red |
Fix the browser runtime first; browser commands depend on it. |
| Skills not loading in Codex | Run webcmd skills add with the agents provider, then restart codex. |
| Search results look stale | web_search defaults to "cached". Set web_search = "live" in ~/.codex/config.toml, then restart codex. |
web_search was disabled and search stopped working |
Expected. Set it back to "live" or "cached" — Webcmd does not replace search. |
webcmd not found in Codex shell |
Confirm webcmd is on the PATH Codex uses; restart after installing the CLI. |
| Browser Session idles or loses its window | Keep its immutable, Profile-scoped ID; webcmd --profile work --session work-project-k7 browser tabs reopens it. Start with webcmd --profile work session create "Work Project"; use webcmd --profile work session list and webcmd --profile work session close work-project-k7 for lifecycle. |
start.md— common setup, auth profiles and human handoff, and security.webcmd-browser— the raw browser session surface.