electron

<!-- Adapted for codexhost from ZCode 872ad960de7ec172591f7e1952f7849229f94521. See ../NOTICE.md for provenance and licenses. --> ## codexhost application routing Honor the user's target app. Prefer available native app/browser-control tools and their documentation; the CLI/CDP examples below apply when that is the selected, available route. For browser runtime selection see [control-browser](../control-browser/SKILL.md). For codexhost source launches follow root AGENTS.md and the current `npm start` implementation. Launching can stop running Codex Desktop processes; do it when launch is part of the task, not as a routine check. Reuse existing Desktop control and versioned binding modules when writing repository code. Do not assume every packaged Electron app permits remote debugging or that a port is already enabled; inspect the actual target. <!-- Derived from vercel-labs/agent-browser (skills/electron/SKILL.md). Copyright 2025 Vercel Inc. Licensed under Apache-2.0. Modified by ZCode: local integration, formatting and adaptations. See ../NOTICE.md for retained license and provenance information. --> # Electron App Automation Automate any Electron desktop app using agent-browser. Electron apps are built on Chromium and expose a Chrome DevTools Protocol (CDP) port that agent-browser can connect to, enabling the same snapshot-interact workflow used for web pages. ## Core Workflow 1. **Launch** the Electron app with remote debugging enabled 2. **Connect** agent-browser ...