Local and cloud work have different requirements
GitHub Copilot, a coding assistant, now works in JetBrains Air, which organizes AI coding tasks. Local work uses an existing Copilot subscription. [1]
Cloud tasks require a JetBrains account in an Air Teams-enabled business organization, a Copilot subscription, and administrator enablement. Usage comes from Copilot allowances, not JetBrains AI credits. [1]
You cannot select a personal or organization plan per task. Air excludes Copilot usage from analytics and cannot cap its spending. Subscription or credit availability may be checked only at cloud startup. [1]
JetBrains describes a fresh remote workspace for each cloud task, separate from your computer. Network connections pass through a proxy, a service that controls where traffic goes. This describes isolation, not a guarantee of safety. [2]
Our take
For a minor website edit, ask the helper to improve one paragraph on a contact page. Use project files your organization permits you to share. Review the proposed changes and run your team’s usual checks before accepting them.
Before delegating deadline work, ask the administrator which Copilot plan will apply and how its usage will be watched. Work done through Air draws on that plan’s allowance, so it can leave less for other Copilot work. Agree on who will check it before relying on a cloud task for a delivery date.