With the Go Build configuration, you can run, compile, and debug Go applications. For more information about creating a run/debug configuration from a template, see Create a run/debug configuration from a template.
Select a building scope for your application. File and Package scopes work similarly in tests and compilation/running configurations (in terms of the scope they cover).
Type or autocomplete a full import path of the package that you want to compile (for example,
You can press Ctrl+Space to see a list of available packages.
Type a path to the directory of your Go application that you want to compile (for example,
Type a path to a file or files of your Go application that you want to compile (for example,
Type a path to a directory where you want to output the executable file.
Run after build
Execute the application after the build.
Redirect input from
Specify a file to read the input from.
Type a 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.
Specify 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
Type arguments for the go tool (for example,
Use all custom build tags
Specify all tags that are applied during the build. Tags are listed in settings Ctrl+Alt+S under.
Type arguments for the built application. Also, you can use macros in this field.
Run with sudo
Run the application with elevated privileges.
Name of the current module.
When you edit a run configuration (but not a run configuration template), you can specify the following options:
Specify a name for the run configuration to quickly identify it among others when editing or running.
Allow multiple instances
Allow running multiple instances of this run configuration in parallel.
By default, it is disabled, and when you start this configuration while another instance is still running, GoLand suggests stopping the running instance and starting another one. This is helpful when a run configuration consumes a lot of resources and there is no good reason to run multiple instances.
Store as project file
Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations. However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project.
By default, it is disabled, and GoLand stores run configuration settings in .idea/workspace.xml.
The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates.
Create a run/debug configuration.
Delete the selected run/debug configuration. Note that you cannot delete default configurations.
Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.
The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent.
Move into new folder / Create new folder. You can group run/debug configurations by placing them into folders.
To create a folder, select the configurations within a category, click , and specify the folder name. If only a category is in focus, an empty folder is created.
Then, to move a configuration into a folder, between the folders or out of a folder, use drag or and buttons.
To remove grouping, select a folder and click .
Click this button to sort configurations in the alphabetical order.
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.
Click this icon to add one of the following available tasks:
Click this icon to remove the selected task from the list.
Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
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 or the Debug 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 or Alt+5.