daypi

Run the Pi coding harness inside a Daytona sandbox while interacting with it from your local terminal. daypi mirrors stdin/stdout to a remote PTY over Daytona's WebSocket so the experience matches running pi locally.

How it works

1. Provision or reconnect to a Daytona sandbox (with optional network allowlist for your proxy).
2. Install Pi in the sandbox if missing.
3. Open a PTY running pi and mirror your local terminal to it.

Setup

bun install
cp .env.example .env
# Set DAYTONA_API_KEY and optional proxy settings

Usage

bun run daypi
# or after linking: daypi

# Named sandbox
bun run daypi -- --sandbox my-project

# Force a fresh sandbox
bun run daypi -- --new

# Custom working directory inside the sandbox
bun run daypi -- --cwd /home/daytona/workspace

Press Ctrl+] to detach from the remote session without killing Pi. Re-run daypi to reconnect.

Environment variables

Variable	Description
DAYTONA_API_KEY	Daytona API key (required)
DAYTONA_API_URL	Daytona API URL
DAYTONA_TARGET	Daytona target region
DAYPI_SANDBOX_NAME	Default sandbox name
DAYPI_SANDBOX_IMAGE	Docker image for new sandboxes (default daytonaio/sandbox)
DAYTONA_AUTO_STOP_INTERVAL	Auto-stop minutes (default 5)
DAYPI_PROXY_URL	Proxy base URL injected into harness env
DAYPI_PROXY_ALLOW_HOSTS	Comma-separated hosts for sandbox domainAllowList
DAYPI_HARNESS_ENV	JSON object of extra env vars for the harness

Architecture

Local terminal ↔ daypi PTY mirror ↔ Daytona WebSocket ↔ pi TUI in sandbox.

Workspace sync (git clone / local upload) is not implemented yet; the harness starts in the sandbox default workspace.