Workspace

JetBrains Fleet uses the concept of Workspace to define the scope of the code you are working on. In practical terms, a workspace is a folder, either on a local or remote system, that contains the files you need for development.

Open a local workspace

Press ⌘ O or select File | Open from the main menu.
Select the folder and click Open.

Another way to create a workspace is to clone a repository from VCS. The repository opens in a separate window.

Clone a repository

From the Workspaces menu, select Clone from Git.
In Source URL and Location fields, specify the repository URL and the desired git-clone location.
Click Clone.

When you open a workspace, you can view the hierarchy of files that belong to it in the Files tree.

If you need to work with multiple locations, you can attach additional folders to the open workspace.

Attach multiple folders

Press ⌘ ⇧ K and start typing Add Folder. Select Add Folder.
Select a folder. The selected folder gets attached alongside the existing one.

Rename a workspace

Click the workspace name and select Rename Workspace. Type a new name and press ⏎.
Press ⌘ ⇧ K and start typing Rename Workspace. Select Rename Workspace. Type a new name and press ⏎.

Creating a workspace with AI in JetBrains Fleet

JetBrains Fleet provides a feature that allows users to generate a workspace using AI. This functionality streamlines the initial setup process by creating the necessary structure and providing example code tailored to the desired template.

Create a workspace with AI

Launch JetBrains Fleet.
On the welcome screen, click the Create with AI button.
When you click this button, JetBrains Fleet opens the AI Assistant view.
In the AI Assistant view, type the prompt and specify what kind of a template you want to generate.
The AI will use this information to build the project structure and insert example code into the generated files.
Click the Create Workspace button and select an empty directory on your hard drive where the workspace will be saved. Ensure that the directory is empty.
With the workspace set up, you can begin developing your project. Use the example code as a starting point and customize it as needed.

Workspace settings

In addition to user settings, which apply globally to all files, you can specify settings for a particular workspace. These settings will only apply to files in this folder, and will be shared among all the users of the workspace.

Open the workspace, whose settings you want to edit.
Press ⌘ , to open settings.
Alternatively, to open settings, you can use the main menu:
- Windows and Linux: click the Menu icon and navigate to File | Settings | Settings.
- macOS: from the main menu, click Fleet | Settings.
Click the tab with the name of your workspace.

Edit workspace settings through settings.json

In the workspace settings menu, select Show settings.json.
Alternatively, open the .fleet folder in the workspace, whose settings you want to edit. If no settings have been defined for the workspace, and the .fleet folder does not exist, create the folder and the settings.json file in it.
Fill in settings.json with the required settings using JSON syntax.
For available settings and their descriptions, refer to Settings reference.
If you don't know the name of the setting, type a quotation mark and try some related words to see if the required setting appears on the suggestion list.
Changes are applied immediately when you save the file.

Subfolder settings

Workspaces support nested settings in their subfolders. You can use them to achieve any level of granular control when you need custom settings for subfolders.

settings.json in a workspace subdirectory

To achieve the necessary granularity, create .fleet/settings.json in a subfolder. When you are working with files inside the subfolder, these settings will override the more general workspace settings.

Application settings

You can change the default directory locations for JetBrains Fleet. Specifically, you can set new paths for your configuration, caches, and plugins.

Default locations

Configuration directory

Windows	%APPDATA%\JetBrains\Fleet
Linux	~/.config/JetBrains/Fleet
macOS	~/Library/Application Support/Jetbrains/Fleet

Caches Directory

Windows	%LOCALAPPDATA%\JetBrains\Fleet
Linux	~/.cache/JetBrains/Fleet
macOS	~/Library/Caches/JetBrains/Fleet

Plugins Directory

WS Server	<config_path>/pluginStorage
Frontend	<config_path>/plugins

Change directory locations by using the fleet.properties file

Locate the fleet.properties file. The default locations of the file are:
- Home directory: ~/fleet.properties
- Default caches directory: <caches_dir>/fleet.properties. Value of <caches_dir> depends on your operating system. For more information, refer to Caches Directory.
Open fleet.properties in an editor and add the following properties to the file:
- fleet.config.path=<your_custom_path>: sets a path to the configuration directory.
- fleet.caches.path=<your_custom_path>: sets a path to the caches directory.
- fleet.log.path=<your_custom_path>: sets a path to the logging directory.

Change directory locations from JetBrains Fleet

Press ⌘ ⇧ , to open settings.json. A separate editor tab opens. In the opened tab, specify the required settings using JSON syntax.
Add the following property to settings.json.
"internalMode": true
Press ⌘ ⇧ K and type Open FleetCfg.
In the Fleet.cfg file, add the following properties:
- java-options=-Dfleet.config.path=<custom_path>: a property that sets a path to the configuration directory.
- java-options=-Dfleet.caches.path=<custom_path>: a property that sets a path to the caches directory.
- java-options=-Dfleet.log.path=<custom_path>: a property that sets a path to the logging directory.
Restart JetBrains Fleet.
Properties in Fleet.cfg are processed first. If the same property is specified in the fleet.properties file, the property from Fleet.cfg will be overridden.
In PROPERTIES files, if you want your value to include a backslash (\), it should be escaped by another backslash (\). For example, F:\\Fleet\\config.

Set a location of fleet.properties with the FLEET_PROPERTIES_FILE environment variable

To set the location of the fleet.properties file, follow the procedure for your operating system:

Press Win + R, type cmd, and press ⏎.

Type set FLEET_PROPERTIES_FILE=C:\path\to\your\file and press ⏎. This will set the variable for the current session only.

To set the environment variable permanently, consider adding it in the System Properties window.

Search for the Terminal application in the Utilities folder within your Applications folder, or use Spotlight to search for it.

Type export FLEET_PROPERTIES_FILE=/path/to/your/file and press ⏎. This will set the variable for the current terminal session only.

To set the environment variable permanently, consider adding export FLEET_PROPERTIES_FILE=/path/to/your/file to .bashrc for bash or .zshrc for zsh.

Search for Terminal in your application menu or by using a keyboard shortcut, often it is Ctrl+Alt+T.

Type export FLEET_PROPERTIES_FILE=/path/to/your/file and press ⏎. This will set the FLEET_PROPERTIES_FILE variable for the current session only.

To set the environment variable permanently, consider adding export FLEET_PROPERTIES_FILE=/path/to/your/file to .bashrc, .bash_profile, or .profile files.

Last modified: 20 September 2024

JetBrains Fleet 1.44 Help