# Daytona Dev

Daytona development environment overview.

- Repository: https://github.com/Devin-AXIS/iPolloWork (7348 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -g -a claude-code -y`
Codex: `npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -g -a codex -y`
Cursor: `npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -g -a cursor -y`
Gemini CLI: `npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -g -a gemini-cli -y`

## Description

Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Skill: Daytona Dev Environment

Launch the iPolloWork Electron app in a Daytona cloud sandbox. The real desktop
app runs on Daytona's XFCE/noVNC desktop stack and is accessible through your
browser.

## Prerequisites

- Daytona CLI installed: `brew install daytonaio/cli/daytona` or download from [GitHub releases](https://github.com/daytonaio/daytona/releases)
- Logged in: `daytona login`
- Using the right Daytona organization for your workspace: `daytona organization use "<org-name>"`

## Quick Start

### 1. Create and start the sandbox

```bash
bash .devcontainer/test-on-daytona.sh [branch-or-commit]
```

The helper uses the VNC snapshot, starts noVNC/Vite/Electron, and prints the
URLs. If the snapshot is missing, create it with
`bash .devcontainer/create-daytona-ipollowork-snapshot.sh`.

Use the Daytona setup as four reusable pieces. Prefer the focused skills when a
request names one piece directly:

- `test-on-daytona.sh` for the real Electron/noVNC/CDP sandbox.
- `fraimz` for the observe -> act -> assert -> evidence loop.
- `test-server-on-daytona.sh` for the cloud Den server sandbox.
- `daytona-electron-den` for Electron connected to a Daytona Den server.
- `daytona-chrome-cdp` for standalone Chrome in the sandbox, separate from Electron.
- `ipollowork-eval-secrets:/daytona-secrets` for provider keys and eval-only secrets.
- `ipollowork-eval-artifacts:/daytona-artifacts` for screenshots, validation notes, and recordings.

Focused skills:

- `daytona-cloud-server` for cloud server and Den flows.
- `daytona-electron-den` for two-sandbox Electron + Den validation.
- `fraimz` for pass/fail validation and evidence.
- `daytona-chrome-cdp` for normal Chrome browser automation in Daytona.
- `daytona-secrets-volume` for adding or verifying secrets.
- `daytona-electron-test` for real Electron UI validation.
- `daytona-recording-artifacts` for screenshots, recordings, and PR evidence.

Or SSH in after the helper prints the sandbox name:

The rest: https://github.com/Devin-AXIS/iPolloWork/blob/HEAD/.opencode/skills/daytona-dev/SKILL.md