Virtual device
A virtual device is a cloud-hosted machine your workspace agents share — always on, with a pre-configured environment for code, browsing, and file work.
A virtual device is a cloud-hosted machine that lives in Nebula's infrastructure and stays on around the clock. It comes pre-configured with the tools your agents need — a filesystem, common runtimes, a browser, and the ability to host a live server.
What it can do
Read, write, and organize files that persist between conversations. Everyone in the workspace sees the same filesystem; everyone's work lands in the same place.
Run Python, Bash, or TypeScript with real package managers. Common data libraries like pandas, numpy, matplotlib, and requests come pre-installed.
Control a full browser to interact with websites and web apps — fill forms, click buttons, extract data, log in to dashboards.
Spin up a web server, get a public URL, and share it for review or testing. Useful for prototypes, previews, and internal tools.
Always on
A virtual device runs continuously. It doesn't sleep between conversations, doesn't reset when someone closes the app, and doesn't lose state when members switch devices of their own.
| Typical AI chat | Virtual device | |
|---|---|---|
| Files between sessions | Lost | Persisted |
| Background tasks | Not possible | Runs continuously |
| Scheduled automations | Not possible | Fires on schedule |
| Shared across members | No | Yes — everyone sees the same files |
What it makes possible
Long-running jobs
Kick off a scrape, leave it for hours, come back to the results. The device keeps running.
Multi-step workflows
Download → process → store → query. State lives between conversations.
Custom tools
Install your own scripts and binaries. Agents in the workspace can use them in any thread or automation.
Shared drop zone
Upload a file in one thread; another agent in another thread can read it from the same filesystem.
Live previews
Build a test site or app and get a real URL to share with teammates for feedback.
Multi-agent handoff
Multiple agents share the same files, reading each other's outputs without manual passing.
Adding a virtual device
One device per workspace is marked Primary — agents reach for it by default. The first virtual device you create becomes the primary; you can switch later from any device card.
Choosing a size
Pick a size when you create the device, and upgrade later from the device card as your work grows. The card and detail page show the active size and its specs.
| Size | CPU | RAM | Disk |
|---|---|---|---|
| Small | 2 CPU | 8 GB | 40 GB |
| Medium | 4 CPU | 16 GB | 250 GB |
Small handles everyday research, writing, and light scripting. Step up to Medium for heavier data work, larger files, or several agents working in parallel.
Watching disk usage
The device card and the detail page show a disk-usage bar — used of total, with free space remaining — that turns amber past 75% used and red past 90%. The bar appears once the device reports its first reading.
Running low? Ask Nebula to clear out files you no longer need, or upgrade the device to a larger size.
Related
Devices
Devices are the machines your workspace agents use to do real work. Choose a virtual device in the cloud, a local device on your own computer, or both.
Local device
Connect your own computer as a Nebula device. Install the desktop app and your agents can work with your files, your software, and your network.