GitHub Copilot is now selectable in JetBrains Air for local and cloud tasks on Copilot plans; Air Neither shows Copilot usage nor caps spending. GitHub and JetBrains say Copilot can run in Air locally or in cloud sandboxes billed to Copilot plans, but Air does not track Copilot credits, show its usage or set spending limits. Verified pipeline | Sources: 4 | Publisher: signed | Contributor: signed | Hash: 72b2974e7a | View Editor's note · november 6, 2026. * Clarification: - The "What We Don't Know" section says that "both vendors direct users to GitHub for usage." Only JetBrains does so (its FAQ says "Check your usage on GitHub"); the GitHub changelog does not direct users to check usage on GitHub. Overview. GitHub says developers can now use GitHub Copilot inside JetBrains Air. According to the GitHub changelog, "you can now delegate coding tasks, guide execution, and review results with GitHub Copilot in JetBrains Air," using the Agent Client Protocol (ACP) for tasks "in your JetBrains IDE or in the cloud." JetBrains published a companion post, Use Your GitHub Copilot Plan in JetBrains Air, saying the tasks run on an existing Copilot plan "not on JetBrains AI credits." Both posts also list limits on what Air can see and control about Copilot usage. What The Machine Herald Know. Local and cloud tasks. GitHub's changelog lists three additions: a GitHub Copilot entry in Air's agent picker that uses an existing Copilot subscription; parallel sessions with in-context review; and cloud tasks that run "through Air Teams, from your IDE or browser." JetBrains says Air runs the official GitHub Copilot CLI over ACP, and that Copilot appears in the same task list as Claude, Codex and Junie. Local use does not need Air Teams, but a Copilot subscription is required. For cloud tasks, GitHub lists three requirements: a JetBrains account in an Air Teams-enabled business organization, a GitHub Copilot subscription, and Copilot enabled by the Air administrator. JetBrains adds that cloud agents work from a remote branch, so changes must be pushed first, and that Air uses the GitHub connection under Settings | VCS Providers to sign in to Copilot when a task starts. Where cloud tasks run. The GitHub changelog says that when a Copilot cloud task runs through Air, "Copilot works in a Docker container on a fresh virtual machine. All traffic passes through a proxy, and no state carries over between tasks." JetBrains' separate post on cloud agent sandboxing in Air describes the design: each task starts a VM that is "not reused between tasks," with the agent in a Docker container behind a proxy. By default the proxy allows connections only to a preset list of trusted source control and package registry domains, such as npm; JetBrains says users can add domains, allow all domains, or turn internet access off. The same post says microVMs are "coming soon" and that cloud agents are currently available to organizational users, with a broader release for individual users planned later. Automations. JetBrains says Air Automations can start cloud tasks on a schedule or when something happens in a repository, such as a new pull request, and that with Copilot selected, "each run uses your Copilot plan." The post recommends a weekly dependency update as a first automation and warns that one reviewing every pull request "can drain your credits much faster, especially if the repository is busy." Usage and spending visibility. Both vendors state limits on usage tracking. Under "Cloud task considerations," GitHub says Air's governance and analytics features do not include Copilot usage, that Air administrators can disable Copilot through a governance policy but cannot set Copilot spending limits within Air, and that users cannot choose per task between a personal and an organization Copilot plan. It also says Air may only verify subscription or credit availability when the cloud environment starts, and that the task fails with an error in the session if they are unavailable. JetBrains makes the same point in its FAQ: "Air doesn't track Copilot credits for local or cloud tasks, and it can't set a spending limit." It adds that Air "doesn't warn you when your credits are all used up" and that runs will "just start failing," so usage has to be checked on GitHub. Background. Air launched in public preview in March. The Register reported on March 10 that Air supported OpenAI Codex, Anthropic Claude Agent, Google Gemini CLI and JetBrains Junie, and that it could use ACP, which Zed and JetBrains sponsor. The outlet also described tasks that could run in a local workspace, a Git worktree, Docker or, in a future release, a cloud container. The Herald has previously reported on JetBrains opening early access for Air inside its IDEs, and, in an Analysis, on sandboxes and permission modes versus repository-borne attacks. What The Machine Herald Don't Know. * None of the cited sources gives a Copilot pricing or credit-consumption figure for Air tasks; both vendors direct users to GitHub for usage. * The Register's report predates the Copilot integration and does not address it, and the other three cited sources are from GitHub or JetBrains, so the claims about the integration rest on the vendors' own descriptions. * Neither vendor says whether Air will add Copilot usage to its governance and analytics features or add Copilot spending limits.

DataGrip 2026.3: agentic development with jetbrains Air, cross-database queries, DuckDB support, and major UX improvements. November 5, 2026 DataGrip 2026.3, the third major update of the year, is here! Let's take a look at what's inside. AI. JetBrains Air is now available by default in DataGrip. You can run SQL, explore data, and reference database objects directly in chats with AI agents. SQL snippets use your IDE's syntax highlighting and formatting settings. You can run them against a selected data source using the Run Query button right in the chat. After execution, you can navigate to object definitions and preview them in the Quick Definition popup. You can view CSV format data in the chat's data editor with sorting and search options. To reference database objects in your prompts, use @dbObject notation with completion to help you find the object you need. Object references in the chat also support Quick Definition. UI and UX improvements. First, JetBrains has moved query results from Services to a new Database Output tool window. It opens automatically at the bottom of the IDE when you run a query, a run configuration, or an SQL file. By default, its contents follow the active editor tab. The header combines the client selector with the Output, Query Plan, and Result tabs. The session client tree is now in a dropdown on the right side of the toolbar, while session management remains in the Services tool window. Second, JetBrains has updated the tool window bar in the window header and the default tool window shortcuts. The bar now shows icons for Database Explorer, Database Output, Files, and Agent Sessions by default. For the default tool window shortcuts, Agent Sessions now uses Cmd+2 (macOS) / Alt+2 (Windows/Linux), previously assigned to Files. Files now uses Cmd+4 (macOS) / Alt+4 (Windows/Linux), previously assigned to Run. Run no longer has a default shortcut. Connectivity. You can now query data across different data sources, even when they use different DBMSs, and view the results directly without copying the data beforehand. To make this possible, JetBrains has introduced a new Workspace data source, based on DuckDB. In its query consoles, you can use a special syntax to reference and join tables from other data sources, filter them, and also run queries against those data sources. DuckDB now gets full support, including a dedicated SQL dialect, DuckDB-specific syntax and functions, code completion, and database object introspection. Three connection types are available: default, In-memory, and URL only. The default option connects to a DuckDB database file at the specified path. In-memory creates a database in memory, while URL only uses the JDBC URL you provide as is. The way DataGrip handles untrusted projects has also been updated. Connecting to a database can execute potentially malicious code, for example, when the connection URL, startup scripts, or driver files have been tampered with. That's why DataGrip now asks you to trust an untrusted project before connecting to a database. You can also stay in safe mode, where database connections are disabled. Working with data. Let's take a look at what's new in the data editor. JetBrains has added two buttons to the query results toolbar: Open in Editor Tab and SQL. Open in Editor Tab opens a result set in a separate tab in the main editor area. The action is available for results in the Database Output tool window and for in-editor results. SQL opens a popup with the result set's original query. From there, you can run the query again, copy it to the clipboard, or navigate to it in the editor. Column management also gets a few enhancements. You can now pin columns to the left side of the data editor to keep them visible as you scroll horizontally. You can pin a single column, several selected columns, or all columns up to a selected one. You can now automatically resize columns to fit the available width of the data editor. This makes it easier to view tables with many columns without adjusting each column individually. JetBrains has replaced the Show Column List popup with the new Manage Columns popup. It lets you find columns, select which ones to display, pin or unpin them, and adjust their order in one place. You can also navigate to a column in the grid. Changes to column order and pinning are immediately reflected in the grid. To open the popup, click Manage Columns on the data editor toolbar or press Cmd+F12 (macOS) / Ctrl+F12 (Windows/Linux). Alternatively, right-click a column header and select Manage Columns. An indicator on the toolbar icon shows when some columns are hidden. Query consoles. JetBrains has improved transaction control in query consoles. In Manual mode, running COMMIT or ROLLBACK now disables the Commit and Rollback toolbar buttons in PostgreSQL, Greenplum, MySQL, MariaDB, and Oracle. Consoles that share a session also display the same transaction state. JetBrains has fixed PostgreSQL transaction and savepoint issues and disabled automatic savepoints by default for databases outside the PostgreSQL family. Database support. JetBrains has added support for MariaDB sequences and initial support for packages. DataGrip displays them in dedicated sequences and packages groups under the schema node in Database Explorer. DataGrip now introspects packages and their bodies and loads their source code. You can generate their DDL, drop them, and refresh individual packages. JetBrains has also improved support for package syntax in the code editor. DataGrip now supports PostgreSQL 19. DataGrip now recognizes INSERT... ON CONFLICT DO SELECT... RETURNING, WAIT FOR LSN, and the EXCEPT clause in CREATE PUBLICATION statements. JetBrains has updated the minicatalogs to include new PostgreSQL 19 functions, too. If you're interested in upgrading to DataGrip 2026.3, or if you have any questions or suggestions, here are a few links you might find useful: * Download DataGrip 2026.3. * Visit its What's New page for the full list of improvements. * Contact JetBrains on X. * Report any bugs to its issue tracker The DataGrip team

JetBrains partners with Logicom to expand software development portfolio across the GCC. Distribution agreement brings more than 30 JetBrains products to regional customers and partners, supporting the shift towards AI-assisted and agentic software development. JetBrains is expanding its regional distribution strategy through a new partnership with Logicom, aiming to widen access to its software development tools across the Gulf Cooperation Council (GCC) countries and the broader Middle East. Announced on October 28, 2026, the agreement combines JetBrains' portfolio of more than 30 software development products with Logicom's regional distribution network, technical resources and partner ecosystem. The collaboration will provide sales support, partner training and joint customer engagement initiatives to help organisations adopt development tools and workflows shaped by artificial intelligence. The partnership comes as software development moves beyond conventional coding assistance towards agentic systems capable of carrying out multiple tasks across the development lifecycle. For enterprises, this transition creates opportunities to accelerate delivery, but also raises questions about code quality, oversight and accountability. JetBrains is positioning its JetBrains Air system as part of this evolution. Designed to support AI agents across individual developers, teams and organisations, Air aims to provide greater visibility, verification and governance as agentic development becomes more prevalent. The broader JetBrains portfolio includes IntelliJ IDEA, PyCharm, YouTrack, Qodana and TeamCity, alongside Kotlin, the company's cross-platform programming language. "As AI reshapes software development, we are committed to enabling our partners to capture this growth through innovative solutions and technical expertise." - Adamos Christodoulou, Group Sales, Marketing and Services Director, Logicom Nadia Rinsky, Head of Business Development for MENA at JetBrains, said the agreement would make its tools and expertise more accessible to organisations across the GCC. She highlighted local technical guidance, training and ongoing partner support as important elements of the collaboration. For Logicom, the agreement strengthens its software portfolio and creates opportunities to help channel partners respond to demand for AI-enabled development solutions. Adamos Christodoulou, Group Sales, Marketing and Services Director at Logicom, said the distributor would focus on combining innovative solutions with technical expertise and stronger customer engagement. The arrangement reflects a broader shift in enterprise technology distribution, where access to software increasingly needs to be accompanied by implementation guidance, technical enablement and support for emerging use cases. JetBrains and Logicom plan to meet customers and partners at GITEX Global in Dubai in December 2026 to discuss the portfolio and software development requirements. With the partnership, both companies are seeking to strengthen their regional reach as organisations evaluate how AI-assisted and agentic tools can be incorporated into development operations while maintaining control over software quality and processes.