neptune sandbox
Manage AgentComputer cloud VMs for remote builds, refinement, and analysis
neptune sandbox
Manage AgentComputer cloud sandboxes used for remote build, refinement, porting, and malware analysis. Sandboxes are provisioned on demand when you pass --sandbox to rebuild, port, or analyze-malware, or you can manage them directly.
Usage
neptune sandbox <COMMAND>Commands
| Command | Description |
|---|---|
list | List all active sandboxes |
destroy-all | Destroy all active sandboxes |
login | Store an AgentComputer API key |
Authentication
Neptune resolves the AgentComputer API key in order:
[sandbox] api_keyin~/.config/neptune/config.tomlAGENTCOMPUTER_API_KEYenvironment variable- Stored credentials from
neptune sandbox login
Examples
# Store your API key
neptune sandbox login
# List running sandboxes
neptune sandbox list
# Tear down all sandboxes
neptune sandbox destroy-allConfiguration
Sandbox behavior can be configured in ~/.config/neptune/config.toml:
[sandbox]
api_key = "sk-..."
auto_teardown = true
max_lifetime_secs = 3600| Key | Default | Description |
|---|---|---|
api_key | AgentComputer API key | |
auto_teardown | true | Automatically destroy VMs after use |
max_lifetime_secs | 3600 | Maximum VM lifetime in seconds |
Using --sandbox with other commands
Pass --sandbox to offload execution to a remote AgentComputer VM:
neptune rebuild firmware.bin --refine --sandbox
neptune port ./neptune-rebuild --target aarch64-unknown-linux-gnu --sandbox
neptune analyze-malware sample.bin --sandbox --output ./casesWhen --sandbox is active, Neptune provisions a VM, uploads the binary, runs the operation remotely via SSH, downloads results, and optionally tears down the VM.