Question 1

What is webclaw?

Accepted Answer

webclaw is DureClaw's browser node, shipped as a Chrome MV3 extension. It lends AI agents 'browser hands' — fetch, DOM reads, clicks, fills, downloads, tab control. Judgment (the brain) is delegated to a master or a local brain; webclaw itself is pure JS acting as hands only.

Question 2

How is bus mode different from standalone mode?

Accepted Answer

In bus mode, webclaw joins a Phoenix channel (ws://<host>/socket), runs the master's task.assign, and replies with task.result. In standalone mode (config.local.json's standalone:true), there's no master or bus — instructions typed into the on-page HUD chat are delegated to a local brainUrl/brain/exec instead. That combination is called a Wide Worker.

Question 3

Which marker commands are supported?

Accepted Answer

core.js's runTask handles 13 marker commands: [FETCH] [DOWNLOAD] [LINKS] [ATTR] [DOM] [TABS] [CLICK] [FILL]/[TYPE] [SUBMIT] [JS] [OPEN] [HUD] [SAY]. Prefix with [NAME@part-of-url] to target a specific tab; with no marker, the whole instruction is delegated to the brain.

Question 4

Where does the brain connect to?

Accepted Answer

The local brain server (app.mjs) tries claude → codex → baryon in order and adopts whichever answers first (via the WW_BACKENDS env var). The API is GET /health and POST /brain/exec {prompt}, on port 4111 by default. Claude Max subscriptions return 401 in headless mode (claude -p), so automation should go through a codex subscription or a baryon API key.

Question 5

How do I install it?

Accepted Answer

In Chrome, just point --load-extension at the unpacked webclaw directory. To embed it as a real browser inside an Electron app, one line — session.defaultSession.loadExtension() — loads the MV3 extension as-is (this is how baryon-desktop/deskclaw does it).

The browser
becomes AI's hands

Not features. Outcomes.

Four moves. That's it.

Not a screen.
A hand.

Alone, or together

Short commands. Instant response.

The browserbecomes AI's hands