Skip to main content
A Connected Machine is your own computer, enrolled once and then available as a session target. See Compute targets for how it compares to a managed sandbox.
Self-hosted deployments must enable Connected Machines first. Besides OPENGENI_SANDBOX_SELFHOSTED_ENABLED=true, they need the stream relay and NATS auth-callout; see the deployment guide.

​
Enroll interactively

1

Run the installer

Open the Machines page in your workspace, copy the one-line installer, and run it on the machine. It installs opengeni-agent as a background service and starts a device sign-in.
2

Approve the device

Open the printed URL, confirm the code, and choose who may use the machine: only you (the default), the workspace, or the organization. Screen control is a separate consent.
3

Done

The machine appears on the Machines page, ready to use.

​
Enroll headlessly

For fleets and CI machines, create a one-time enrollment token in the workspace and pass it to the installer:

​
Use it in a session

  • At creation: pick the machine, and optionally a working directory, when starting a session.
  • Later: switch a session to the machine, or back to its managed sandbox. History is unaffected.
The agent works in the chosen folder and uses the machine’s own Git setup.

​
Connect more workspaces

One agent can connect to several workspaces, even on different Opengeni deployments. Each connection is independent.
disconnect only stops the local link. The machine stays listed in the workspace until an admin removes it.

​
Revoke

Approval lasts until you revoke it; the agent renews its credentials automatically. Revoke a machine from the Machines page to cut off all access until it is enrolled again.

​
Programmatic enrollment

To build your own approval page, drive enrollment through the SDK. See the Connected Machines guide.