Skip to main content
Each session runs its commands, files, and tools on one of two targets.

​
Managed sandboxes

Opengeni provisions a fresh sandbox for the session. Backends include Docker (the local default), Modal, local, and several cloud sandbox providers. The stock images include Terraform, Checkov, GitHub CLI, git, psql, a Python toolchain, common shell tools, and a Chromium-based browser. The headless image adds Azure CLI; the desktop image adds a graphical desktop and FFmpeg. A session’s files can be recovered from a snapshot after its sandbox is gone. A session can also run with no compute when it needs only model and tool calls.

​
Connected Machines

A Connected Machine is a computer you enroll: a laptop, workstation, build server, or GPU box. The agent runs on it directly.
  • Your credentials. The machine uses its own SSH keys, gh login, and Git setup.
  • Your files. Each session works in a folder on the machine.
  • Outbound only. The machine connects to Opengeni; it doesn’t need to be reachable from the internet.
  • Explicit consent. Enrollment asks for machine access, screen control is a separate consent, and you can revoke access in one click.
Self-hosted deployments must enable Connected Machines first. See Connect a machine.

​
Choosing a target

Pick a machine and working directory when you create a session, or switch the session’s target later. Child sessions use their parent’s machine unless told otherwise.