JetBrains Air Teams: Automations, shared cloud environments, and team projects

JetBrains’ Air blog on September 28, 2026 introduces JetBrains Air Teams—the team layer for agentic development, giving humans and agents shared context, environments, tools, and instructions across the development lifecycle (blog, Vladimir Gromozdin).

What Air Teams is

Air Teams has four parts, as JetBrains names them:

• Automations — agentic workflows that run in the cloud on an event or a schedule, for recurring work such as reviews, issue fixes, and dependency updates; they are shared team assets
• Shared cloud environments — tools, dependencies, and credentials the team sets up once and reuses
• Cloud tasks — work that runs in those environments, in parallel, without tying up a laptop
• Projects — shared home for members, environments, connectors, and Automations, with shared credits and roles

This is the team and organization layer—not the earlier Air in JetBrains IDEs early-access story of embedding Air inside the IDE as a multi-agent conduit.

Automations

An Automation is instructions, an environment, tools (connectors such as Jira, Figma, and Linear), and a trigger (GitHub or Jira event, webhook, or schedule). JetBrains says Air Teams ships with 10 Automation templates, including code review, bug fixes, dependency upgrades, and documentation maintenance—use one as-is or adapt it.

Control stays with people: every code change arrives as a pull request, and an engineer decides whether to merge it. Runs keep the agent’s conversation and tool calls for review when a result looks wrong.

Shared environments, cloud tasks, and projects

Shared cloud environments live per repository in a team project. Teams pick VM size, domain allowlist, and variables or secrets; setup lives in the repo at .air/cloud/startup.sh. Air can save a ready environment as a snapshot. Shared secrets let teammates and Automations use a value without seeing it, as JetBrains states.

Cloud tasks can run local or in the cloud. Cloud runs are not tied to the starting device—you can start and follow them from Air in JetBrains IDEs or on the web; JetBrains says phone/mobile follow-up is coming soon, not available yet.

Team projects bring members, environments, connectors, and Automations together. Admins manage membership and setup; members use shared environments and create Automations. Project credits and a project service account can keep Automations running even after the creator leaves, as JetBrains describes.

Availability

Air Teams is already available to JetBrains business customers, with plans to expand access to individual customers later. JetBrains does not name seat SKUs or dollar pricing in this post. Try it at air.jetbrains.cloud.

Who should care

Engineering teams on JetBrains commercial plans who want shared agentic workflows—not one-off laptop prompts—should start at the Air Teams announcement. Treat the ten templates and mobile “soon” as vendor-stated; confirm business eligibility with JetBrains before planning an org rollout.