Skip to main content
This example installs OpenCode in a microVM and opens its terminal UI in a project mounted from your host. OpenCode edits the source checkout directly while its tools and dependencies stay inside the sandbox.

Run OpenCode

1

Start OpenCode

Replace ./my-project with the project directory you want OpenCode to work on:
The first run downloads the package and may take a couple of minutes. OpenCode should render its prompt and offer /connect for provider setup. Its XDG configuration, provider connections, and session data live on the sandbox’s 4 GiB root disk and remain available when the sandbox stops and starts.
For an isolated workspace, or when using microsandbox cloud, replace --mount-dir ./my-project:/workspace:rw with --copy-dir ./my-project:/workspace. To try the TUI without a project, use --mkdir /workspace instead.
2

Start another session

After leaving OpenCode, return to the same sandbox and workspace with:
3

Verify the installation

Exit the TUI, then run:
The pinned example prints 1.18.4.
4

Review or export changes

With the default writable mount, changes are already in the host checkout. Review the diff from either side of the mount:
If you chose the isolated --copy-dir alternative, export a patch from the sandbox:
Copy the patch to the host:
Check that it applies cleanly before applying it:
5

Clean up

Remove the sandbox:
Removing the sandbox also removes its provider connections, sessions, and OpenCode configuration. Changes made through the default workspace mount remain in the host checkout. Never copy an agent’s entire home directory back to the host.

Reference