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

# superun Cloud Computer

> Add an interactive Linux cloud desktop to your app, with remote access, command execution and agent control, billed through compute credits.

## What it is

superun Cloud Computer gives your application a Linux computer running in the cloud. Users can view and operate its desktop, use a browser, work with files, or delegate tasks to an agent.

Describe what you need in your project chat. superun connects the service, writes the backend logic and builds the interface. For example:

```text theme={null}
Add cloud computers to my app. Users should be able to create their own computer,
open its desktop to use a browser, check its status and delete it when finished.
```

Use it for applications that need browser interaction, desktop software or command execution. Connect it to a [superun General Agent](/superun/integrations/superun-agent) to let an agent perform tasks on the computer.

***

## Enable and manage instances

Open your project, go to **Development → Skills**, and find **superun Cloud Computer**. You can also ask for the integration in project chat; superun handles the necessary setup and application code.

Once enabled, the plugin provides instance management for the project:

* **Create** an instance with a resource configuration and a running timeout.
* **List and filter** instances by status, with running instances shown by default. Each card displays CPU, memory and disk specifications.
* **Open the desktop** of an existing instance and interact with it.
* **View details** on a timeline of running, light-sleep and deep-sleep periods. Hover over a period to see its compute credits.
* **Delete** instances you no longer need.
* **View consumption details** for settled cloud-computer charges.

This is the project maintainer's management interface. The computer list, desktop interface and permissions available to your app's users are built to match your product requirements. The plugin does not provide template creation or editing.

***

## Add computers to your application

Tell superun who can use a computer, who owns each instance and which actions are needed. For example:

```text theme={null}
Give each signed-in user their own cloud computer. Show a computer list on the left
and the remote desktop on the right. Users can only access their own computers,
with controls to create, delete and check their status.
```

Your application can have a **management area** for creating, inspecting, renewing, sleeping, resuming and deleting instances, and a **workspace** for desktop interaction, browser use, files and commands. Include only the controls your users need.

The platform's preview entry does not automatically become a page in your application. Ask superun to build the in-app desktop preview and interactions you want.

***

## Choose a control method

| Method | How it works | Required integrations |
| - | - | - |
| Direct control | Users operate the remote desktop, or your app performs specified actions through the SDK | Cloud Computer |
| General Agent control | Your app's agent observes and operates the computer through tools | Cloud Computer and General Agent |
| DSH inside the host | Send natural-language tasks to preinstalled DSH; it executes them and returns progress and results | Cloud Computer and superun AI; General Agent is also required when it delegates the tasks |

### Let the General Agent operate a computer

For example:

```text theme={null}
Let my app's General Agent operate the user's selected cloud computer:
open a browser and fill in forms, with the desktop visible on the right.
```

The agent first uses the application's UI structure to identify and operate controls. When controls are inaccessible through that structure, it falls back to screenshots, mouse and keyboard input. Support varies between applications, so validate it with your actual business software.

### Recommended: delegate computer tasks to DSH

DSH (DeepSeek Harness) is an agent framework preinstalled in the cloud computer. Your app can submit a task, receive its ID, continue the conversation, inspect progress or wait for the result. For example:

```text theme={null}
Build a computer assistant using the preinstalled DSH. Users describe their tasks;
the page shows progress, final results and the remote desktop, with follow-up chat
and cancellation. I choose DSH and accept its additional superun AI model costs.
```

<Warning>
  Enable [superun AI](/superun/integrations/ai) before using DSH. DSH model calls consume additional compute credits on top of cloud-computer charges. Any existing General Agent usage is still billed as usual. superun explains the differences so you can choose whether to use DSH.
</Warning>

DSH suits computer tasks described in natural language. For a remote desktop or fixed SDK actions, direct control avoids introducing DSH model calls. Other agent frameworks can also integrate with Cloud Computer; it is not limited to superun General Agent.

***

## Timeouts, sleep and data

* **The running timeout is a lifecycle countdown**, not an inactivity timer. Opening the desktop or executing commands does not automatically renew it. Ask superun to implement renewal for longer sessions.
* **Sleep and deletion are different**: sleep preserves state for later resumption; deletion destroys the instance. Save important files to your application's persistent storage first.
* **Sleep is not free**: running, light sleep and deep sleep have different billing rules. Deep sleep still incurs snapshot-storage charges.
* **Closing the page does not stop the computer**: sleep or delete it when appropriate. Disabling the plugin does not replace instance deletion.

If you want automatic sleep after inactivity and resume on use, specify that requirement so superun implements it in your application's backend.

***

## Billing and consumption details

Cloud Computer consumes **compute credits** based on the instance's resources, lifecycle state and time spent in that state. Charges use the same credit balance as other platform services. Settlement normally runs hourly and is also triggered by key lifecycle changes such as deletion.

To review charges:

* Open the plugin's **Consumption details** for settled usage.
* Open an instance's **Details** to see lifecycle periods and their compute credits on the timeline.

<Note>
  Consumption details and timeline amounts may appear after a settlement delay. A new instance or recent state change with no displayed charge is not necessarily free; the final settlement record is authoritative.
</Note>

***

## FAQ

<AccordionGroup>
  <Accordion title="The General Agent already has a sandbox. Why use Cloud Computer?">
    The General Agent's built-in sandbox starts and stops with its conversation, making it suitable for tasks such as running code and processing files during a chat. Cloud Computer has an independently managed lifecycle: renew, sleep, resume or delete it as needed. It suits more complex, longer-running work that needs a retained environment across multiple sessions. Your General Agent can operate the same cloud computer and continue work in a later conversation. You still need to manage timeouts and costs; this does not mean unlimited runtime or retention.
  </Accordion>

  <Accordion title="Do I have to use an agent?">
    No. Offer a desktop for manual use or implement specific SDK actions. Choose General Agent or DSH integration when you need natural-language control.
  </Accordion>

  <Accordion title="Does enabling the plugin automatically add a computer page to my app?">
    No. Enabling it provides the service and project management interface. Ask superun to build your app's computer pages, ownership rules and access controls.
  </Accordion>

  <Accordion title="Should access keys be placed in frontend code?">
    No. Your app's Supabase backend uses the cloud-computer credentials. For DSH, proxy model requests through the application backend so the platform model key stays outside the host. A business credential used inside the host may still be readable by users or tools with OS access; restrict its permissions and scope to match your business.
  </Accordion>

  <Accordion title="Can I manage or upload desktop templates?">
    The plugin currently manages instances, not templates. Available configurations and environments are those offered in the product.
  </Accordion>
</AccordionGroup>

After enabling Cloud Computer, superun uses the accompanying skill for API references and code examples.

## Related documentation

* [superun General Agent](/superun/integrations/superun-agent)
* [superun AI](/superun/integrations/ai)
* [superun File Storage](/superun/integrations/storage)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.