2491f5c732
40 files demonstrating every major OpenClaw capability using Claude Code: - 3 agents (researcher, writer, reviewer) - 3 skills (daily-briefing, slack-message, web-research) - 2 security hooks (pre-tool-use blocker, post-tool-use logger) - 10 self-contained examples with copy-paste prompts - Complete feature map (20 capabilities, 11 full match, 7 different, 2 gap) - Security docs including NemoClaw comparison - Automation, messaging, browser, memory documentation Zero dependencies. Clone and run. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| playwright-mcp-setup.md | ||
| README.md | ||
Browser Automation
OpenClaw: Built-in CDP/Playwright
OpenClaw ships with browser control built in. It manages multiple browser
instances, supports profiles, and exposes act commands that combine
navigation, interaction, and extraction in one step. No setup required.
Claude Code: Playwright MCP server
Claude Code uses the @playwright/mcp server. Same underlying engine
(Playwright), different integration model: the browser runs in a separate
process, and Claude communicates with it over MCP.
Tradeoff: The decoupled approach means the browser can be swapped or updated independently. The cost is one extra setup step.
Comparison
| Property | OpenClaw | Claude Code |
|---|---|---|
| Engine | CDP/Playwright | Playwright |
| Setup | Zero | Enable in .mcp.json |
| Multi-instance | Yes | One per MCP server |
| Browser profiles | Yes | Via Playwright config |
act shorthand |
Yes | No (compose manually) |
For setup, see playwright-mcp-setup.md.