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: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.
Add computers to your application
Tell superun who can use a computer, who owns each instance and which actions are needed. For example:Choose a control method
Let the General Agent operate a computer
For example: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: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.
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.
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.
FAQ
The General Agent already has a sandbox. Why use Cloud Computer?
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.
Do I have to use an agent?
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.
Does enabling the plugin automatically add a computer page to my app?
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.
Should access keys be placed in frontend code?
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.
Can I manage or upload desktop templates?
Can I manage or upload desktop templates?
The plugin currently manages instances, not templates. Available configurations and environments are those offered in the product.

