daytona-chrome-cdp
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.
pinned to #c2d3a52updated 2 months ago
Ask your AI client: “install skills/daytona-chrome-cdp”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/daytona-chrome-cdpmetahub onboarded this repo on the author's behalf.
If you own github.com/Devin-AXIS/iPolloWork on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
1,202
Last commit
2 months ago
Latest release
published
- #a2a-protocol
- #ai-agent-network
- #bnb-chain
- #ethereum
- #mcp-server
- #protocol
- #smart-contracts
- #token-economy
- #web3
- #x402-compatible
About this skill
Pulled from SKILL.md at publish time.
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.
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.c2d3a52· 2 months ago
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Kind-specific
3 passed1 warningSkill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: SKILL.md present
found at .opencode/skills/daytona-chrome-cdp/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
279 words · 2,183 chars · 6 sections · 6 code blocks
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Release history
1- releasecurrentc2d3a52warn2 months ago
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'"
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/daytona-chrome-cdp