Skip to main content
Bruno helps you organize your API requests efficiently by grouping them into folders. You can create a structured hierarchy that matches your API’s organization, making it easier to manage and navigate your collections.

Creating a New Folder

  1. Select your Collection from the sidebar.
  2. Click on the ··· button.
  3. Select New Folder from the dropdown menu.
create folder
  1. Enter a name for your folder.
  2. Click Create to finish.
new folder dialog Your new folder is now ready to organize your requests!

Folder tags

Define tags once on a folder and every request inside it inherits them. Use this for suites you already group by folder, such as smoke tests or regression runs, instead of tagging each request by hand.

Add tags to a folder

  1. Select the folder in the sidebar.
  2. Open the Settings tab.
  3. In the Tags section, type a tag and press Enter. The placeholder shows examples such as smoke or regression.
  4. Save. Each tag appears as a removable chip.
Folder Settings tab with Tags input and chips

How folder tags work

  • Inherited by requests — every request in the folder (and nested folders) picks up the folder’s tags.
  • Combined with request tags — effective tags for a request are its own tags plus inherited folder tags.
  • Runner filters — Collection Runner Include tags / Exclude tags (and the matching CLI tag filters) match on effective tags, so folder tags count the same as request tags.
  • Visual distinction — on a request or nested folder, direct tags stay editable as chips; inherited tags show separately (expand Inherited from parent) and name the source folder.
  • Persistence — tags are stored in the folder config (folder.bru or folder.yml) and travel with the collection through Git.
Nested folders inherit from their parents the same way. A request two levels down gets tags from every ancestor folder plus its own. For filtering runs by tags in the app, see Tag-Based Request Filtering.

Ignore folders

You can hide folders from a collection without deleting them. Ignoring a folder adds it to the collection’s ignore config and removes it from the sidebar. This is useful for folders that should stay on disk (for example assets, fixtures, or generated files) but should not appear as part of the runnable collection.
  1. Right-click a folder in the collection sidebar (or use the ··· menu).
  2. Select Ignore.
  3. Bruno adds the folder to the collection ignore config and the folder disappears from the sidebar.
Ignore folder from the sidebar
You no longer need to hand-edit the collection config file to ignore a folder. Use the sidebar menu instead. Bruno updates opencollection.yml or bruno.json for you.

Config after ignoring a folder

After you ignore a folder such as assets from the UI, Bruno appends it to the ignore list. Existing entries like node_modules and .git stay unchanged.
opencollection.yml
In the example above, assets is the folder ignored from the sidebar. The folder remains on disk. It is only hidden from the collection tree.

Custom Folder Names

You can use any characters in your folder names, including special characters like /, [, ], *, etc. Bruno automatically handles filesystem compatibility by replacing unsupported characters with - in the filenames while preserving your original folder name.

How to View or Customize Filesystem Names

  1. Select Show Filesystem Name.
show filesystem name
  1. You can now see how your folder name is stored on the filesystem.
filesystem name view
  1. (Optional) Click the edit icon to customize the filesystem name while keeping your display name intact.
This feature allows you to:
  • Create more descriptive folder organization.
  • Use special characters freely.
  • Maintain filesystem compatibility automatically.
  • Keep your collection structure clean and organized.

Example

You could name a folder “API [v2.0] / Authentication” and Bruno will automatically handle the filesystem compatibility while preserving your desired display name.