agent-browser
Medium RiskElectron app automation via Chrome DevTools Protocol
Editorial assessment
Where agent-browser fits
agent-browser is currently positioned as a automation skill for teams automating browsers, app flows, and web data collection. Based on the available metadata, the core job to be done is straightforward: electron app automation via chrome devtools protocol.
The current description adds a practical clue about how the skill behaves in the field: control desktop applications like slack, vs code, and discord programmatically using cdp. headless browser automation for testing and monitoring. Combined with a Node package install path, this makes agent-browser easier to evaluate than pages that only list a name and external link.
agent-browser should be tested in a controlled environment before wider rollout. The current record points to Network requests and System access as part of the operational surface, which should be reviewed during security and workflow testing.
Best fit
teams automating browsers, app flows, and web data collection
Install surface
npm install -g agent-browser
Source signal
Public source link available
Workflow tags
Automation, Openclaw, and Cli
Adoption posture
Install command documented
Risk review
Should be tested in a controlled environment before wider rollout
Install Command
npm install -g agent-browserBest-fit workflows
Agent browser is best evaluated in automation environments where electron app automation via chrome devtools protocol
Shortlist it when your team is actively comparing options for automation, openclaw, and cli workflows
Use a disposable workspace for the first pass so you can confirm the install flow, repository quality, and downstream permissions before broader adoption
About
Control desktop applications like Slack, VS Code, and Discord programmatically using CDP. Headless browser automation for testing and monitoring.
Rollout checklist
Review the source repository at https://github.com/openclaw/agent-browser and confirm the README, maintenance activity, and install notes are still current.
Run `npm install -g agent-browser` in a disposable environment first so you can confirm package resolution, dependencies, and rollback steps.
Verify whether network requests and system access matches your security expectations and least-privilege model.
Map agent-browser against the rest of your stack in automation, openclaw, and cli workflows so the team knows whether it is a standalone tool or a supporting utility.
FAQ
What does agent-browser help with?
agent-browser is positioned as a automation skill. Based on the current summary and tags, it is most relevant for teams automating browsers, app flows, and web data collection, especially when the workflow requires electron app automation via chrome devtools protocol.
How should I evaluate agent-browser before using it in production?
Start by running npm install -g agent-browser in a disposable environment, then review the source repository, permission surface, and any workflow-specific dependencies before wider rollout.
Why does this page include editorial guidance instead of only the upstream docs?
ClawList is trying to make each skill page more useful than a bare directory listing. That means surfacing practical signals like the install surface, source link, permissions, workflow fit, and rollout considerations in one place.
Who is the best first user for agent-browser?
The best first evaluator is usually the operator or engineer already responsible for automation workflows, because they can verify whether agent-browser matches the current stack, risk tolerance, and maintenance expectations.
Security & Permissions
This skill requires the following permissions:
- Network requests
- System access
Recommendation: Use the principle of least privilege and regularly review skill behavior.
Related Skills
Agent Mail
Intelligent email processing with sending, receiving, and thread management capabilities.
Agent-Browser: Electron App Automation via CDP
Automate Electron applications using Chrome DevTools Protocol through agent-browser for UI control and interaction.
Agency Agents
Multi-agent application framework for orchestrating more capable automation systems.