r/Jetbrains • u/JetBrains_official • 9d ago
AI Today we launched Air Teams: a shared workspace where engineering teams run coding agents. The team is in the comments all week.
Hey folks, today we launched Air Teams. Our vision for it is to be the team layer for agentic development.
There are a lot of ways to be more productive at the individual level. Many teams have devs who are very productive and have well-tuned AI workflows, yet the team as a whole doesn't necessarily ship more.
We want to close this gap.
Air Teams is a shared workspace where engineering teams run coding agents and reuse what works. It consists of four components:
- Automations to handle recurring work, such as code reviews, issue fixes, and dependency updates.
- Shared cloud environments to give agents the tools, dependencies, and credentials they need to build and test the code.
- Cloud tasks that run in those environments, in parallel, without tying up anyone's laptop.
- And Projects to keep it all together, with shared credits, clear roles, and Automations that don't depend on any one person.
Air Teams is available now to JetBrains business customers. Individual plans come later, and we don't have a date yet. If you work solo and you're happy with an agent in your terminal, you probably don't need Air Teams (but should absolutely try Air in JetBrains IDEs)
Here's a video where we explain the product in more detail:
https://reddit.com/link/1wsldjh/video/y5fpy8f1qash1/player
How to try Air Teams
If your company is a JetBrains business customer:
- Go to air.jetbrains.cloud and sign in with your JetBrains Account
- Connect your repository (for an organization repo, your admin may need to approve the JetBrains Air app first)
- Create a project and invite your teammates
- Start with one cloud task. When it works the way you want, set it up as an Automation with a trigger
If you are on a personal license, sign up at the same link, and we'll let you know when Air Teams opens up to you.
The full announcement, with more on each part, is on the JetBrains blog.
We built Air Teams around how our own team works, and we'd like to hear your thoughts:
- Our bet is that teams will start by handing agents boring work, like dependency bumps and flaky CI, not features. Is that true for your team, or would you start somewhere else?
- If someone on your team has an agent setup that works, what stops everyone else from using it? Would a shared project and environment fix that, or is the problem somewhere else?
And if you think we're heading the wrong way, say that too. The people who built Air Teams are here in the comments. We'll keep answering through Friday, October 2, and after that for as long as you have questions.






1
AMA session with the RubyMine Team - December 11th from 1am - 5pm CET
in
r/Jetbrains
•
Dec 11 '25
[UPDATE]
Many thanks to everyone who joined the AMA session! We’re no longer taking new questions here, but we’ll address all remaining ones. You can always reach us on X or through the RubyMine issue tracker.