OpenParable
Skip to content
← Back to skills

Daytona Chrome Cdp

Apps & Automation
daytona-chrome-cdp

Daytona Chrome Cdp is an Agent Skill for apps & automation published in the Devin-AXIS/iPolloWork repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Devin-AXIS/iPolloWork/blob/HEAD/.opencode/skills/daytona-chrome-cdp/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/daytona-chrome-cdp, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Daytona Standalone Chrome CDP

Use this skill when a Daytona sandbox needs a normal Chrome/Chromium browser in the XFCE display, separate from the Electron app. This is useful for Den Web sign-in, OAuth provider setup, browser-only admin flows, and checking what a user would see in a regular browser.

Launch Chrome

Run inside the Electron or server sandbox:

daytona exec "$SANDBOX" -- "bash -lc 'mkdir -p /tmp/daytona-chrome-profile; DISPLAY=:99 nohup chromium --no-sandbox --disable-dev-shm-usage --remote-debugging-address=0.0.0.0 --remote-debugging-port=9222 --user-data-dir=/tmp/daytona-chrome-profile about:blank >/tmp/daytona-chrome.log 2>&1 &'"

If chromium is missing, try google-chrome, google-chrome-stable, or install Chromium in the sandbox only when needed.

Get The CDP URL

CHROME_CDP_URL=$(daytona preview-url "$SANDBOX" -p 9222 2>/dev/null | grep -v '^time=')

Then connect browser tools:

browser_list({ browser_url: CHROME_CDP_URL })

Verify It Is Not Electron

After selecting the Chrome target:

navigator.userAgent

Expected: contains Chrome/ or Chromium/ and does not contain Electron/.

Drive A Web Flow

Use normal browser tools:

browser_navigate({ browser_url: CHROME_CDP_URL, target_id: TARGET_ID, url: DEN_WEB_URL })
browser_snapshot({ browser_url: CHROME_CDP_URL, target_id: TARGET_ID })
browser_click({ browser_url: CHROME_CDP_URL, target_id: TARGET_ID, uid: UID })
browser_fill({ browser_url: CHROME_CDP_URL, target_id: TARGET_ID, uid: UID, value: VALUE })

Validate with the daytona-flow-validator loop. Do not assume navigation or sign-in worked until the post-action snapshot or URL proves it.

Common Uses

  • Sign into Den Web while Electron remains on the desktop handoff screen.
  • Complete OAuth approval pages from a mock or real provider.
  • Configure web-only admin state before validating Electron sync.
  • Compare Den Web behavior against Electron cloud account behavior.

Stop Chrome

daytona exec "$SANDBOX" -- "bash -lc 'pkill -f \"chromium.*remote-debugging-port=9222\" || pkill -f \"chrome.*remote-debugging-port=9222\" || true'"