A sandbox lifetime is a workflow decision: using Never in Lizard

Description and use

Setting the sandbox lifetime to "Never" in Lizard prevents premature deletion during long builds and review waits, but requires explicit cleanup after completion.

Problem

Fixed sandbox expiry can delete a working environment before a task finishes, causing loss of progress when a build is running, an agent is waiting for review, or a laptop is closed.

Outcome

Setting sandbox lifetime to "Never" prevents unintended deletion during long-running or review-dependent tasks, while still requiring explicit cleanup to avoid unnecessary compute charges.

Workflow

• 1. In the Lizard dashboard, select "Never" under "Delete Sandbox after" when creating a sandbox.
• 2. Or use the CLI: lizard sandbox create --size small --timeout 0 to create a sandbox that never expires.
• 3. Run your development task (e.g., install dependencies, start a long build, wait for review).
• 4. If needed, pause the sandbox (if supported) to preserve memory and files while you are away.
• 5. When the task is finished, manually delete the sandbox or let the owner decide to clean it up.

Evidence

In the dashboard, choose Never under Delete Sandbox after when creating a sandbox. This disables scheduled expiry.

Source

With the Lizard CLI, the corresponding creation flag is --timeout 0. For example: lizard sandbox create --size small --timeout 0

Source

The current CLI default is a five-minute lifetime, not an indefinitely running workspace.

Source

The update also describes pausing a supported sandbox and resuming it later with memory and files retained.

Source

At the Small compute rate of $0.009 per hour, continuous execution for a 30-day month works out to: 30 days × 24 hours × $0.009 = $6.48

Source