# Use Orca, editors and coding agents

Start a sandbox from Orca or connect your editor and coding tools. Follow the detailed tool guides on GitHub.

## Choose how you work

Use Orca to create a sandbox for each workspace, or create a sandbox yourself and connect over SSH. VS Code and Cursor open the same project files. Herdr keeps agent panes running while you disconnect from a running sandbox.

These integrations are published. Orca sandbox creation, SSH and stop/start have passed production checks. Other editor and coding-tool integrations have been tested on shared. Starting a sandbox depends on your workspace permissions, credit and regional capacity.

## Install, sign in and select a workspace

On macOS or Linux, install rzv and OpenSSH on your computer. Replace \<workspace-id\> with a workspace from the list. The installer supplies the current rzv executable, with no separate runtime to install.

Your rzv sign-in renews automatically. Sign in again after 14 days without use or 30 days from sign-in, whichever comes first. Your AI provider sign-in is separate.

On your computer · replace \<workspace-id\>

```
curl -fsSL https://runzivo.dev/downloads/rzv/install.sh | sh
rzv login
rzv workspaces list
rzv workspaces select <workspace-id>
```

[CLI installation and supported platforms](https://runzivo.dev/docs/cli/)

[Detailed sign-in and credential reference on GitHub](https://github.com/Runzivo/rzv-cli/blob/main/docs/login.md)

## Open a sandbox in VS Code or Cursor

Create a sandbox with the quickstart, wait for it to run, then replace \<sandbox-id\> below. Install your editor's Remote SSH extension and open the generated \<sandbox-id\>.rzv host. Work in /workspace. The GitHub guide covers editor commands, connection settings and troubleshooting. Sandbox SSH from Windows is not supported yet.

On your computer · replace \<sandbox-id\>

```
rzv sandboxes ssh-config <sandbox-id> --write
ssh <sandbox-id>.rzv true
```

[Create your first sandbox](https://runzivo.dev/docs/sandboxes-quickstart/)

[VS Code and Cursor connection guide on GitHub](https://github.com/Runzivo/rzv-cli/blob/main/docs/editors.md)

## Create the workspace from Orca

Install the Runzivo Sandboxes plugin from Orca's plugin directory and follow its setup guide. When creating an Orca workspace, choose a Runzivo sandbox under Run on. Orca creates the sandbox, copies the selected commit and connects over SSH. The plugin is publicly listed as version 0.1.1.

The plugin uses your Runzivo workspace's existing equivalent-minute balance. There is no separate Orca subscription or wallet. Sleep stops sandbox compute, wake starts it again, and delete removes its files. The sandbox lifetime continues while it sleeps.

[Runzivo Sandboxes in the Orca directory](https://www.onorca.dev/plugins/runzivo/rzv-orca-plugin)

[Plugin installation and requirements on GitHub](https://github.com/Runzivo/rzv-orca-plugin)

[Orca lifecycle command reference on GitHub](https://github.com/Runzivo/rzv-cli/blob/main/docs/orca.md)

## Use your own coding tools

Claude Code and Codex are included in the sandbox developer image, signed out. OpenCode and Herdr have installation and setup guides. Use your own authorized AI account or provider key inside the sandbox. Your provider bills model usage directly; Runzivo bills sandbox infrastructure.

Follow the tool's guide for sign-in, credentials and supported configuration. Keep provider keys out of chat prompts, copied commands and source control. Review changes and run your project's tests before pushing.

[Claude Code guide on GitHub](https://github.com/Runzivo/rzv-cli/blob/main/docs/claude-code.md)

[Codex guide on GitHub](https://github.com/Runzivo/rzv-cli/blob/main/docs/codex.md)

[OpenCode guide on GitHub](https://github.com/Runzivo/rzv-cli/blob/main/docs/opencode.md)

[Herdr guide on GitHub](https://github.com/Runzivo/rzv-cli/blob/main/docs/herdr.md)

## Stop, reconnect and keep your work

Files in /workspace, your home directory, installed tools, settings and saved sign-ins survive a stop and start within the sandbox lifetime. Disk retention across stop/start has been verified in production. Running processes and open sessions end at a stop. Back up settings you need, reconnect and start tools again after waking.

Sign out of a tool before stopping if you do not want its credentials retained. Do not assume a stop signs you out. A stop does not pause the lifetime. Expiry or deletion removes the sandbox and its temporary files. Copy or push work you need before expiry. Separate persistent disks follow their own lifecycle; disk charges are currently off.

[Sleep, wake and saved data](https://runzivo.dev/docs/sandbox-sleep-wake/)

[Lifetime and expiry](https://runzivo.dev/docs/sandboxes-lifetime/)

## Find technical details and share feedback

Use the website for the product guide and first steps. GitHub holds the detailed CLI and tool references, release notes and community feedback. Custom runner profile commands are published, but the production service remains switched off; existing runner labels continue to work.

[CLI 0.26.0 release notes and downloads](https://github.com/Runzivo/rzv-cli/releases/tag/release-2026-11-06-151513)

[Detailed CLI documentation index on GitHub](https://github.com/Runzivo/rzv-cli/blob/main/docs/README.md)

[Suggest an idea or vote on the roadmap](https://runzivo.dev/roadmap/)

On this page and page tools