Organizing Collections

As a collection grows, folders and a consistent structure keep it navigable. Vegha lets you nest folders freely and share configuration down the tree.

Folders and nesting

A folder is a subfolder inside a collection. You can nest folders as deeply as your project needs — for example, group requests by API resource, by feature, or by environment-specific workflow. Right-click any collection or folder in the Collections panel to add a child folder.

A common layout looks like this:

my-workspace/
  payments-api/
    auth/
      login.bru
      refresh-token.bru
    customers/
      list-customers.bru
      create-customer.bru
    invoices/
      create-invoice.bru

Ordering requests

Requests and folders display in a defined sequence rather than alphabetically. The order is recorded in each request’s meta block via its seq value. Reorder items by dragging them in the Collections panel; Vegha updates the sequence on disk. A predictable order is especially useful when requests are meant to run as a workflow — for example, log in, then create resource, then clean up.

Inherited configuration

Folders can carry their own headers, authorization, and variables. Any request inside a folder inherits these automatically, so you do not have to repeat them on every request.

Defined at	Applies to
Collection	Every request in the collection.
Folder	Every request in that folder and its subfolders.
Request	That request only.

When the same setting is defined at more than one level, the most specific level wins:

request overrides folder overrides collection.

For example, if a folder sets a Bearer token but one request inside it sets its own Authorization, that request uses its own value while its siblings keep the folder’s.

Precedence

A request always has the final say. Folder and collection settings are defaults that requests may override.

Naming conventions

Because every request and folder is a file or directory on disk, pick names that read well both in the Collections panel and in a file browser:

• Use clear, action-oriented request names — Create invoice, not req3.
• Keep folder names short and resource-oriented.
• Avoid characters that are awkward in file paths.

Moving requests

Drag a request or folder to a new parent in the Collections panel to move it. Vegha moves the underlying file or directory on disk. You can also move items by relocating files in your file explorer — the panel reflects the change the next time the workspace is read.

Finding requests quickly

In a large collection, browsing the tree is slow. Press Ctrl+K (⌘+K on macOS) to open the Find request palette, type part of a request name, and jump straight to it. This is the fastest way to navigate once a collection has more than a handful of requests.