# External Tools

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

> **TL;DR**
> `File | Settings | Tools | External Tools` for Windows and Linux
>
>
>
> `GoLand | Settings | Tools | External Tools` for macOS
>
>
>
> `Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `Ctrl+Comma` (VSCode), `⌘ Comma` (VSCode (macOS)) ![the Settings icon](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.settings.svg)

This page describes the settings that you can configure for local external tools. For more information about adding and using external tools, refer to [External tools](configuring-third-party-tools.html).

![The External Tools settings page](https://resources.jetbrains.com/help/img/idea/2026.3/settings_tools_external_tools.png)

Use the toolbar buttons to manage the list of available external tools. Clear checkboxes for tools that you want to keep but not show in menus.

![the Add button](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.add.svg) Add `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))
: Add a new external tool.

![the Remove button](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.remove.svg) Remove `Ctrl+Y` (Windows), `⌘ ⌫` (macOS), `⌘ Y` (IntelliJ IDEA Classic (macOS)), `⌘ ⌫` (macOS System Shortcuts), `Ctrl+Y` (XWin), `Ctrl+Y` (GNOME), `Ctrl+Y` (KDE), `Ctrl+Y` (Emacs), `Ctrl+Shift+K` (Sublime Text), `⌃ ⇧ K` (Sublime Text (macOS)), `Ctrl+Shift+K` (VSCode), `⌘ ⇧ K` (VSCode (macOS))
: Remove the selected tool or group.

![the Edit button](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.edit.svg) Edit `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))
: Edit the selected tool.

![](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.up.svg) Up `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), `⌥ ↑` (Sublime Text (macOS)), `Alt+Up` (VSCode), `Alt+Up` (VSCode (macOS))
: Move the selected tool up in the list.

![](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.down.svg) Down `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), `⌥ ↑` (Sublime Text (macOS)), `Alt+Up` (VSCode), `Alt+Up` (VSCode (macOS))
: Move the selected tool down in the list.

![](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.copy.svg) Copy
: Move the selected tool down in the list.

When you create, edit, or copy an external tool, you need to provide the tool's settings.

![Creating, editing, or copying an external tool](https://resources.jetbrains.com/help/img/idea/2026.3/settings_tools_external_tools_dialog.png)

Name
: The name of the tool that will be used as the action for running the tool in the GoLand interface.

Group
: The name of the group to which the tool belongs.

Description
: A meaningful description of the tool.

## Tool Settings

> **Warning:**
> Make sure that you specify the absolute paths for the tool's settings, not paths relative to the project.

Program
: The absolute path to the executable file (script, utility, application, and so on).

Arguments
: The arguments passed to the executable file, as you would specify them on the command line.
:
:
:
:
:
: * Use spaces to separate individual arguments.
:
: * Use double quotes for arguments and paths that contain spaces.
:
: * Use a backslash to escape double quotes that are part of the argument or path.
:
:
:
:
:
: For example:
:
:
:
:
:
:
: ```PLAINTEXT
: -Dmy.prop=\"quoted_value\" "second arg" third" "arg
: ```

Working directory
: The absolute path to the working directory from which the tool should be executed.

> **Tip:**
> You can use [built-in IDE macros](built-in-macros.html) to specify the name of the current file, paths relative to the project root, and other contextual information for the tool.

### Tools in WSL

If your project is stored in WSL, path macros return the path in the format that GoLand uses.

The macro preview shows the same value:

```
\\wsl.localhost\Ubuntu\home\me\index.php
```

.

When you run the tool, GoLand converts the paths to the format of the environment where the tool runs.

Check the following example:

```
<path>/home/me/index.php</path>.
```

GoLand selects the environment as follows:

1.  If Program points to a file inside WSL, the tool runs in WSL.

2.  If Program is a command name, such as `node` or `git`, the Working directory defines the environment. If the working directory is inside WSL, the tool runs in WSL, and GoLand looks for the command in the `PATH` of that WSL distribution.

3. In all other cases, the tool runs on Windows.

> **Warning:**
> If Program is an absolute Windows path, for example `C:\Program Files\nodejs\node.exe`, the tool runs on Windows even if the project and the working directory are in WSL. In this case, the arguments contain paths that exist only in WSL, and the tool fails with errors such as `No such file or directory`. To run the tool in WSL, specify the command name or the path to the executable inside WSL.

GoLand converts the path in Program, the path in Working directory, and each argument that consists of a path only. Paths inside longer arguments and paths in environment variables stay unchanged. For example, with the `-e "console.log('$FilePath$')"` arguments, the tool receives the path in the `\\wsl.localhost\...` format.

To get the Linux path, pass it as a separate argument and refer to that argument in the command:

```PLAINTEXT
-e "console.log(process.argv[1])" $FilePath$
```

## Advanced Options

Synchronize files after execution
: Automatically load the changes to your project files made by the external tool. If the tool does not modify any files in your project, you can disable this option.

Open console for tool output
: Open a console with the tool's standard output and error streams.

Make console active on message in stdout
: Activate the console when the tool uses the standard output stream.

Make console active on message in stderr
: Activate the console when the tool uses the standard error stream.

Output filters
: Specify filters to turn absolute file paths, line and column numbers in the output messages into hyperlinks. This will allow you to jump from the console output directly to the relevant location in the file. Each line is a regular expression that defines a separate filter.
:
:
:
:
:
: For example, let's say some tool produces lines of output similar to the following:
:
:
:
:
:
:
: ```PLAINTEXT
: /path/to/file.conf:42:10 WARNING: Some message
: ```
:
:
:
:
:
: Then you can define a filter like this one:
:
:
:
:
:
:
: ```PLAINTEXT
: $FILE_PATH$:$LINE$:$COLUMN$.*
: ```
:
:
:
:
:
: > **Note:**
: > For these filters to work correctly, the tool must output the absolute path to the file. Line and column numbers, if it is present, must be on the same line as the file path.

