Follow-up to my post last week. Should say properly this time that I work on this, not just use it. The bit people picked up in comments wasn’t the CLI part it was that it avoids launching a browser where it can. Order it tries: public endpoint, then session cookie, then replays whatever request the frontend makes, and then a real browser last. Most tasks stop at two or three. Claude never sees a DOM, just gets small structured output back. On a long session that’s the difference between browser tooling being a rounding error and being the reason you’re compacting. Installs as a skill so commands show up natively. webcmd list -f json if you want Claude to see what’s available mid-session. Still not handling staleness. Site changes, the stored command returns wrong data confidently instead of failing, and Claude will act on it. Worse than a hard error in an agent loop. Don’t wire it into anything important yet. github.com/agentrhq/webcmd submitted by /u/Opening-Profile6279
Originally posted by u/Opening-Profile6279 on r/ClaudeCode
