OpenCode

Use OpenCode with Edgenivo Sandbox through the Sandbox CLI or the OpenCode plugin.

Choose how to run OpenCode

Option	What runs in the sandbox	How you start
Sandbox CLI	The whole OpenCode session	Run `sandbox create opencode` in your terminal, before entering OpenCode
Plugin: automatic tools	Supported shell and file tools; OpenCode and model authentication stay local	Configure automatic mode, then use OpenCode normally. The first supported tool call creates the sandbox automatically
Plugin: remote workspace	The OpenCode server and agent tools	Inside OpenCode, enter `/warp` and select Edgenivo Sandbox

Use the CLI shortcut to run the whole OpenCode session remotely without installing the plugin. Your local project files aren't uploaded automatically. See Run a coding agent for CLI installation, authentication, and reconnecting or stopping the sandbox.

Use the plugin

Follow the plugin setup guide for installation and supported OpenCode versions. Choose one mode per OpenCode instance.

Automatic tools

Use OpenCode normally, with supported shell and file tools running in the sandbox.

Review changes: Ask the agent to run gitSync. It waits for changes to return and shows a separate local Git branch to review. Your current branch and working files stay unchanged.
Stop: Ask the agent to run sandboxStop to sync changes and stop compute.

Remote workspace

Remote workspaces require an AI Gateway API key. OAuth and subscription logins aren't supported. Follow the workspace guide to connect the key locally and set remoteConfig.model to one vercel/<provider>/<model> model.

Inside OpenCode, enter /warp and select Edgenivo Sandbox. Changes don't automatically sync back to your laptop. Use the workspace guide to export changes and stop the sandbox.

The plugin keeps your AI Gateway key outside the sandbox. Sandbox credential brokering adds it to requests for your configured model. Code in the sandbox can still make billable model requests.

Files and cleanup

Both modes upload committed files and Git history. Uncommitted changes and untracked files stay local. Check your Git history for secrets before starting.
Exiting OpenCode doesn't stop the sandbox. Stop it explicitly when finished. Retained storage remains billable after compute stops.
When upgrading from a version that copied credentials, create a fresh workspace. Upgrading doesn't remove credentials from existing sandboxes or snapshots.

Paseo

Pricing and Quotas

Was this helpful?