# Run/debug configurations

> For the complete documentation index, see [llms.txt](https://www.jetbrains.com.cn/en-us/help/go/llms.txt).

> **TL;DR**
> Configure: `Run | Edit Configurations`

GoLand uses run/debug configurations to run, debug,  and test your code. Each configuration is a named set of startup properties that define what to execute and what parameters and environment should be used.

There are two types of run/debug configurations:

* Temporary — created when you run or debug main functions or tests when no matching permanent configuration exists.

* Permanent — created explicitly from a template or by saving a temporary configuration. Permanent configurations remain as part of your project until you remove them.

Whenever you run, debug, or test your code, GoLand either uses an existing permanent run/debug configuration or creates a new temporary one.

Permanent configurations have opaque icons while the icons of temporary configurations are semi-transparent. The red cross over the configuration icon indicates an error in configuration settings.

The maximum number of temporary configurations is 5. The older ones are automatically deleted when new ones are added. If necessary, you can increase this limit in `Settings | Advanced Settings | Run/Debug | Temporary configurations limit` .

## Create temporary run/debug configurations

To create a temporary run/debug configuration, you can run your code from the gutter or from the context menu.

Procedure: Run from the editor

If you are not going to pass any parameters to your program, and your program does not require any specific actions to be performed before start, you can run it right from the editor.

* Click ![](https://resources.jetbrains.com.cn/help/img/idea/2026.3/app.actions.execute.svg) in the [gutter](guided-tour-around-the-user-interface.html) near the  `main` function and select Run.

[Video](https://resources.jetbrains.com.cn/help/img/idea/2026.3/go_run_code_from_gutter.mp4)

* To run a script, open it in the editor or select it in the Project tool window, and then select Run <script file name> from the context menu.

[Video](https://resources.jetbrains.com.cn/help/img/idea/2026.3/go_run_from_the_context_menu.mp4)

## Create permanent run/debug configurations

GoLand provides the following ways to create a permanent run/debug configuration:

* [Save a temporary run/debug configuration as permanent](#save-as-permanent).

* [Create from a template](#createExplicitly) or copy an existing configuration.

Procedure: Save a temporary configuration as permanent

* Select a temporary configuration in the run/debug configuration switcher, click ![](https://resources.jetbrains.com.cn/help/img/idea/2026.3/app-client.actions.more.svg) / ![](https://resources.jetbrains.com.cn/help/img/idea/2026.3/app-client.general.chevron-right.svg) and select Save Configuration.

* Alternatively, select a temporary configuration in the Run/debug configurations dialog and click ![Save](https://resources.jetbrains.com.cn/help/img/idea/2026.3/app-client.expui.general.save.svg) on the toolbar.

GoLand provides run/debug configuration [templates](#templates) for different languages, tools, and frameworks. The list of available templates varies depending on the installed and enabled [plugins](managing-plugins.html).

Procedure: Create a run/debug configuration from a template

1. Go to `Run | Edit Configurations`. Alternatively, press `Alt+Shift+F10` (Windows), `⌃ ⌥ R` (macOS), `⌥ ⇧ F10` (IntelliJ IDEA Classic (macOS)), `⌃ ⌥ R` (macOS System Shortcuts), `Alt+Shift+F10` (XWin), `Alt+Shift+F10` (GNOME), `Alt+Shift+F10` (KDE), `Alt+Shift+F10` (Emacs), `Alt+Shift+F10` (Sublime Text), `⌃ ⌥ R` (Sublime Text (macOS)), `Ctrl+;, A` (VSCode), `⌘ ;, A` (VSCode (macOS)), then `0` (Windows), `0` (macOS), `0` (IntelliJ IDEA Classic (macOS)), `0` (macOS System Shortcuts), `0` (XWin), `0` (GNOME), `0` (KDE), `0` (Emacs), `0` (Sublime Text), `0` (Sublime Text (macOS)), `0` (VSCode), `0` (VSCode (macOS)).

2. In the Run/Debug Configurations dialog, click ![](https://resources.jetbrains.com.cn/help/img/idea/2026.3/app.expui.general.add.svg) on the toolbar or press `Alt+Insert` (Windows), `⌘ N` (macOS), `⌃ N` (IntelliJ IDEA Classic (macOS)), `⌘ N` (macOS System Shortcuts), `Alt+Insert` (XWin), `Alt+Insert` (GNOME), `Alt+Insert` (KDE), `Alt+Insert` (Emacs), `Ctrl+N` (Sublime Text), `⌘ N` (Sublime Text (macOS)), `Alt+Insert` (VSCode), `⌃ ⏎` (VSCode (macOS)). The list shows the run/debug configuration templates.   Select Go Build.

3. Specify the run/debug configuration name in the Name field. This name will be used to identify the run/debug configuration in lists and menus.

4. On the Configuration tab, you can set the following options:

5. In the Before launch section, define whether you want to perform any specific actions before launching the application, for example,  launch an [external tool](configuring-third-party-tools.html)  or another run/debug configuration before run.

6. You can either run the configuration right away or save the configuration to run it later.

* To save the run configuration for later, click OK.

* To run the configuration right away, click Run.

### List of fields in Go Build configuration

| Name | Description |
| --- | --- |
|  Run kind  |    Building scope for your application.  File  and  Package  scopes work similarly in tests and compilation/running configurations (in terms of the scope they cover).        * Directory : build an application in the specified directory as a package, without processing any subdirectories. For test configurations, GoLand runs all the tests in the specified directory and all its subdirectories.    * File : build an application from files specified in the Files field. To pass multiple file paths, use the vertical bar (`\|`) as a delimiter. This configuration is automatically selected when you run your program from scratch files.    * Package : build a single package with all its dependencies. Specify a full import path to the package that you want to build in the Package path field (for example, `github.com/gorilla/mux`). This configuration is automatically selected when you run the `main` function by using the Run Application icon (![the Run button](https://resources.jetbrains.com.cn/help/img/idea/2026.3/app.actions.execute.svg)) in the gutter.    |
|  Package path  |    Full import path of the package that you want to compile (for example, `myServerApp`). This field is available only when you select the  Package  run kind.      You can press `Ctrl+Space` (Windows), `⌃ Space` (macOS), `⌃ Space` (IntelliJ IDEA Classic (macOS)), `⌃ Space` (macOS System Shortcuts), `Ctrl+Space` (XWin), `Ctrl+Space` (GNOME), `Ctrl+Space` (KDE), `Alt+/` (Emacs), `Ctrl+Space` (Sublime Text), `⌃ Space` (Sublime Text (macOS)), `Ctrl+I` (VSCode), `⌘ I` (VSCode (macOS)) to see a list of available packages.     |
|  Output directory  | Path to a directory where you want to output the executable file. |
| Build on remote target |    This checkbox appears when you select a non-local run target. It is cleared by default.     Select it to copy the source files to the target and build there. When you select it, GoLand hides the Output directory field.     Clear it to build locally and copy the executable to the target.     If the selected Go SDK is located in WSL, GoLand builds on the run target even when this checkbox is cleared. For more information, refer to [Run on a target](run-targets.html#run).    |
|  Run after build  | Execute the application after the build. |
|  Emulate terminal in output console  |    Executes the application and displays the output in the Run tool window as it would appear in the terminal.    |
|  Redirect input from  |    File to read the input from.    |
|  Working directory  | Directory that is used for the built application. If you have any code that creates relative files or directories, they will be relative to this directory.  |
|  Environment  |    Environment variables for your application.      To edit environment variables, click the Browse button at the end of the field. In the Environment Variables dialog, click the Add button and add the environment variables that you need.     |
|  Go tool arguments  | Arguments for the go tool (for example, `-o`). Also, you can use [macros](built-in-macros.html) in this field.  |
|  Use all custom build tags  |    Select this checkbox to add the tags from the Custom tags field under `Go \| Build Tags` to the build command.     If Go tool arguments already contains `-tags`, the command uses those tags instead.     |
|  Program arguments  | Arguments for the built application. Also, you can use [macros](built-in-macros.html) in this field. |
|  Run with sudo  | Run the application with elevated privileges. |
|  Module  | Name of the current module. |
|  Before launch  | Add tasks that you want to launch before the launch of the selected run/debug configuration. To add a task click the  Add  button `Alt+Insert` (Windows), `⌘ N` (macOS), `⌃ N` (IntelliJ IDEA Classic (macOS)), `⌘ N` (macOS System Shortcuts), `Alt+Insert` (XWin), `Alt+Insert` (GNOME), `Alt+Insert` (KDE), `Alt+Insert` (Emacs), `Ctrl+N` (Sublime Text), `⌘ N` (Sublime Text (macOS)), `Alt+Insert` (VSCode), `⌃ ⏎` (VSCode (macOS)) and select the tool that you want to add.  |
|  Store as project file  |     Enable this option to save your configuration as a project file and share it with team members through [VCS](version-control-integration.html).     |

### List of fields in Go Test configurations

| Name | Description |
| --- | --- |
| Test framework | Select the test framework to use.       * gotest: run standard Go tests. For more information about `go test`, refer to [Package testing](https://pkg.go.dev/testing).    * gocheck: run tests with the gocheck framework.    * gobench: run benchmarks. For more information, refer to [Package testing: Benchmarks](https://pkg.go.dev/testing#hdr-Benchmarks).    * go test -fuzz: run fuzz tests. Fuzzing sends random or unexpected input to your code to find problems. For more information, refer to [Go Fuzzing](https://go.dev/security/fuzz/). Use Run to start fuzzing. The Debug action is unavailable for the go test -fuzz framework.     |
| Test kind | Select the scope from which you want to run tests:       * Directory: run tests in the selected directory and its subdirectories. Specify the directory in the Directory field. To debug tests, select Package instead.    * Package: run tests in a package. In the Package path field, enter the package import path, for example, `example.com/myapp/calc`.    * File: run tests from the selected files. In the Files field, enter file paths separated by `\|`, for example, `/work/myapp/calc.go\|/work/myapp/calc_test.go`. Select files from the same directory. At least one file needs to support the selected test framework.    |
|   Pattern   | This field is available for Directory and Package scopes. For File scope, GoLand generates the pattern from the test functions in the selected files when no pattern is set.     Enter a regular expression to select the tests to run. For tests with subtests, separate the expressions with `/`. The first expression matches the test name, and each following expression matches a subtest name at the next level.     For example, to run the `add_positive_and_negative` subtest of `TestAdd`, enter `^\QTestAdd\E$/^\Qadd_positive_and_negative\E$`.     > **Tip:** > To generate the pattern, [run a subtest](performing-tests.html#run-individual-table-tests) or [a set of tests](performing-tests.html#run-tests) from the gutter. You can then edit the pattern in the generated configuration.    |
|   Working directory   | Directory that is used for the built application. If you have any code that creates relative files or directories, they will be relative to this directory.  |
|   Output directory   | Directory for the compiled test executable when you use File or Package scope. |
| Build on remote target |    This checkbox appears when you select a non-local run target. It is cleared by default.     Select it to copy the source files to the target and build there. When you select it, GoLand hides the Output directory field.     Clear it to build locally and copy the executable to the target.     If the selected Go SDK is located in WSL, GoLand builds on the run target even when this checkbox is cleared. For more information, refer to [Run on a target](run-targets.html#run).    |
|   Redirect input from   | Path to the file to use as standard input instead of the console.  |
|   Environment   |    : environment variables that you need to run the test.      To edit environment variables, click the Browse button at the end of the field. In the Environment Variables dialog, click the Add button and add the environment variables that you need.     |
|   Go tool arguments   | Arguments for the go tool (for example, `-tags`).  |
|   Use all custom build tags   |    Select this checkbox to add the tags from the Custom tags field under `Go \| Build Tags` to the build command.     If Go tool arguments already contains `-tags`, the command uses those tags instead.      If neither Go tool arguments nor this checkbox supplies `-tags`, GoLand can select tags from `//go:build` and `// +build` constraints in the test files. This applies to File scope and to Package scope when GoLand can identify the selected test functions.    |
|   Program arguments   | Arguments for the test. |
|   Run with sudo   | Run the tests with elevated privileges. This option is available for local configurations when the operating system supports process elevation. |
|  Before launch: Activate tool window  | Add tasks that you want to launch before the launch of the selected run/debug configuration. To add a task, click the  Add  button `Alt+Insert` (Windows), `⌘ N` (macOS), `⌃ N` (IntelliJ IDEA Classic (macOS)), `⌘ N` (macOS System Shortcuts), `Alt+Insert` (XWin), `Alt+Insert` (GNOME), `Alt+Insert` (KDE), `Alt+Insert` (Emacs), `Ctrl+N` (Sublime Text), `⌘ N` (Sublime Text (macOS)), `Alt+Insert` (VSCode), `⌃ ⏎` (VSCode (macOS)) and select the tool that you want to add.  |

### Before launch

In this area, you can specify tasks to be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.

| Item | Shortcut | Description |
| --- | --- | --- |
| ![the Add button](https://resources.jetbrains.com.cn/help/img/idea/2026.3/app.expui.general.add.svg) | `Alt+Insert` (Windows), `⌘ N` (macOS), `⌃ N` (IntelliJ IDEA Classic (macOS)), `⌘ N` (macOS System Shortcuts), `Alt+Insert` (XWin), `Alt+Insert` (GNOME), `Alt+Insert` (KDE), `Alt+Insert` (Emacs), `Ctrl+N` (Sublime Text), `⌘ N` (Sublime Text (macOS)), `Alt+Insert` (VSCode), `⌃ ⏎` (VSCode (macOS)) |    Click this icon to add one of the following available tasks:        * Launch Web Browser: select this option to have a browser started. In the dialog that opens, select the type of the browser and provide the start URL. Also, specify if you want the browser to be launched with the JavaScript debugger.    * Run External tool: select to run an external application. In the dialog that opens, select one or multiple applications you want to run. If it is not defined in GoLand yet, add its definition.    * Run Another Configuration: select to execute another run/debug configuration and wait until it finishes before starting the current configuration. If you want to run several configurations in parallel, use a [compound run/debug configuration](run-debug-multiple.html#compound-configs) .    * Run File Watchers: select this option to have GoLand apply all the currently active [File Watchers](using-file-watchers.html).    * Run Remote External Tool: adds a remote SSH external tool.    * Run Grunt task: select this option to run a Grunt task. In the Grunt task dialog that opens, specify the `Gruntfile.js` where the required task is defined, select the task to execute, and specify the arguments to pass to the Grunt tool. Specify the location of the Node.js runtime, the parameters to pass to it, and the path to the grunt-cli package.    * Run gulp task: select this option to run a Gulp task. In the Gulp task dialog that opens, specify the `Gulpfile.js` where the required task is defined, select the task to execute, and specify the arguments to pass to the Gulp tool. Specify the location of the Node.js runtime, the parameters to pass to it, and the path to the gulp package.    * Run npm script: select this option to execute an npm script. In the NPM Script dialog that opens, specify the [npm run/debug configuration settings](null).    * Compile TypeScript: select to run the built-in TypeScript compiler and thus make sure that all the changes you made to your TypeScript code are reflected in the generated JavaScript files. In the TypeScript Compile Settings dialog that opens, select or clear the Check errors checkbox to configure the behaviour of the compiler in case any errors are detected: * If the Check errors checkbox is selected, the compiler will show all the errors and the run configuration will not start. * If the Check errors checkbox is cleared, the compiler will show all the detected errors but the run configuration still will be launched.    * Run Go Command: select to run a Go command before running your program. For example, you can run `go generate` to generate source code before compilation. In the Edit Go Command Task dialog, you can use auto-completion. Auto-completion supports the following commands `generate`, `vet`, `test -i`. You can use your own commands.    * Disconnect Data Source: select this option if you want to disrupt the connection to a data source before the run/debug configuration is run.     |
| ![the Remove button](https://resources.jetbrains.com.cn/help/img/idea/2026.3/app.expui.general.remove.svg) | `Alt+Delete` (Windows), `⌘ ⌦` (macOS), `⌘ ⌦` (IntelliJ IDEA Classic (macOS)), `⌘ ⌦` (macOS System Shortcuts), `Alt+Delete` (XWin), `Alt+Delete` (GNOME), `Alt+Delete` (KDE), `Alt+Delete` (Emacs), `Alt+Delete` (Sublime Text), `⌘ ⌦` (Sublime Text (macOS)), `Alt+Delete` (VSCode), `Alt+Delete` (VSCode (macOS)) |  Click this icon to remove the selected task from the list.  |
|  ![Edit](https://resources.jetbrains.com.cn/help/img/idea/2026.3/app.expui.general.edit.svg)  |  `Enter` (Windows), `⏎` (macOS), `⏎` (IntelliJ IDEA Classic (macOS)), `⏎` (macOS System Shortcuts), `Enter` (XWin), `Enter` (GNOME), `Enter` (KDE), `Enter` (Emacs), `Enter` (Sublime Text), `⏎` (Sublime Text (macOS)), `Enter` (VSCode), `⏎` (VSCode (macOS))  | Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.  |
|     ![Method up](https://resources.jetbrains.com.cn/help/img/idea/2026.3/app.expui.general.moveUp.svg)       ![Method down](https://resources.jetbrains.com.cn/help/img/idea/2026.3/app.expui.general.moveDown.svg)     |     `Alt+Up` (Windows), `⌃ ⇧ ↑` (macOS), `⌃ ↑` (IntelliJ IDEA Classic (macOS)), `⌃ ⌥ ↑` (macOS System Shortcuts), `Alt+Up` (XWin), `Alt+Up` (GNOME), `Alt+Up` (KDE), `Alt+Up` (Emacs), `Alt+Up` (Sublime Text), `Alt+Up` (Sublime Text (macOS)), `Alt+Up` (VSCode), `Alt+Up` (VSCode (macOS))       `Alt+Down` (Windows), `⌃ ⇧ ↓` (macOS), `⌃ ↓` (IntelliJ IDEA Classic (macOS)), `⌃ ⌥ ↓` (macOS System Shortcuts), `Alt+Down` (XWin), `Alt+Down` (GNOME), `Alt+Down` (KDE), `Alt+Down` (Emacs), `Alt+Down` (Sublime Text), `Alt+Down` (Sublime Text (macOS)), `Alt+Down` (VSCode), `Alt+Down` (VSCode (macOS))     | Click these icons to move the selected task one line up or down in the list. The tasks are performed in the order that they appear in the list.  |
| Show this page |  | Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.  |
| Activate tool window |  |      By default this checkbox is selected and the [Run](run-tool-window.html) or the [Debug](debug-tool-window.html) tool window opens when you start the run/debug configuration.       Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing `Alt+4` (Windows), `⌘ 4` (macOS), `⌘ 4` (IntelliJ IDEA Classic (macOS)), `⌘ 4` (macOS System Shortcuts), `Alt+4` (XWin), `Alt+4` (GNOME), `Alt+4` (KDE), `Alt+4` (Emacs), `Alt+4` (Sublime Text), `⌘ 4` (Sublime Text (macOS)), `Ctrl+Shift+U` (VSCode), `⌘ ⇧ U` (VSCode (macOS)) or `Alt+5` (Windows), `⌘ 5` (macOS), `⌘ 5` (IntelliJ IDEA Classic (macOS)), `⌘ 5` (macOS System Shortcuts), `Alt+5` (XWin), `Alt+5` (GNOME), `Alt+5` (KDE), `Alt+5` (Emacs), `Alt+5` (Sublime Text), `⌘ 5` (Sublime Text (macOS)), `Ctrl+Shift+Y` (VSCode), `⌘ ⇧ D` (VSCode (macOS)).       |
| Focus tool window |  |     Select this checkbox to automatically move focus to the [Run](run-tool-window.html) or the [Debug](debug-tool-window.html) tool window when you start the run/debug configuration.     |

## Launch a run configuration

Procedure:

You can launch existing run configurations in one of the following ways:

* If the run configuration is already selected in the [Run widget](guided-tour-around-the-user-interface.html#toolbar) , click ![](https://resources.jetbrains.com.cn/help/img/idea/2026.3/app.expui.run.run.svg) next to it or press `Shift+F10` (Windows), `⌃ R` (macOS), `⇧ F10` (IntelliJ IDEA Classic (macOS)), `⌥ ⇧ R` (macOS System Shortcuts), `Shift+F10` (XWin), `Shift+F10` (GNOME), `Shift+F10` (KDE), `Shift+F10` (Emacs), `Shift+F10` (Sublime Text), `Shift+F10` (Sublime Text (macOS)), `Ctrl+F5` (VSCode), `⌃ F5` (VSCode (macOS)).

* If you want to select another run configuration, click the [Run widget](guided-tour-around-the-user-interface.html#toolbar) . In the menu that opens, click ![](https://resources.jetbrains.com.cn/help/img/idea/2026.3/app.expui.run.run.svg) next to the run configuration you want to launch.

* Press `Alt+Shift+F10` (Windows), `⌃ ⌥ R` (macOS), `⌥ ⇧ F10` (IntelliJ IDEA Classic (macOS)), `⌃ ⌥ R` (macOS System Shortcuts), `Alt+Shift+F10` (XWin), `Alt+Shift+F10` (GNOME), `Alt+Shift+F10` (KDE), `Alt+Shift+F10` (Emacs), `Alt+Shift+F10` (Sublime Text), `⌃ ⌥ R` (Sublime Text (macOS)), `Ctrl+;, A` (VSCode), `⌘ ;, A` (VSCode (macOS)). In the menu that opens, click the run configuration you want to launch.

## Share run/debug configurations

You might want to share your run/debug configurations so that your teammates could run the application using the same configuration or enable them to remotely attach to the process you are running.

GoLand provides a mechanism to store your run/debug configurations as project files and share them through VCS. The same mechanism can also be used when you want to send your configuration as a file to someone else, create a local backup of your run/debug configurations, or import them from a file.

Procedure:

1. Go to `Run | Edit Configurations`. Alternatively, press `Alt+Shift+F10` (Windows), `⌃ ⌥ R` (macOS), `⌥ ⇧ F10` (IntelliJ IDEA Classic (macOS)), `⌃ ⌥ R` (macOS System Shortcuts), `Alt+Shift+F10` (XWin), `Alt+Shift+F10` (GNOME), `Alt+Shift+F10` (KDE), `Alt+Shift+F10` (Emacs), `Alt+Shift+F10` (Sublime Text), `⌃ ⌥ R` (Sublime Text (macOS)), `Ctrl+;, A` (VSCode), `⌘ ;, A` (VSCode (macOS)), then `0` (Windows), `0` (macOS), `0` (IntelliJ IDEA Classic (macOS)), `0` (macOS System Shortcuts), `0` (XWin), `0` (GNOME), `0` (KDE), `0` (Emacs), `0` (Sublime Text), `0` (Sublime Text (macOS)), `0` (VSCode), `0` (VSCode (macOS)).

2. Select the run/debug configuration you want to share, enable the Store as project file option, and specify the location where the configuration file will be stored.

You can configure any location unless compatibility with GoLand 2019.3 and earlier is required. For compatibility with these versions, store the file in the suggested location.

3. (Optional) If the `.idea` directory is added to VCS ignored files, the `.idea/runConfigurations` subfolder will be ignored, too. If the project uses Git, you can share `.idea/runConfigurations` and leave `.idea` ignored by modifying `.gitignore` as follows:

```
/.idea/*
!/.idea/runConfigurations
```

> **Note:**
> Turning on the  Store as project file  option does not submit anything to the VCS. For run/debug configurations to make their way to a shared repository, you have to check them in like the other versioned files.

## Run/debug configuration templates

All run/debug configurations are based on templates, which implement the startup logic, define the list of parameters and their default values. The [list of available templates](list-of-run-debug-configurations.html) is predefined in the installation and can only be extended via [plugins](managing-plugins.html). However, you can edit default parameter values in each template to facilitate the setup of new run/debug configurations.

Procedure: Configure the default values for a template

1. Go to `Run | Edit Configurations`. Alternatively, press `Alt+Shift+F10` (Windows), `⌃ ⌥ R` (macOS), `⌥ ⇧ F10` (IntelliJ IDEA Classic (macOS)), `⌃ ⌥ R` (macOS System Shortcuts), `Alt+Shift+F10` (XWin), `Alt+Shift+F10` (GNOME), `Alt+Shift+F10` (KDE), `Alt+Shift+F10` (Emacs), `Alt+Shift+F10` (Sublime Text), `⌃ ⌥ R` (Sublime Text (macOS)), `Ctrl+;, A` (VSCode), `⌘ ;, A` (VSCode (macOS)), then `0` (Windows), `0` (macOS), `0` (IntelliJ IDEA Classic (macOS)), `0` (macOS System Shortcuts), `0` (XWin), `0` (GNOME), `0` (KDE), `0` (Emacs), `0` (Sublime Text), `0` (Sublime Text (macOS)), `0` (VSCode), `0` (VSCode (macOS)).

2. In the left-hand pane of the run/debug configuration dialog, click Edit configuration templates….

3. In the  Run/Debug Configuration Templates  dialog that opens, select a configuration type.

4. Specify the desired default parameters and click OK to save the template.

## Run/debug configuration folders

When there are many run/debug configurations of the same type, you can group them in folders for easier access.

Procedure: Create a folder for run/debug configurations

1. Go to `Run | Edit Configurations`. Alternatively, press `Alt+Shift+F10` (Windows), `⌃ ⌥ R` (macOS), `⌥ ⇧ F10` (IntelliJ IDEA Classic (macOS)), `⌃ ⌥ R` (macOS System Shortcuts), `Alt+Shift+F10` (XWin), `Alt+Shift+F10` (GNOME), `Alt+Shift+F10` (KDE), `Alt+Shift+F10` (Emacs), `Alt+Shift+F10` (Sublime Text), `⌃ ⌥ R` (Sublime Text (macOS)), `Ctrl+;, A` (VSCode), `⌘ ;, A` (VSCode (macOS)), then `0` (Windows), `0` (macOS), `0` (IntelliJ IDEA Classic (macOS)), `0` (macOS System Shortcuts), `0` (XWin), `0` (GNOME), `0` (KDE), `0` (Emacs), `0` (Sublime Text), `0` (Sublime Text (macOS)), `0` (VSCode), `0` (VSCode (macOS)).

2. In the Run/Debug Configurations dialog, select a configuration type and click ![the New Folder icon](https://resources.jetbrains.com.cn/help/img/idea/2026.3/app.expui.actions.newFolder.svg) on the toolbar. A new empty folder for the selected type is created.

3. Specify the folder name in the text field to the right or accept the default name.

4. Select the desired run/debug configurations and move them under the target folder.

5. Apply the changes. If a folder is empty, it will not be saved.

When you no longer need a folder, you can delete it `Delete` (Windows), `⌦` (macOS), `⌦` (IntelliJ IDEA Classic (macOS)), `⌦` (macOS System Shortcuts), `Delete` (XWin), `Delete` (GNOME), `Delete` (KDE), `Delete` (Emacs), `Delete` (Sublime Text), `⌦` (Sublime Text (macOS)), `Delete` (VSCode), `⌦` (VSCode (macOS)). The run/debug configurations grouped under this folder will be moved under the root of the corresponding run/debug configuration type.

