Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Local: install Air in a JetBrains IDE, select GitHub Copilot, and connect your existing Copilot account.
- Browser-based cloud tasks require an Air Teams business organization, a JetBrains account, a Copilot subscription, and administrator enablement. Connect GitHub under Settings > VCS Providers, then choose a repository, branch, and Copilot.
- For cloud tasks in the IDE, select Cloud in the Air plugin's environment selector. The sources describe current cloud access for organizational users; a broader release for individuals is only planned.
- Copilot cloud tasks use the Copilot plan rather than JetBrains AI credits. General Air cloud subscription requirements still need to be checked for the selected workflow.
- A connected account can still fail a subscription or credit check when the cloud environment starts. Per-task billing selection, Air usage analytics and spending caps have specific limits.
Separate local use from cloud eligibility
GitHub announced Copilot in JetBrains Air on November 3, 2026, with support for local and cloud coding tasks using an existing Copilot subscription. The integration uses Agent Client Protocol (ACP), a protocol for connecting development tools with agents. Start by choosing where the task will run, then check the account and billing conditions for that path.
The local workflow is for developers using Air in a JetBrains IDE. The cloud workflow is described for users in Air Teams-enabled business organizations. JetBrains' cloud-sandbox article says a broader release for individuals is planned; it does not confirm that every personal JetBrains account already has cloud access. The sources do not list exact account, regional, or subscription eligibility.
Use your existing Copilot subscription locally
Open a JetBrains IDE, install the Air plugin, and open the Air workspace. Select GitHub Copilot from the agent picker. If prompted, connect your existing GitHub Copilot account, then send a task prompt and review the result. The announcement says this local path uses your existing Copilot subscription.
Air's native Copilot agent and the GitHub Copilot IDE plugin are separate workflows that can coexist; Air's native agent does not require a separate Copilot plugin installation. Keep the plugin if you also want its other IDE integrations. The announcement does not name eligible Copilot tiers, permission requirements, supported countries, or prices, so check the current GitHub account and organization settings.
Start a cloud task from the browser or IDE
The browser flow requires a JetBrains account in an Air Teams-enabled business organization, a GitHub Copilot subscription, and Copilot enabled by the Air administrator. Open Air in the browser, connect GitHub under Settings > VCS Providers, then create a task by choosing a repository and remote branch, selecting GitHub Copilot, and sending your prompt.
In the IDE, select Cloud in the Air plugin's environment selector. The task runs remotely; GitHub says it starts in a Docker container on a fresh virtual machine, with no task environment state carried over from a previous task. Seeing Cloud in the selector does not grant access by itself: the organization and administrator requirements still apply.
Check Copilot billing separately from JetBrains AI rules
GitHub's November 3 announcement says cloud tasks using Copilot through Air use your GitHub Copilot plan rather than JetBrains AI credits. However, the JetBrains IDE EAP FAQ still associates general Air cloud tasks with a JetBrains AI subscription. The statements may cover different agents or task scopes; the available material does not reconcile them.
Apply the Copilot announcement only to the Copilot cloud path it describes. It does not establish that every Air cloud task no longer requires JetBrains AI, or that there are no additional charges. Before starting, check the current rules for your account, selected agent, and organization with your administrator. These sources do not specify eligible plan names, prices, quotas, country or region support, or how a cloud task is assigned to a personal versus organization bill.
Keep four cloud governance limits in view
First, Air may check Copilot subscription or credit availability only when the cloud environment starts; if the check fails, the session reports an error. Second, you cannot choose whether an individual task uses your personal or organization Copilot plan, so the task picker does not determine billing ownership.
Third, Air governance analytics do not include Copilot usage, so an Air report alone cannot reconcile Copilot consumption. Fourth, Air administrators can disable Copilot through a governance policy, but cannot set a Copilot spending limit inside Air. The sources do not describe the billing and limit controls of the Copilot plan itself; check the relevant GitHub account or organization settings.
Understand the private-code, network, and secret boundaries
A cloud Copilot task runs in a Docker container inside a JetBrains-managed remote virtual machine. Traffic passes through a proxy, and tasks do not share state between runs. JetBrains says the default proxy allows a preset list of trusted source-control and package-registry domains; an organization admin can narrow or add domains, allow all domains, or turn internet access off. The boundary depends on organization settings; do not assume the proxy bypasses network policy.
Tasks use the developer’s existing repository permissions and cannot access repositories that developer could not already view. Repository permissions do not establish the model provider’s retention terms. Before starting a cloud task, confirm that your organization permits the repository in that remote workflow.
Air stores secrets encrypted and exposes them to a task as environment variables. Encryption at rest does not prevent running code or tools from reading a value once it has been injected. Add only narrowly scoped secrets that the task needs, and check your organization's network and secret rules. Fresh virtual machines and no state carryover do not replace reviewing code access, permissions, or the resulting changes.
Sources
Frequently Asked Questions
My account connected, but a cloud task reports unavailable subscription or credits. Should I reinstall the Copilot plugin?
Read the session’s exact error and check the Copilot subscription, available credits and Air organization requirements first. A successful connection does not establish that the cloud-start check has passed. Reinstalling a plugin for a different workflow does not establish that those conditions have recovered.
If Copilot usage is missing from Air reports, can I treat it as no consumption?
No. GitHub says Air governance and analytics do not include Copilot usage. A missing row is not evidence of zero consumption. Check available records for the GitHub account or organization actually used; keep usage and cost unknown when matching data is unavailable.
Can I choose a country or a fixed residential IP for the cloud proxy?
These sources do not describe the proxy’s egress region, IP type or user-selected exit capability. Do not infer those properties. The proxy defines network access for cloud tasks and does not change account, regional or subscription eligibility.