CLI Our power users often need to automate environment setups. To address that, we've introduced a command line interface that allows you to programmatically manage your database connections and drivers. The syntax is: datagrip dataSources [options] [arguments] Available commands: list, manage. The new CLI uses a batch-processing approach. Instead of running one command per action, you can pass a JSON file containing multiple instructions. The tool processes them in a single session and returns the results in JSON, making it perfect for shell pipelines. The full documentation for this feature can be found here.

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. This means it appears as a regular IDE tab instead of a modal dialog, so you can continue working with the IDE while using it. This new Welcome to DataGrip tab opens in the automatically created DataGripWorkspace project. It provides quick actions and useful links to help you get more familiar with the IDE and configure it to suit your needs.

Redesigned empty state in the database explorer This update also includes a redesigned empty state in our database explorer, which offers quick actions for creating data sources in a new project. It also provides PostgreSQL, MySQL, and SQLite demo databases used in our Quick start guide that you can connect to and use to get familiar with basic DataGrip features.

Interactive onboarding tour We're introducing an interactive onboarding tour that guides you through DataGrip's core features. It covers such basics as key actions in the database explorer, the data source settings dialog, query execution in a query console, viewing and working with query result sets, and submitting changes to a database. For demonstration purposes, the tour includes a preset H2 playground data source and a short SQL script that runs against the playground database during one of the steps. To take the tour, go to Help | Learn IDE Features in the main menu.

Custom query console names in editor tab headers Different workflows and tasks require different information to be available at a glance. This is why we've 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. The customization settings are located in Settings | Database | Query Files and Consoles. 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. To use a variable, place the caret where you want to insert it in the Template field and click the corresponding variable button. If you'd like to use this template for query files, too, select Use this template for query files.

Known issues:

• DBE-25800 Dump button in SQL Generator doesn't work
• DBE-26207 One-row data extractor fails with MissingPropertyException
• DBE-26075 No output shown for Script text execution in Run Configurations