Sign inSign up

docker/sbx-kit-open-interpreter-mixin

Verified Publisher

By Docker, Inc.

•Updated 9 days ago

Open Interpreter as a mixin -- the agent's own uv tool installation in an overlay, with the proxy...

Sandbox Kit
0

92

docker/sbx-kit-open-interpreter-mixin repository overview

Digest

sha256:d1fa017197ba…

Size

176.3 MB

Schema

v3

Pushed

9 days ago

Specificationspec.yaml
MIXIN

Open Interpreter as a mixin -- the agent's own uv tool installation in an overlay, with the proxy-managed Anthropic and OpenAI credentials, the auth-resolution startup hook and the egress the agent needs to write and run code. Layer it onto a shell base and run `interpreter`.

Arguments
NameRequiredDefaultDescription
versionOptional0.4.3

Open Interpreter release to install

Provides[email protected]
CapabilitiesExpand a row to see its full configuration. See the full spec for the complete descriptor.
TypeRequiredDescription
com.docker.sandbox/network-policy@1Required—
com.docker.sandbox/credential@1OptionalAnthropic API access (API key or claude.ai OAuth)
com.docker.sandbox/credential@1OptionalOpenAI API access
com.docker.sandbox/lifecycle@1Required—
com.docker.sandbox/agent-context@1Required—

Apply this mixin to a sandbox

sbx run <agent> --kit docker/sbx-kit-open-interpreter-mixin:latest

Make sure you have docker sbx installed

Run the following command to install sbx on your machine.

macOS
brew install docker/tap/sbx
Windows
winget install Docker.sbx
Learn more about docker sbx⁠

Note

Experimental: Sandbox Kit v3

This kit uses the experimental Sandbox Kit specification⁠, specifically v3⁠. The format and runtime behavior may change before v3 is stable.

⁠open-interpreter-mixin

Open Interpreter⁠ as a mixin — the same agent as the open-interpreter⁠ workload kit, packaged as an overlay you layer onto a shell base instead of running as the sandbox's own image.

⁠Usage

sbx run --kit ./open-interpreter-mixin/ <shell-workload>

Or from a git URL targeting this repo:

sbx run --kit "git+https://github.com/docker/sbx-kits-contrib.git#dir=open-interpreter-mixin" <shell-workload>

The base workload keeps its own launch command, so nothing starts the agent for you:

open-interpreter-start      # applies the resolved Anthropic auth state, then execs
interpreter                 # or straight to the binary

⁠What it carries

  • The uv tool install of open-interpreter, copied out of a build stage on the same base the workload uses. The install cannot be relocated — uv bakes absolute paths into the venv, and the C toolchain psutil needs on arm64 is apt content, not copyable content — so the overlay runs the unmodified install and copies the resulting tree at the path it was built at. The toolchain stays behind in the build stage.
  • The standalone Python 3.12 runtime uv downloads for it, so the overlay does not depend on the composed base's Python version.
  • The proxy-managed anthropic (API key or OAuth) and openai credentials, the model-API and package-index egress, and the auth-resolution startup hook.

⁠A note on files/

files/ here is a byte-identical copy of ../open-interpreter/files/. A kit's build context is its own directory, so an overlay cannot reach its sibling workload's assets; diff -r between the two directories is what catches drift.

⁠What it deliberately leaves to the base workload

  • The launch command. A mixin does not set an entrypoint.
  • The base's apt mirrors. The workload lists them because a workload owns its base image; here they belong to whatever base you compose onto.
  • The context-file profile. filename: is workload-only; this kit contributes a body through contentFile.
  • sbx@1. A mixin's image config does not become the composed image's.

This week's pulls

Pulls:

55

Last week

Learn more⁠