Skip to content
Open Interpreter AI Agents · Open Interpreter 0.4.2+sushi.2 Launch on AWS

Operations

This page covers running Open Interpreter day to day: how it is secured, how it is updated, what to back up, and how to get help.

Security model

  • No listening ports. Open Interpreter is a command-line tool you start yourself. The image adds no web UI, background service or network listener.
  • Confirmation by default. The profile sets auto_run: false, and the interpreter command refuses -y and --auto_run unless you set SUSHI_OI_ALLOW_AUTO_RUN=1 for a session.
  • No baked secrets. The image contains no provider key, password or private key. First boot checks that no api_key: is in the profiles.
  • Code runs as you. Approved code runs as the ubuntu user, which can use sudo. Treat the instance as disposable and keep unrelated data off it.
  • SSH. Password authentication and root login are turned off.
  • No AWS access by default. Attach only AmazonSSMManagedInstanceCore until a task needs more. Code that Open Interpreter runs can use any permission the instance role has.
  • Your data goes to your provider. Your requests, and the code output the model needs to see, are sent to the model provider you chose. Check that provider's data policy before you use it with private data.

First-boot service

sushi-open-interpreter-firstboot.service runs at every boot. It creates the profiles and the workspace if they are missing, and leaves existing files unchanged. It also clears leftover cache directories under /home/ubuntu that are not owned by ubuntu. There is no Open Interpreter service to start or stop.

systemctl status sushi-open-interpreter-firstboot --no-pager
sudo journalctl -u sushi-open-interpreter-firstboot --no-pager

Updates

  • Ubuntu packages get security updates automatically through unattended upgrades.
  • Open Interpreter and its Python dependencies are pinned in /opt/open-interpreter/venv. A new release comes as a new version of the AMI: launch it, copy your workspace and profile over, and retire the old instance. A new AMI version does not update running instances.

The upstream command checks PyPI for a newer version when it starts. Ignore that notice on this image.

Do not upgrade Open Interpreter in place

Running pip install --upgrade in /opt/open-interpreter/venv replaces the tested, pinned build. Launch a new version of the AMI instead.

Backups

Before you replace an instance, copy what you want to keep:

  • /var/lib/open-interpreter/workspace and any other files you worked on.
  • ~/.config/open-interpreter/profiles/default.yaml, if you changed it.

The root volume is the only disk. There is no separate data volume. Snapshot it if you need a full copy.

Check the installation

The image includes a self-test that runs as root. It checks the pinned build, the profile defaults, the ownership of the ubuntu home directory, a local Python run as ubuntu in the workspace, and that the interactive prompt starts for the ubuntu user without a model key:

sudo /opt/sushi/bin/smoke.sh

No model is called. The Python run leaves a small file, smoke-sum.txt, in the workspace.

Support

Software Sushi provides installation and configuration guidance for this image. Email info@softwaresushi.com with your product version and the steps you took. Never send credentials or private data. Guaranteed response times require a separate agreement. This offer does not include upstream Open Interpreter support.

Last updated October 13, 2026 · Suggest an improvement