本文へ移動
cccskills
無料GitHub で公開

cua-local-sandbox

Run Cua sandboxes locally - no API key required. Covers Docker (XFCE/Kasm) for Linux containers, QEMU for full VMs, Lume for macOS guests on Apple Silicon, and Tart for Apple VZ VMs. Use when the user wants a local sandbox, wants to keep things off the cloud, or asks "spin up an Ubuntu desktop", "open a sandbox VM", "let me try this safely first".

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Local Cua sandbox

In mode: "local" (the default), cua_sandbox_start spins up a sandbox on your machine. Cua picks the runtime from the image OS unless you pass runtime explicitly.

Runtime selection

OS imageAuto runtimeWhen kind: "container"Override
linuxDocker (XFCE)XFCE Docker (trycua/cua-xfce)qemu, docker
macosLume (Apple Silicon required)-tart
windowsQEMU Docker--
androidAndroid Emulator--

kind defaults to "container" for Linux (fast, GUI via XFCE) and "vm" for everything else.

Prerequisites

  • Docker Desktop or Colima for Linux containers / Windows VMs
  • macOS Apple Silicon for Image.macos() via Lume
  • qemu installed locally for runtime: "qemu"

Cua will print actionable errors when prerequisites are missing.

Example calls

// Fast Linux XFCE container - recommended for most automation
cua_sandbox_start({ os: "linux", kind: "container" })

// Full Ubuntu VM via QEMU
cua_sandbox_start({ os: "linux", kind: "vm", runtime: "qemu" })

// macOS guest via Lume (Apple Silicon host only)
cua_sandbox_start({ os: "macos", kind: "vm", runtime: "lume" })

Performance notes

  • XFCE containers are fastest (seconds to start).
  • QEMU VMs take ~30s for Linux, several minutes for Windows.
  • macOS Lume VMs need a one-time lume pull for the image.

After start

The returned sandbox name is also used as name for cua_sandbox_stop and the sandbox argument of control tools. If you only use one sandbox you can omit the sandbox argument; the manager remembers the first sandbox as default.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use Cua's cloud sandboxes via cua.ai. Requires CUA_API_KEY. Cloud sandboxes are isolated VMs run by trycua with billing per usage. Use when the user wants no local Docker/QEMU, wants Windows/macOS guests without Apple Silicon, or explicitly asks for cloud.

日本語の概要は準備中です。原文の説明を表示しています。

code-yeongyu/pi-cua-integration72026年10月7日 更新

Mouse, keyboard, and scroll primitives for cua_click / cua_type / cua_key / cua_scroll. Reference for action shapes, modifier keys, key chord syntax, and screenshot-driven targeting workflows.

日本語の概要は準備中です。原文の説明を表示しています。

code-yeongyu/pi-cua-integration72026年10月7日 更新

Drive the user's host machine directly through Cua, with no sandbox. Maps to Cua's Localhost API. Higher risk - the agent can click, type, and run shell commands on the real desktop. Use only when the user explicitly opts in and read the safety section first. Triggers - "control my computer", "click here", "use my real Chrome", "no sandbox", "내 컴퓨터 자동화".

日本語の概要は準備中です。原文の説明を表示しています。

code-yeongyu/pi-cua-integration72026年10月7日 更新

pi-cua-integration is a Pi/Senpi extension that bridges Cua (trycua/cua) for computer-use sandboxes and host control. MUST USE when the user asks to drive a desktop UI, take screenshots, run a "computer use" task, control a sandbox, or invoke any cua_* tool. Triggers - "cua", "computer use", "sandbox", "screenshot the desktop", "click the screen", "take over the browser", "샌드박스 켜줘", "스크린샷 찍어", "내 컴퓨터에서 자동화".

日本語の概要は準備中です。原文の説明を表示しています。

code-yeongyu/pi-cua-integration72026年10月7日 更新

code-yeongyu のスキルをすべて見る

このスキルの問題を報告する