Collections as files
The folder is the collection. The app reads it and writes changes back; it keeps no copy of its own. Every request is a readable YAML file in OpenCollection format, so a diff in Git shows exactly what you changed.
- Format
- OpenCollection 1.0 (YAML), as Bruno writes it
- Root
opencollection.yml- Per request
- one file
- Saving
- byte-identical for unchanged parts
Folder layout
my-api/
opencollection.yml the collection: name, default headers, auth, variables
users/
folder.yml optional: folder name, order, defaults for its requests
get-user.yml one request per file
create-user.yml
environments/
Local.yml one file per environment
Staging.yml
A folder inside the collection that has its own opencollection.yml is a separate collection. The app is only a view of the folder1: what you change in it ends up as a file change in the folder, and what you change in an editor the app sees the next time it reads.
A request file
info:
name: Get user
type: http
seq: 1
http:
method: GET
url: "{{baseUrl}}/users/{{userId}}"
headers:
- name: Accept
value: application/json
auth: inherit
auth: inherit takes the authentication of the folder or the collection. The URL is the truth for the query string; query parameters in a params list only mirror it. You write variables as {{name}} – where their values come from is explained in Environments and variables.
RequestTailor reads body files (file bodies, multipart parts) relative to the collection root. Absolute paths, .. and symlinks that lead outside the folder are refused.
OpenCollection and Bruno
The files follow OpenCollection 1.0, the YAML format Bruno writes. You open Bruno collections in that format unchanged with Open folder. OpenCollection allows no unknown fields; RequestTailor’s own data – such as the rules for AI agents – goes into the extensions section of opencollection.yml or into companion files.
Saving without side effects
Reading and writing gives byte-identical files2, comments and formatting included. When you change one request, only that part of that file changes – a diff shows what you did and nothing else. The test suite checks this on every commit against 86 Bruno collections. What a writer cannot do exactly is refused by the read-back check instead of silently changing the file.
New collections and new requests
- Open the collection with Open folder.
- Choose New request (Mod+N, or + next to REQUESTS in the sidebar).
- Enter method, URL, headers and body.
- Save with Mod+S. The app writes a new YAML file into the folder.
Existing collections from Postman, Insomnia, OpenAPI, cURL, HAR or .http come in through Import.
See also
- Features at a glance Features · dateien
- Docs Git
- Docs Import
- Docs Environments and variables
- Sources Format1 · Round trip2