Overview
Mounts allow you to attach external resources to your Devbox at creation time. This provides a flexible way to inject code, files, data, and AI agents into your Devbox environment without manually uploading or cloning after the Devbox starts. All mount types use the unifiedmounts parameter when creating a Devbox, with a type discriminator to specify the mount type.
Mount Types
Runloop supports four types of mounts:| Mount Type | Description | Use Case |
|---|---|---|
| Code Mount | Clone a GitHub repository | Working with existing codebases |
| Object Mount | Mount a storage object | Large datasets, model weights, archives |
| File Mount | Inject file content inline | Config files, scripts, small text files |
| Agent Mount | Mount a pre-configured AI agent | Running AI agents on your Devbox |
Using the Unified Mounts Parameter
All mounts are specified using themounts array parameter. Each mount object requires a type field to identify the mount type:
Choosing the Right Mount Type
- Code Mount: Best for cloning Git repositories. Supports private repos with authentication tokens.
- Object Mount: Best for large files, binary data, datasets, or archives. Objects are stored in Runloop’s storage and can be reused across Devboxes.
- File Mount: Best for small text files like configuration, scripts, or environment files. Content is provided inline.
- Agent Mount: Best for mounting pre-configured AI agents that can be run on your Devbox.
