Loading post…
JetbrainsVladimir GromozdinAnnouncement
Air Teams: Bring Your Best Agentic Workflows to the Whole Team – and Automate Repeatable Work
Summary
JetBrains introduced Air Teams, a shared workspace for agentic development that extends beyond individual developers to teams and organizations. The system comprises four components: Automations for recurring tasks triggered by events or schedules, shared cloud environments with preconfigured tools and credentials, cloud tasks that run in parallel without tying up local machines, and team projects that centralize members, environments, and credits. Automations include templates for code review, bug fixes, and dependency updates, and they run under a project’s service account so they persist after a creator leaves. Shared environments are defined in a repository’s .air/cloud/startup.sh script and can be snapshotted for reuse, with secrets shared without exposing values. Air Teams is available to business customers, with plans to expand to individual customers later.
Context
JetBrains observed that while individual developers gained productivity with AI agents, the bottleneck shifted to team-level coordination, prompting the creation of Air Teams to provide shared context, environments, and automations across the development lifecycle.
Approach / What changed
Air Teams provides four components: Automations for event- or schedule-triggered recurring tasks (e.g., code review, bug fixes, dependency updates); shared cloud environments with preconfigured tools, dependencies, and credentials defined in a repository script; cloud tasks that run in parallel on remote machines without tying up local resources; and team projects that centralize members, environments, connectors, and credits with role-based access.
Takeaways
Automations run under a project’s service account and can persist after the creator leaves, using project credits or the creator’s own credits.
Shared environments are defined in a .air/cloud/startup.sh script in the repository, version-controlled, and can be snapshotted for reuse; secrets are shared without exposing values.
Cloud tasks can be started from an IDE and followed up on the web or mobile, and they continue running even after the user’s laptop is closed.
FAQ
How do Automations handle recurring tasks?
Automations are triggered by events (e.g., GitHub pull request, Jira label) or schedules. They run in a shared cloud environment with predefined instructions, tools, and triggers. The agent performs the task and opens a pull request for review, and the team decides whether to merge.
How are credentials managed in shared environments?
Shared secrets let teammates and Automations use a value without seeing it, while personal secrets and repository access stay with each person. The environment setup is version-controlled in the repository.
What happens to Automations when a creator leaves the team?
Automations run under the project's service account and can use project credits. They continue running after the creator leaves, as long as the project admin has configured them to use project credits.
Source and freshness
- Source
- blog.jetbrains.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.