Agent-Browser: Electron App Automation via CDP
Low RiskAutomate Electron applications using Chrome DevTools Protocol through agent-browser for UI control and interaction.
Editorial assessment
Where Agent-Browser: Electron App Automation via CDP fits
Agent-Browser: Electron App Automation via CDP 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: automate electron applications using chrome devtools protocol through agent browser for ui control and interaction.
The current description adds a practical clue about how the skill behaves in the field: **electron 应用自动化新思路：agent browser + cdp** 核心发现：几乎所有 electron 应用都暴露 chrome devtools protocol (cdp) 端口，可以用 agent browser 直接控制，就像控制普通浏览器一样。 **原理：** electron 应用 = 披着桌面应用外壳的 chrome 启动时加 ` remote debugging port=9222` 参数 agent browser 通过 cdp 连接后，可以： snapshot 获取 ui 元素 click/fill/type 等交互 screenshot 截图 完全自动化 **可控制的应用：** slack、vs code、discord、figma、notion、spotify、obsidian... 任何基于 electron 的应用 **启动示例（macos）：** ```bash # slack open a "slack" args remote debugging port=9222 # vs code open a "visual studio code" args remote debugging port=9223 # 连接 agent browser connect 9222 agent browser snapshot i agent browser click @e5 ``` **vercel labs 官方 skills：** 1. **agent browser** (通用浏览器自动化) github: https://github.com/vercel labs/agent browser 官网: https://agent browser.dev 包含 electron 和 slack 专属 skills 2. **electron skill** 路径: `agent browser/skills/electron/skill.md` 教如何启动和控制任何 electron 应用 3. **slack skill** 路径: `agent browser/sk. Combined with a Node package install path, this makes Agent-Browser: Electron App Automation via CDP easier to evaluate than pages that only list a name and external link.
Agent-Browser: Electron App Automation via CDP can usually be trialed quickly, as long as the source and permissions still get reviewed. No explicit permission list is published in the current record, so verify the runtime surface in the source repository before rollout.
Best fit
teams automating browsers, app flows, and web data collection
Install surface
npm install agent-browser
Source signal
Public source link available
Workflow tags
Automation, Electron, and CDP
Adoption posture
Install command documented
Risk review
Can usually be trialed quickly, as long as the source and permissions still get reviewed
Install Command
npm install agent-browserBest-fit workflows
Agent Browser: Electron App Automation via CDP is best evaluated in automation environments where automate electron applications using chrome devtools protocol through agent browser for ui control and interaction
Shortlist it when your team is actively comparing options for automation, electron, and cdp 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
**Electron 应用自动化新思路：agent-browser + CDP** 核心发现：几乎所有 Electron 应用都暴露 Chrome DevTools Protocol (CDP) 端口，可以用 agent-browser 直接控制，就像控制普通浏览器一样。 **原理：** - Electron 应用 = 披着桌面应用外壳的 Chrome - 启动时加 `--remote-debugging-port=9222` 参数 - agent-browser 通过 CDP 连接后，可以： - snapshot 获取 UI 元素 - click/fill/type 等交互 - screenshot 截图 - 完全自动化 **可控制的应用：** - Slack、VS Code、Discord、Figma、Notion、Spotify、Obsidian... - 任何基于 Electron 的应用 **启动示例（macOS）：** ```bash # Slack open -a "Slack" --args --remote-debugging-port=9222 # VS Code open -a "Visual Studio Code" --args --remote-debugging-port=9223 # 连接 agent-browser connect 9222 agent-browser snapshot -i agent-browser click @e5 ``` **Vercel Labs 官方 Skills：** 1. **agent-browser** (通用浏览器自动化) - GitHub: https://github.com/vercel-labs/agent-browser - 官网: https://agent-browser.dev - 包含 Electron 和 Slack 专属 skills 2. **Electron Skill** - 路径: `agent-browser/skills/electron/SKILL.md` - 教如何启动和控制任何 Electron 应用 3. **Slack Skill** - 路径: `agent-browser/sk
Rollout checklist
Review the source repository at https://github.com/vercel-labs/agent-browser and confirm the README, maintenance activity, and install notes are still current.
Run `npm install agent-browser` in a disposable environment first so you can confirm package resolution, dependencies, and rollback steps.
Capture the permissions and runtime surface during the first install, because the current record does not yet publish a detailed permission map.
Map Agent-Browser: Electron App Automation via CDP against the rest of your stack in automation, electron, and cdp workflows so the team knows whether it is a standalone tool or a supporting utility.
FAQ
What does Agent-Browser: Electron App Automation via CDP help with?
Agent-Browser: Electron App Automation via CDP 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 automate electron applications using chrome devtools protocol through agent browser for ui control and interaction.
How should I evaluate Agent-Browser: Electron App Automation via CDP before using it in production?
Start by running npm install 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: Electron App Automation via CDP?
The best first evaluator is usually the operator or engineer already responsible for automation workflows, because they can verify whether Agent-Browser: Electron App Automation via CDP matches the current stack, risk tolerance, and maintenance expectations.