Daytona Electron Den
Testing & Qualitydaytona-electron-denDaytona Electron Den is an Agent Skill for testing & quality published in the Devin-AXIS/iPolloWork repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Electron and Den, desktop plus cloud, two-sandbox e2e, cloud auth, marketplace, org policy, worker proxy, provider sync, desktop handoff. Validate Electron against a Daytona Den server with unified proof.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/Devin-AXIS/iPolloWork/blob/HEAD/.opencode/skills/daytona-electron-den/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/daytona-electron-den, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Daytona Electron Against Den
Use this skill for full-stack cloud behavior: one Daytona sandbox runs Den, and a separate Daytona sandbox runs the real Electron app pointed at that Den server.
Start The Server Sandbox
Use the server skill first:
bash .devcontainer/test-server-on-daytona.sh <branch-or-commit>
Record the printed values:
SERVER_SANDBOXDEN_WEB_URLDEN_API_URLDEN_WORKER_PROXY_URL
Validate server health:
curl -sf "$DEN_WEB_URL/api/den/health"
curl -sf "$DEN_API_URL/health"
Start Electron Against Den
bash .devcontainer/test-on-daytona.sh <branch-or-commit> \
--den-base-url "$DEN_WEB_URL" \
--den-api-base-url "$DEN_API_URL" \
--artifacts-volume
Add --require-signin when the expected behavior must be signed-out until cloud
auth completes. Add --record-video --recording-name <name> when PR evidence is
needed.
Validate Bootstrap
Before testing cloud behavior, prove Electron is using the Daytona Den server:
JSON.stringify({ hash: location.hash, text: document.body.innerText.slice(0, 1000) })
Then inspect the desktop bootstrap file:
daytona exec "$SANDBOX" -- 'cat /workspace/.ipollowork-daytona/desktop-bootstrap.json'
Expected: baseUrl is DEN_WEB_URL and apiBaseUrl is DEN_API_URL, not
production.
Desktop Handoff Pattern
For seeded/demo auth, create the handoff URL from the Den API, then paste it into Electron's Cloud Account sign-in code field. Do not rely on browser navigation alone as proof that desktop auth completed.
Validate all of these:
- Electron Cloud Account shows signed-in user/org state.
- Den API logs show handoff exchange or
/v1/me/orgs. - Electron UI can refresh cloud providers/workers/marketplace without production URLs.
Marketplace, Policy, Provider Sync
For each cloud feature, use the daytona-flow-validator loop:
- Assert server seed or API state.
- Act in Electron UI.
- Assert Electron visible state.
- Assert Den logs/API state if relevant.
- Capture screenshot or recording evidence.
Minimum assertions:
- Marketplace: package appears, install/remove changes local extension state.
- Org policy: restriction appears in Electron and persists after reload.
- Provider sync: Den-managed provider appears as imported/credential-ready, model can be selected, and task metadata uses the Den provider id.
- Worker proxy: worker/proxy failures affect only worker UI and recover after proxy restart.
Evidence
Report both server and Electron proof:
- Den Web/API health checks.
- Relevant
/tmp/den-*.logsnippets. - Electron CDP assertions and screenshots.
- Recording URL if requested.