How do I install the Daytona Chrome Cdp skill?

Run npx skillmds@latest add gabrielmoreira/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?

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

Daytona Chrome Cdp by gabrielmoreira

Name: Daytona Chrome Cdp
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

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 \"$DEN_WEB_URL\" >/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=')

Verify the target directly:

curl -fsS "$CHROME_CDP_URL/json/list"

Verify It Is Not Electron

The coded flow must assert that navigator.userAgent contains Chrome/ or Chromium/ and does not contain Electron/.

Drive A Web Flow

Create or reuse an evals/flows/*.flow.mjs flow and set its cdpTarget to a stable title or URL fragment for the standalone page. Drive the visible flow with ctx.clickText, ctx.fill, ctx.waitFor, and ctx.screenshot, then run:

pnpm evals --flow <flow-id> --cdp-url "$CHROME_CDP_URL"

Validate with the fraimz loop. Do not assume navigation or sign-in worked until the post-action URL, visible assertion, and frame prove 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'"

---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 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: ```bash 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 \"$DEN_WEB_URL\" >/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 ```bash CHROME_CDP_URL=$(daytona preview-url "$SANDBOX" -p 9222 2>/dev/null | grep -v '^time=') ``` Verify the target directly: ```bash curl -fsS "$CHROME_CDP_URL/json/list" ``` ## Verify It Is Not Electron The coded flow must assert that `navigator.userAgent` contains `Chrome/` or `Chromium/` and does not contain `Electron/`. ## Drive A Web Flow Create or reuse an `evals/flows/*.flow.mjs` flow and set its `cdpTarget` to a stable title or URL fragment for the standalone page. Drive the visible flow with `ctx.clickText`, `ctx.fill`, `ctx.waitFor`, and `ctx.screenshot`, then run: ```bash pnpm evals --flow <flow-id> --cdp-url "$CHROME_CDP_URL" ``` Validate with the `fraimz` loop. Do not assume navigation or sign-in worked until the post-action URL, visible assertion, and frame prove 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 ```bash daytona exec "$SANDBOX" -- "bash -lc 'pkill -f \"chromium.*remote-debugging-port=9222\" || pkill -f \"chrome.*remote-debugging-port=9222\" || true'" ```

Frequently asked questions

Daytona Chrome Cdp