Run configurations

To run code, tests, or tasks, JetBrains Fleet uses run configurations.

A run configuration defines the parameters for running your application. It can include commands, executable paths, environment variables, virtual machine options, arguments, and other required context.

Create a run configuration

Press ⌘ R or select Run | Run & Debug from the main menu. In the popup that appears, click Create Run Configurations.
The .fleet/run.json file opens. This file defines run configurations for the workspace and uses JSON format.
Define new configurations as objects inside the configurations array. For example, this configuration runs script.sh using a macro to specify its path:
{ "configurations": [ { "name": "Run my script", "type": "command", "program": "$USER_HOME$/script.sh", "args": ["any", "optional", "arguments"] } ] }
For more information about available run configuration types and their parameters, see: Java, Kotlin, Go, PHP, JavaScript, Python, C#, Rust, C/C++.
For details on macros like $USER_HOME$ , refer to Run configuration macros.
You can explore available parameters using code completion. Press ⌃ Space at the caret to view suggestions.

Launch a run configuration

Press ⌘ R or select Run | Run & Debug from the main menu. Select the configuration you want to run or debug.

Run configuration properties

Each run configuration can include the following properties:

Key	Description
`name`	A human-readable name that identifies the run configuration.
`type`	The configuration type, which determines how the application will be launched. Additional parameters depend on the selected type. For supported types and their parameters, refer to: JavaScript, Java, Kotlin, Go, Python, C#, PHP, Rust.
`environment`	Custom environment variables for the process, specified as a JSON object. To define an environment variable, add a property where the key is the variable name and the value is its value. For example: "environment": { "TEMP_DIR": "/home/user/temp", "GENERATE_RANDOM_PASSWORD": "true" }
`dependsOn`	Names of other configurations to run before this configuration. For example: `"dependsOn": ["first", "second"]`. For details, see Chained run configurations.
`workingDir`	Working directory for the run configuration.
`allowParallelRun`	If set to `true`, multiple instances of this configuration can run simultaneously.

08 May 2025