How do I install the Daytona Chrome Cdp skill?

Run npx skillmds add thedixitjain/daytona-chrome-cdp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Daytona Chrome Cdp safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Daytona Chrome Cdp?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Daytona Chrome Cdp free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Daytona Chrome Cdp?

thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Daytona Chrome Cdp by thedixitjain — Agent Skill

Name: Daytona Chrome Cdp
Rating: 4.666666666666667 (3 reviews)
Author: thedixitjain

File contents

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'"

Source: different-ai/openwork → .opencode/skills/daytona-chrome-cdp/SKILL.md

---name: daytona-chrome-cdpdescription: 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.---# Daytona Standalone Chrome CDPUse this skill when a Daytona sandbox needs a normal Chrome/Chromium browser inthe XFCE display, separate from the Electron app. This is useful for Den Websign-in, OAuth provider setup, browser-only admin flows, and checking what a userwould see in a regular browser.## Launch ChromeRun inside the Electron or server sandbox:```bashdaytona 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 installChromium in the sandbox only when needed.## Get The CDP URL```bashCHROME_CDP_URL=$(daytona preview-url "$SANDBOX" -p 9222 2>/dev/null | grep -v '^time=')```Then connect browser tools:```textbrowser_list({ browser_url: CHROME_CDP_URL })```## Verify It Is Not ElectronAfter selecting the Chrome target:```jsnavigator.userAgent```Expected: contains `Chrome/` or `Chromium/` and does not contain `Electron/`.## Drive A Web FlowUse normal browser tools:```textbrowser_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 orsign-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```bashdaytona exec "$SANDBOX" -- "bash -lc 'pkill -f \"chromium.*remote-debugging-port=9222\" || pkill -f \"chrome.*remote-debugging-port=9222\" || true'"```---**Source:** [`different-ai/openwork`](https://github.com/different-ai/openwork) → `.opencode/skills/daytona-chrome-cdp/SKILL.md`

Frequently asked questions