DataGrip Releases

• Disabling 'Show the Welcome screen in non-modal mode' has no effect in DataGrip.

• Switching to Database Explorer by Cmd+1/Alt+1 doesn't focus on the Tree.
• The Search path drop-down doesn't expand.
• Quick Documentation shows nothing for built-in SQL functions.

• Added support for authentication and authorization with OIDC/OAuth 2.0 for MongoDB.

• Query Console
  • Backspace stops working in MongoDB JS console after typing '${'.
• Quick Documentation
  • Quick Documentation shows nothing for built-in SQL functions.

AI

• AI agent skills for working with databases - DataGrip 2026.2 introduces three agent skills for working with databases: database-connection-management, database-text-to-sql, and database-tools. Skills define reusable procedures for AI agents. They provide step-by-step instructions for completing complex tasks using existing DataGrip features, including MCP tools. Following these instructions helps agents generate higher-quality results with lower token usage.
• Data source management with MCP tools - JetBrains have expanded the list of MCP tools that help AI agents work with databases. This release adds two new tools to the list: create_database_connection and edit_database_connection. The database-connection-management skill includes instructions that help agents use these tools correctly. To have an agent create a new data source, ask it to do so and provide the connection details. The agent will create the data source and run a test connection.
• Other improvements
  • AI in DataGrip now remembers query results from previous interactions, allowing you to fetch additional rows without rerunning the query. This also works for statements that return data with RETURNING.
  • When an AI agent creates a table, a column, or any other database object, DataGrip automatically introspects the database or schema you're working with. The newly created object will appear in the database explorer right away.
  • Previously, when an AI agent couldn't find a referenced database object, it couldn't tell whether the object didn't exist or simply hadn't been introspected. Now, the agent can identify missing objects, suggest similarly named objects in case of typos, and recognize objects that haven't been introspected.
  • Queries run by AI agents are now also tracked and logged in the data source query history. To check them, open the data source's query console by pressing Shift+Ctrl+F10 and selecting any query console. In the query console tab, click Browse Query History.
  • Previously, AI agents received a generic Not done error when an SQL query failed. Now, the agent receives an actual database message with an SQL error.
  • The list_database_connections MCP tool now returns database connection information correctly. Previously, incorrect handling of parameters with default values caused an output schema error.
  • The database schema attachment UI in the AI chat has been redesigned.
  • Database-specific MCP tools no longer require the AI Assistant plugin.

A smoother start

• Non-modal Welcome screen - The Welcome screen, which appears when you start DataGrip for the first time or after you close all projects, is now non-modal. It appears as a regular IDE tab instead of a modal dialog, so you can continue working in the IDE while using it. This new Welcome to DataGrip tab opens in the automatically created default project. It provides quick actions and useful links to help you get more familiar with the IDE and configure it to suit your needs.
• Interactive onboarding tour - JetBrains have introduced an interactive onboarding tour that guides you through DataGrip's core features. It covers basics such as key actions in the Database Explorer tool window, the data source settings dialog, query execution in a query console, viewing and working with query result sets, and submitting changes to a database.

Command-line interface

• CLI commands for data sources - Power users often need to automate environment setups. To support this, JetBrains have introduced a command-line interface that lets you programmatically manage your database connections and drivers.

Connectivity

• Two-session mode - Before this release, session control was handled through the IDE's default behavior, with the optional Single shared session mode. By default, each new client, such as a query console or data editor, created a separate connection to the database. If Single shared session mode was enabled, DataGrip used one shared connection whenever you worked with a data source. Single shared session mode supports scenarios where you want to share one connection across multiple clients. However, it can be inconvenient because the same session is also used for database introspection - the process of retrieving metadata. DataGrip 2026.2 introduces the new Two sessions: shared and introspection mode, which creates two sessions: one for introspection and one for everything else. This new mode keeps metadata retrieval separate from your working session. If introspection takes longer, query consoles, data editors, and other clients continue using the shared session instead of waiting for it to finish.
• Bundled JDBC drivers - Previously, DataGrip didn't include any JDBC drivers. Each driver you wanted to use had to be downloaded separately when creating a data source. Now, the following JDBC drivers are bundled in DataGrip:
  • Microsoft SQL Server 13.2.1.
  • MongoDB 1.21.
  • MySQL Connector/J 9.5.0.
  • PostgreSQL 42.7.3.
  • Redis 1.6.
• Role and warehouse switcher Snowflake - Switching between database roles and warehouses is now much faster. If you work with Snowflake, you no longer need to manually execute SET ROLE commands or search through connection settings to change your permissions for the current session. A new drop-down menu in the query console toolbar lets you switch between available roles and warehouses instantly.

Working with data

• SQL expressions in the data editor - You can now set cell values using SQL expressions instead of being limited to literal values. Previously, when editing data in the grid, you could only enter static values or use the context menu to set a cell to NULL or its DEFAULT value. If you wanted to use a database function like NOW() or gen_random_uuid(), or perform a calculation, you had to manually write and execute an UPDATE statement in the console. This update introduces the new SQL Expression mode in the data editor. When editing a cell, you can now right-click it and choose Edit as SQL Expression, or enable SQL Expression mode using the fx button in the value editor.

Database explorer

• Redesigned empty state in the database explorer - The Database Explorer tool window now features a redesigned empty state that offers quick actions for creating data sources in a new project. It also provides PostgreSQL, MySQL, and SQLite demo databases used in the quick start guide, so you can connect to them and get familiar with basic DataGrip features.
• Database colors: v2.0 - Database colors now have a fresh, consistent UI, and custom colors work differently. Previously, the fixed #RRGGBB hex code looked the same across all IDE themes, so it usually looked right in either the light or the dark theme, but not both. Now, you can simply set the hue, and the system handles the shades automatically.
• Schema object grouping by prefix - The database explorer now allows grouping schema objects by prefix in the tree. The following characters are treated as prefix delimiters: _, -, and $. For example, my_table01 and my_table02 are grouped under my_, and their names are displayed as table01 and table02 within the group.
• Deletion of folders and their contents - Previously, you were unable to delete non-empty folders. Now, you can delete folders that contain other folders or data sources. Before deleting a folder, DataGrip will ask for confirmation and display the list of items to be deleted.

Explain Plan menu and actions

• Return of the Explain Plan raw format actions - In the previous release, JetBrains simplified the Explain Plan drop-down by removing the Explain Plan (Raw) and Explain Analyse (Raw) actions. This affected workflows that regularly require these actions. In this release, JetBrains have addressed your feedback by bringing back these actions and making them accessible from the toolbar. There's now a Raw button on the left-hand toolbar of the Query Plan tab. For the plan tree, the button opens the raw execution plan in the Raw inner tab. The plan tree also remains available in the Operation Tree inner tab.

Query files and consoles

• Custom query console names in editor tab headers - Different workflows and tasks require different information to be available at a glance. This is why JetBrains have added the ability to customize how query console names are displayed in editor tab headers - the first place you look when identifying an open file. Previously, only the data source name was displayed next to the file name. Now, you can use variables to add more details, such as the attached data source, database, schema, or search path.

Code editor

• Execution time display near queries - Previously, you could find timestamps for a query execution only in the Services tool window. Now, once DataGrip has executed a query, it shows the query execution time next to the query in the code editor.
• Improved support for ClickHouse and Snowflake SQL - Expanded ClickHouse SQL support with the following additions:
  • Query parameter syntax.
  • Additional SYSTEM statements.
  • The FIRST clause in ALTER TABLE ADD COLUMN statements.
• Other enhancements include:
  • Improved support for ORDER BY... WITH FILL STEP.
  • Fixes for false syntax errors related to projection indexes.
• For Snowflake, JetBrains have added support for:
  • Flow operations.
  • DATABASE ROLE syntax.
  • HASH functions, including HASH(*).
  • INTERSECT, UNION BY NAME, and DISTINCT in SELECT statements.
  • Object, session, and user parameters in ALTER USER statements.

• AI Assistant
• Added the ability to extract DB consent classes from 'llm.sql' module to a separate module.
• Added the ability extract business logic from MCP modules into dbe/database.

• AI Assistant
  • MCP: AI agent receives generic 'not done' error instead of actual SQL error message.
• Data Editor/Viewer
  • Clear icon no longer refreshes table after clearing WHERE or ORDER BY fields.
• Database Explorer
  • Custom data source color not applied to sessions in Services tool window.
• Query Console
  • Can't execute statement in PyCharm dbt project.

• Data Editor/Viewer
  • Added the ability to show arrays in grid editor.
• General
  • Added support for procedure parameter directions.

• Code Generation
  • Checkbox is absent in the Truncate prompt.
• Code Highlighting
  • Fixed issue with SHOW BUILTIN / USER PROCEDURES syntax.
  • Snowflake: Directory Tables are not supported.
  • Revise FILE FORMAT syntax.
  • Snowflake: Datagrip does not support 'create temp' syntax.
  • Fixed issue with syntax for (temp|temporary) (procedure|function).
  • Fixed issue with ALTER COLUMN ... IF NOT EXISTS.
  • Fixed issue with multiple DROP COLUMNs in Snowflake.
  • Fixed issue with MERGE with ALL BY NAME in Snowflake.
  • Snowflake procedures: language clause is optional.
  • Fixed issue with CREATE OR ALTER syntax.
• Database Explorer
  • Data source custom colors are rendered incorrectly (desaturated, shifted hue).
• Introspection
  • Fragment introspection for routine dropping introspection level of unmodified routine.
• Query Console
  • MongoDB console executes only the first query in multi-operation scripts.
• SQL Resolve
  • Fixed issue with highlighting for DUAL table in Snowflake.
  • Sub-partition references are red.

• Connectivity
  • Added usage statistics for the 'Comment' field in Data Sources and Drivers.
  • Improved UI/UX of the 'Comment' field in Data Sources & Drivers.

• AI Assistant
  • AI Assistant fails to attach Schema with "Schema is too large".
  • 'test_database_connection' doesn't show original connection error message.
  • Removed redundant 'Use this tool to' prefix from MCP tool descriptions.
• Code Generation
  • Dump button in SQL Generator doesn't work in 2026.1.
• Code Highlighting
  • 'ClassCastException' for shared function objects in console.
• Introspection
  • CockroachDB backward incompatible change.
  • Schemas are deselected when adding a new one.
• Query Console
  • SQL Execution with CTRL + ENTER Changes sqldialects.xml.
  • The hash symbol in the one-line comment is displayed in the result tab name.
  • Incomplete text for Chinese in error toolbar.
  • IDE freezes while executing multiple UPDATE statements.
  • The 'Treat text as title after' setting is confusing.
  • Execution status icon disappears for DDL statements in Single session mode.
  • Gutter icons are not removed if request is slowly removed symbol-by-symbol.
  • Name action groups which are lacking naming in the settings.

• Added support DATABASE ROLE syntax in Snowflake.
• Moved color settings to the large settings dialog.

• Code Highlighting
  • Fixed issue with 'create task' syntax.
  • Snowflake: problem with 'RETURNS TABLE' syntax when creating procedures.
  • False-positive 'Cursor might not have been open' warning for cursors with parameters.
• DDL Data Source
  • Only the first file listed in sources for DDL data source is used for resolve / completion in sql files (even if listed in resolution scope).
• Schema Diff
  • Dump to DDL data source ignores IF NOT EXISTS setting for indexes.

AI improvements: Agentic flow

• File creation with the SQL dialect and data source attached - When chatting with AI Assistant in the AI Chat tool window, you can create a file from a code snippet.
• If any context relating to the SQL dialect, a data source, or a schema is provided in the chat, you don't have to attach the data source or schema or set the dialect because DataGrip will do this automatically. The same goes for questions you ask AI Assistant about a file that already has a data source attached: DataGrip will attach that data source to the newly created file.
• Integration of AI agent into the AI chat - Claude Agent and Codex are now natively integrated in the AI chat interface. This makes it easier to get the right kind of assistance for every task. Currently, Codex integration requires configuring the MCP server manually.
• Database-specific capabilities of the MCP server - Extended the MCP server with database-specific functionalities. With this enhancement, built-in AI agents and third-party tools can work with databases in a more structured way. The new capabilities include:
  • Obtain connection configurations and test them.
  • List database schemas.
  • Retrieve supported schema object types (such as tables and views) and browse schema objects.
  • View recent and currently running SQL queries.
  • Execute and cancel running SQL queries.
  • Preview table data and get result sets in CSV format.
• For security, four types of user consent are required by default:
  • Schema access requests.
  • Data access requests.
  • Schema modification requests.
  • Data modification requests.

Query files and consoles

• New flow for creating a query file - Redesigned the flow for working with query files side by side with query consoles. You can now use either just files or just consoles, or both at the same time, depending on your tasks and workflow.
• Query Files folder in the database explorer - You can now access your query files in the database explorer. Added a Query Files folder, which appears under each data source node. To toggle this folder's visibility, click View Options on the tool window toolbar, and then select or deselect the Query Files option.
• New options for tailoring how files are displayed - Different tasks require different information to be visible. Added some settings to ensure that the presentation of query files gives you the right info for your specific use case. You can use these settings to toggle whether data source names are displayed, apply schema colors, and use the icon of the attached data source with your query files.

Connectivity

• Data source templates - Implemented a way to store data source settings as a template in your JetBrains Account. When stored this way, the template is available in every JetBrains IDE with database functionality provided through your JetBrains Account. These templates store settings from the General and Advanced tabs of the Data Source and Drivers dialog, but exclude your database credentials.
• PostgreSQL 18 support - DataGrip now supports PostgreSQL 18, which was released last year. Full support includes the following keywords and commands, among others:
  • OLD and NEW resolution in RETURNING clauses.
  • WITHOUT OVERLAPS in primary and unique constraints.
  • PERIOD in foreign key constraints.
  • GENERATED ALWAYS AS (...) [STORED | VIRTUAL] for columns.
  • NOT ENFORCED and NOT VALID constraints.
• Data Sources and Drivers dialog improvements:
  • The Data Sources, Clouds, Drivers, and DDL Mappings sections are now the main tabs in the dialog, located on the left-hand side.
  • If the Comment field is empty, it is hidden by default. To display it, click Add Comment next to the Name field.
  • If the driver selected in the Driver dropdown menu has yet to be downloaded, a Download option appears next to the menu. Click this to download the driver.
  • The Connection type dropdown options are now tabs. If a data source has more than three connection types, they are displayed as a dropdown.
  • In addition, the Create DDL Mapping action has been removed. You can create a DDL mapping on the DDL Mappings main tab.

Explain Plan workflow

• UI and UX improvements - Updates to the Explain Plan workflow to make it more discoverable, informative, and easy to use:
  • The list of options in the Explain Plan dropdown on the code editor toolbar has been shortened to just two: Explain Plan and Explain Analyse.
  • In the Services tool window, the Query Plan tab that displays the plan has been moved to the same level as the Output and Result tabs. It also has a new icon.
  • In the Query Plan tab, you can now view the details of each plan row in a separate panel on the right-hand side of the tab.
  • For the cells that contain a table name, quick documentation is available in a popup when you hover the cursor over the table.
  • The different views available for a query plan are displayed in separate sub-tabs. These inner tabs can be seen at the bottom of the Query Plan tab. They are hidden by default and appear only when more than one tab is open. To open the Total Cost or Startup Cost tab, click Flame Graph on the left-hand toolbar and select the view you need.
• Option to copy a query plan in its native format - You can now copy a query plan in the database's native format, for example, JSON or XML. To do this, click the Copy Original Query Plan button at the top of the left toolbar. This is supported for PostgreSQL, Amazon Redshift, MySQL, MariaDB, Oracle, Microsoft SQL Server, and Snowflake.

Code editor

• Intention action for suppressing the resolve inspection for back label references (Oracle) - Made the Suppress for back label references option easier to find and use. Previously, it was only available in the Settings dialog under Editor | Inspections | SQL. Now, it can be toggled in intention actions. To enable or disable it, open the list of intention actions by pressing Alt+Enter (Windows/Linux) or Option+Enter (macOS), navigate to Enable option "Suppress for back label references", and select or deselect the Suppress for back label references checkbox.
• Execute Selection as Single Statement action in the context menu - Added the Execute Selection as Single Statement action to the context menu of a code selection. Use this when you need to execute a certain chunk of code and DataGrip isn't parsing it properly.
• Editor caret movement animation - The code editor caret has received two new options for the movement animation to improve your typing experience. Animation preferences vary quite a lot. With this in mind, JetBrains carefully developed their own mode of caret movement: Snappy. It ensures smooth animation without making the caret feel slow and unresponsive or overloading the interface with excessive action. In this mode, the caret initially jumps quickly to its new position, but then slows down a bit and "settles into" position. The result feels quick yet smooth. In the other caret animation mode, Gliding, the caret moves smoothly, making jumps easy to follow with your eyes. This mode is similar to the ones you see in other popular text editors.

Working with data

• Support for JSON indexes Microsoft SQL Server - DataGrip now supports creating and modifying JSON indexes for Microsoft SQL Server. You can work with them in code generation and also use the indexes in the Create and Modify dialogs.
• Show Geo Viewer button on the toolbar - Moved the Show Geo Viewer button to the data editor toolbar.

Working with files

• Deleted files go to the bin by default - Previously, when Delete actions were invoked, DataGrip deleted files permanently instead of moving them to the bin. Added a setting that sends files to the bin instead. It's called Move files to the bin instead of deleting permanently, and it is enabled by default.

• Code Highlighting
  • Current statement highlighting does not work for files outside the project.
• Data Editor/Viewer
  • Services window: 'Delete' key prompts to close session instead of deleting table row.
• Data Import/Export
  • Copy To Clipboard does not work.
  • Export data does not work.
• Query Console
  • DataGrip cannot execute MongoDB .js query scripts.
  • Do not store query consoles in data source per files mappings.

• Added an option to hide query files node in DB Explorer.

• Data Editor/Viewer
  • Option to display geo-type in raw binary.
• Database Explorer
  • Some actions on DataSource are disabled or don't work when there is no model.
  • Virtual views folder is not shown under a data source node.
• Query Console
  • Cannot open the console when a data source has no model.
  • Color of file in File Explorer depends on availability of connection.

• Code Formatter
  • Postgres: Formatter attempts to quote operators like ||.
• Data Import/Export
  • Data extractors always use CSV and ignore other formats when copying via clipboard.
• Query Console
  • Attach data source doesn't work for multiple SQL files.
• Usability
  • Parameter dialog: input focus jumps to next field while typing.