skills.rest
Devin-AXIS
Devin-AXISCOMMUNITY
Explore all skills by this author →
GitHub

daytona-chrome-cdp

Launch and control standalone Chrome browsers in a Daytona sandbox via CDP.

3.2k|690|Updated Aug 25, 2025
Search Tags:#OAuth#sandbox#web debugging#Chrome#remote debugging#Daytona
One-click install
npx skills add https://github.com/Devin-AXIS/iPolloWork --skill daytona-chrome-cdp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: daytona-chrome-cdp
Source: https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/daytona-chrome-cdp
Command: npx skills add https://github.com/Devin-AXIS/iPolloWork --skill daytona-chrome-cdp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

daytona-chrome-cdp allows users to launch and control a standalone instance of Chrome within a Daytona sandbox, facilitating tasks that require browser-specific features outside of the Electron framework.

Core Features & Use Cases

  • Standalone Chrome Execution: Provides the ability to use a full browser experience for scenarios not suitable for Electron apps.
  • Browser Integration: Facilitates tasks such as web sign-in, OAuth provider setup, and web-only admin flows.
  • CDP Utilization: Utilizes Chrome DevTools Protocol (CDP) for debugging and control, making it ideal for development and debugging workflows.
  • Use Case: This skill can be used to test a website's OAuth flow without requiring an Electron app or to simulate a web-based login process.

Quick Start

Start the standalone Chrome browser in the Daytona sandbox to execute tasks requiring web-based interaction.

Frequently Asked Questions about daytona-chrome-cdp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I control a standalone Chrome browser in a Daytona sandbox?▼

You can control standalone Chrome in a Daytona sandbox by using this Skill to launch a browser instance that supports remote debugging. It enables direct browser interaction for development workflows without requiring an Electron application.

Can I test an OAuth provider flow without using an Electron app?▼

Yes, testing an OAuth flow without an Electron app is possible by launching a standalone Chrome instance in a Daytona sandbox. This provides a full web browser experience to simulate web-based login processes and provider setups.

What is the Chrome DevTools Protocol used for in a Daytona sandbox?▼

The Chrome DevTools Protocol (CDP) is utilized for debugging and control within the Daytona sandbox. It allows developers to execute browser-specific tasks, web sign-ins, and web-only admin flows in a standalone development environment.

When do I need a standalone Chrome instance instead of an Electron app for web debugging?▼

You need a standalone Chrome instance when your web debugging tasks require browser-specific features outside the Electron framework. This approach is ideal for scenarios like simulating web-based logins or testing admin flows.

Does this approach require remote debugging support to run Chrome in a sandbox?▼

Yes, remote debugging support is required to control the standalone Chrome browser in a Daytona sandbox. This feature allows the development environment to facilitate browser-specific debugging and web sign-in tasks.

Related Skills

Explore More Software Engineering Skills→
udecodeudecode
434

browser-debug-setup

Set up a persistent Chrome debugging environment with a dedicated profile.

Official
Intermediate
BenAIOSBenAIOS

agent-browser

Automate Chrome browser interactions and web scraping via CDP.

Official
Advanced
AskTinNguyenAskTinNguyen

browser-testing-with-devtools

Inspect live pages, DOM, console logs, and network activity via Chrome DevTools MCP.

Community
Advanced
NagyViktNagyVikt
2

agent-browser

Automate browser interactions and capture screenshots for UI verification.

Community
Advanced