Webcmd

Self-learning browser infra for AI agents.

Webcmd learns the navigational context of websites as agents use them, then compiles that knowledge into deterministic commands for faster, cheaper, more reliable browser automation. The goal is simple: stop making agents rediscover the same sites on every run and cut browser-agent token spend by up to 90%.

On top of live browser control, Webcmd adds 3 layers of learnings. Each layer collapses cost and variance for the layer above it.

Layer	Scenario	What Webcmd Helps With
0. Live browser control	The site is unfamiliar.	Use webcmd browser to inspect, click, type, extract, capture network calls, and complete the task in a real browser.
1. Sitemap memory	The site is familiar, but the action space is not fully known.	Capture an agent-facing sitemap of observed pages, states, actions, workflows, APIs, pitfalls, and fallback paths.
2. CLI authoring	The action space is known, but the path is still too variable for one fixed sequence.	Explicitly author a reusable webcmd <site> adapter with structured output, so future agents spend tokens on the task instead of navigation.
3. Extend existing CLIs	The workflow is deterministic enough to stop browsing.	Extend the webcmd <site> adapter with a tailored command so the workflow runs instantly with the least amount of tokens.

For local, multi-step browser exploration, agents can send one sandboxed Playwright-style program to an explicit browser session:

webcmd --profile work session create "Work Project" -f json
# id: work-project-k7
webcmd --profile work --session work-project-k7 browser tabs
webcmd --profile work --session work-project-k7 browser run --file explore.js
printf 'return await page.title();' \
  | webcmd --profile work --session work-project-k7 browser run --stdin
webcmd --profile work session close work-project-k7

Profiles are cookie jars; Sessions are independent browser windows within a profile, so Session IDs are immutable, Profile-scoped, and safe to reuse for that Session's lifetime. Parallel agents should create separate Sessions. Adapter commands without --session reuse the Profile's adapter-default Session. Raw browser commands require an explicit readable Session ID.

Demo

https://github.com/user-attachments/assets/04eceadc-d398-4303-984d-ae3197bfa664

Quick Start

Agent prompt

Fetch and follow https://raw.githubusercontent.com/agentrhq/webcmd/main/start.md to set up Webcmd end to end.

Manual

Webcmd requires Node.js 20.6+.

npm install -g @agentrhq/webcmd

The npm package ships the Webcmd core and browser commands, but no site adapters. Search the plugin catalog and explicitly install the adapter you need:

webcmd plugin search <site> -f json
webcmd plugin install <installSource-from-search>

webcmd skills add

When prompted, choose Claude, Codex, another supported harness, or a custom skills path. That install is exactly one skill, webcmd-browser. Adapter, search, fetch, and plugin commands remain on the CLI; they are outside the default installed browser skill.

Load or tag webcmd-browser only for live browser work. Existing adapter, search, fetch, and plugin CLI operations do not require that skill.

Use webcmd to research the latest discussions about browser automation across Hacker News and Reddit, then return a concise comparison with source links.

What You Can Ask

---

GitHub에서 전체 내용 보기