Environments
An environment defines a space’s machine: CPU, memory, installed packages, and setup commands. All projects and chats in the space share the machine.
Use a custom environment when you need extra tools or computing resources. For example, video work might need ffmpeg and 8 GB of memory, and data analysis might need specific Python packages.
The default environment
Medium is the default: 2 vCPUs and 2 GB of memory. You can switch a space to another built-in size or to a custom environment at any time.
| Built-in size | CPU | Memory |
|---|---|---|
| Small | 1 vCPU | 1 GB |
| Medium | 2 vCPUs | 2 GB |
| Large | 4 vCPUs | 4 GB |
| Extra large | 6 vCPUs | 6 GB |
| 2X large | 8 vCPUs | 8 GB |
Environment options
A custom environment has these settings:
| Setting | What it controls |
|---|---|
| Name | How the environment appears when you pick one for a space |
| Machine size | CPU (1, 2, 4, 6, or 8 vCPUs) and memory (1 to 8 GB), in any combination |
| Packages | Packages to install with apt, npm, pip, or go |
| Build commands | Shell commands that run after the packages install, in order, such as corepack enable |
Packages and build commands are under Advanced settings.
Create an environment
Only organization admins can manage environments in Settings.
- Open Settings → Environment and select New environment.
- Enter a Name and set the Machine size.
- Open Advanced settings to add Packages and Build commands.
- Leave Build after creation on, and select Create environment.
ren environments create --name media --body @environment.jsonren environments builds start <environment-id>Put the machine size and packages in environment.json. Run ren environments create --help for the fields.
Edit or delete an environment
Rebuild after editing an environment. Spaces use the new build when their machines next resume from pause.
- Open Settings → Environment and select the environment.
- Change its settings and select Save changes.
- Select Rebuild on the environment to apply them.
To delete it, select the delete icon in the same dialog and confirm. Spaces that used it go back to their built-in size.
ren environments update <environment-id> --body @environment.jsonren environments builds start <environment-id>ren environments archive <environment-id>Builds
A build creates a machine image from the environment settings. Start one with Build, Rebuild, or Build after creation. Each environment runs one build at a time, and a build can take several minutes.
| Status | Meaning |
|---|---|
| Not built | No build has succeeded yet. Spaces stay on their built-in size. |
| Queued, Building | A build is in progress. |
| Ready | The latest build succeeded. Spaces use it when their machines next resume from pause. |
| Build failed | The last build failed. Spaces stay on their built-in size or the last ready build. |
A build fails when a package doesn’t install or a build command exits with an error. Fix the setting and select Rebuild. To list builds, run ren environments builds list.
Use an environment in a space
Give a project its own environment by putting it in its own space.
- Open the space and go to its Environment tab.
- Select Change, pick a built-in size or a custom environment, and confirm.
The tab shows the environment’s status, packages, and build commands, with Build or Rebuild.
ren pods update <space-id> --environment-id <environment-id>When changes take effect
A space’s machine pauses after about 10 minutes without activity. A new environment, a new build, or a different built-in size takes effect the next time the machine resumes from pause. A running machine is never swapped, so chats in progress aren’t interrupted.
A busy space may delay the change until the machine can pause. Files outside storage don’t transfer to the replacement machine. Projects, storage, and databases stay available.