Configure environments

A cloud environment is a Docker container that runs on a virtual machine in the cloud. JetBrains Air creates this environment for the task, runs the agent in it, and removes it when the task is finished. If you return to the task later, JetBrains Air recreates the environment.

Use environment configuration to make the remote environment fit your project requirements. For example, you can choose the VM size, control internet access, and provide environment variables and personal secrets.

Create environment configurations in the web version of JetBrains Air: Settings | Environments.

Each user can have only one cloud environment configuration per repository. If you create one, JetBrains Air always uses it for your cloud tasks and automations in that repository. If you do not create one, JetBrains Air uses the default configuration.

Create an environment configuration

Create an environment configuration once for the repository and then reuse it for all cloud tasks in that repository.

Create an environment configuration

Open the web version of JetBrains Air at https://air.jetbrains.cloud.
Go to Settings | Environments.
Click New Configuration.
Select the repository.
Configure the environment:
- Repository – the repository this configuration applies to.
- VM Size – the amount of CPU, RAM, and disk space available for the task.
  Learn how to configure custom VM resources
- Internet access – whether the agent can access the internet, and if so, which domains it can reach.
  Learn how to configure internet access
- Additional domains – extra domains that are allowed when internet access is limited.
- Environment Variables – non-sensitive variables available in the cloud environment.
- Personal Secrets – sensitive values that are stored securely and exposed in the environment as variables.
  Learn more about personal secrets
Click Save.

Now, all tasks you run for this repository will use this configuration.

Configuration visibility and access

Environment configurations are currently personal.

You see and use only your own configurations. Other users can create their own configuration for the same repository, or have no configuration for it at all.

Shared cloud environment configurations are not supported yet. You cannot view, reuse, or inherit configurations created by other users.

This also applies to personal secrets stored in the configuration. Other users cannot view, reuse, or inherit them.

Use the default image

If you do not create a custom environment configuration, JetBrains Air uses the default environment configuration.

The default configuration uses the default image and does not add any custom variables, secrets, or internet access rules. This is the simplest option and is enough for tasks that do not require project-specific setup.

The default image includes almost all common tools and frameworks.

Use a custom image

Custom Docker images for cloud environments are not supported yet. This functionality is planned.

Provide personal secrets

Use Personal Secrets to store sensitive values such as tokens, passwords, or API keys.

Personal secrets are stored in encrypted form and are available in the environment as environment variables.

Because environment configurations are personal, secrets are not shared with other users.

Limit internet access

Use Internet access to control which external sites the agent can reach from the cloud environment. Limiting internet access helps reduce the risk of unintended access to untrusted resources.

The following modes are available:

Off – no internet access.
Specified domains – access only to domains you list in Additional domains.
Trusted domains – access to a preset list of domains commonly used for downloading dependencies, plus any domains you add manually.
The preset includes common source control, package management, and dependency domains.
alpinelinux.org anaconda.com apache.org apt.llvm.org archlinux.org azure.com bitbucket.org bower.io centos.org cocoapods.org continuum.io cpan.org crates.io debian.org docker.com docker.io dot.net dotnet.microsoft.com eclipse.org fedoraproject.org gcr.io ghcr.io github.com githubusercontent.com gitlab.com golang.org google.com goproxy.io gradle.org hashicorp.com haskell.org hex.pm java.com java.net jcenter.bintray.com json-schema.org json.schemastore.org k8s.io launchpad.net maven.org mcr.microsoft.com metacpan.org microsoft.com nodejs.org npmjs.com npmjs.org nuget.org oracle.com packagecloud.io packages.microsoft.com packagist.org pkg.go.dev ppa.launchpad.net pub.dev pypa.io pypi.org pypi.python.org pythonhosted.org quay.io ruby-lang.org rubyforge.org rubygems.org rubyonrails.org rustup.rs rvm.io sourceforge.net spring.io swift.org ubuntu.com visualstudio.com yarnpkg.com
All domains – unrestricted internet access.

Add your own domains

Use Additional domains to add domains that are required for your project but are not included in the preset list.

Enter one domain per line. You can specify exact domains such as example.com and wildcard domains such as *.example.com.

Run commands before the agent session

To run commands before the agent session starts, add the file .air/cloud/startup.sh under the repository root. JetBrains Air runs this script in the cloud environment before the agent starts working on the task.

Use this script for one-time environment setup, for example, to install tools, prepare configuration files, or initialize project-specific resources. For example:

        
            #!/bin/sh
            apt-get update
            apt-get install -y jq
            mkdir -p ~/.config/my-tool
            echo "startup complete"
                    
        

When it runs – only the first time the cloud environment is created. It does not run again when the environment is resumed or when the agent is restarted in the same environment.
Repository state – the repository is already checked out when the script runs.
Working directory – the script starts in the project root.
User – the script runs as the environment user with sudo rights.
Access to environment variables – the script has access to everything that is already present in the environment, including configured secrets and environment variables.
Shell process – the script runs in a separate process. If you use export inside the script, the exported variables are not preserved for the agent session.
Failure behavior – if the script exits with an error, the session is marked as failed. This behavior may change in the future.
Timeout – there is currently no dedicated timeout for the startup script. If it hangs, the environment can remain stuck until the cloud environment itself times out.
Logs – startup script logs are currently part of the workspace logs. In case of failure, the script output becomes part of the error message.

21 May 2026