---
title: "Sine Box: files, commands, and runtimes"
description: "Choose Lite or Sandbox, create a Box, manage files, and run commands. Understand VM runtime windows, backups, API permissions, and execution costs."
image: "https://docs.sinecloud.dev/opengraph.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.sinecloud.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Sine Box: files, commands, and runtimes

Sine Box provides independent file and execution spaces. It does not require Agents or a project. The product workspace and an individual Box are separate: after preparing a workspace, choose or create the resource that owns your files and execution history.

## Choose Lite or Sandbox

| Type | Execution | Billing basis |
| --- | --- | --- |
| Lite | Runs commands in a bounded shell without starting a Sandbox VM window. | Command wall-clock duration. |
| Sandbox | Requires an explicitly started VM window for live file access and commands. | Confirmed VM window duration, including idle time; commands inside the window are not charged again for execution. |

Select the runtime type at creation. Available types, features, and actions depend on release configuration, organization permissions, and runtime services. Basic Free access does not guarantee that every runtime capability is enabled.

## Create and select a resource

1. Sign in to [Console](https://sinecloud.dev/en/dashboard), select an organization, and open **Box**.
2. If no product workspace exists, an owner or admin prepares one. A project is optional; resources can belong directly to the organization.
3. Choose **Create Box**, select Lite or Sandbox, and complete the form.
4. Select the individual resource in the Box selector before opening Files, Commands, or Settings.

The product workspace ID differs from the individual `boxId`. Follow the next-step links after creation to retain the selected resource. Browsing pages and switching Boxes do not start a VM automatically.

## Use a Sandbox runtime window

1. Review the displayed price, available balance, and estimated reservation before starting.
2. Explicitly start the window. The default is ten minutes, with a maximum total window of thirty minutes.
3. Access live files or execute commands while the window is active. To extend it, renew the window; the additional reservation uses its original price.
4. Pause when you no longer need the VM and check that its state is confirmed.

A reservation estimate is not a locked price or a promise of admission. Reading files or submitting commands does not wake a paused Sandbox. Commands do not start the VM automatically. If status is unknown or a query fails, recover the original window instead of issuing a new start request.

## Work with files and commands

**Files** supports directory browsing, previews, and downloads. Writing and deleting require `fileWrite`. Command execution requires `boxRun` and valid price, balance, and runtime configuration.

Submit work and inspect the selected Box's history in **Commands and executions**. Commands use an `executionId`; Sandbox windows use a `leaseId`. If a response is lost, query the original `executionId` or `leaseId` to avoid repeating commands with side effects.

Access to a history summary does not grant access to full output. Cancelling a dispatched command requires runtime confirmation. Unknown status does not mean the work has stopped or a refund has occurred. Closing the page does not cancel execution either.

## Lifecycle, backups, and costs

Use **Settings** to manage the selected resource's lifecycle and durable backups. **Overview** also provides backup and historical window cost entries. Destruction is a separate action requiring confirmation of the exact resource ID. Suspended resource access and a stopped VM are different states; check both.

Opening a historical window from Billing only displays its financial details; it does not recover or start the current window. Use the explicit current-window action when you need runtime controls. [Organization Usage and Billing](/billing/) distinguish execution status, held reservations, and actual charges.

## Connect Agents or an application

[Agents](/products/agents/) can explicitly link a Box in the same organization and project scope. Two organization-level resources share the same project scope. Linking is optional and does not grant access to the other product.

For programmatic access, use the `/api/box/v1/{boxId}` address shown on the Box **API** page and create an [API key](/api-keys/) with Box and the necessary capabilities. A key with only Agents permission cannot access Box directly.

Source: https://docs.sinecloud.dev/products/box/index.mdx