Local OpenWork Electron browser automation with CDP for exploration and debugging: attach OpenCode browser tools to the Electron dev app, drive its UI through the Chrome DevTools Protocol endpoint, and confirm composer task responses.
Tasks
Drive the local OpenWork Electron app UI via CDP for exploration and debugging
Send a task/session from the Lexical composer and confirm the response in the UI
Run local UI smoke tests using browser_list, browser_snapshot, and browser_eval
Inputs
A local Electron dev app started with pnpm dev
OpenCode browser tools configured with browser_url http://127.0.0.1:9823
Interaction with the OpenWork Electron app UI through the CDP endpoint
Session responses confirmed via document.body.innerText or the current URL
Limitations and checks
For verdicts, do not drive CDP by hand; write or run an evals/specs test instead — this skill is for exploration and debugging only
Electron CDP is used for development test tooling; user browser tasks should use the built-in OpenWork Browser target
Undocumented: platform support, license, and any capabilities beyond those described in the SKILL.md
Confirm an OpenWork target appears via browser_list with browser_url http://127.0.0.1:9823
Verify the composer fill succeeded by checking the editor's innerText before clicking Run task
Confirm the session response by checking document.body.innerText or the current URL; the expected smoke response is 'Hello from the Electron browser test.'
AI Search
Find projects, verify facts, compare options, or turn a complex need into an actionable plan
Try a searchA click only fills the search box; you stay in control