RequestTailor Preview (22 November 2026): requests as files in Git, no account, offline – on the Mac, in the browser and in the pipeline. What’s inside → +43 664 1964199Contact →

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 folder: 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 files, 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

  1. Open the collection with Open folder.
  2. Choose New request (Mod+N, or + next to REQUESTS in the sidebar).
  3. Enter method, URL, headers and body.
  4. 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

Sources on this page

The superscript numbers in the text point here. Tap one to see the source right where it is used; all sources of this website are listed on one page.

  1. 1

    Requests as OpenCollection YAML, one file per request ↑Product · RequestTailor core repository, CLAUDE.md (Produktprinzip „Dateien sind die Wahrheit“), crates/rt-format, website/docs/collections · checked on 2026-11-22

  2. 2

    Byte-identical round trip, 86 Bruno collections ↑Product · RequestTailor core repository, testdata/collections/bruno, crates/rt-format (Round-Trip-Tests) · checked on 2026-11-22

Frequently asked

Short answers.

Can I edit the files with a text editor too?
Yes. The files are readable YAML; the app reads the folder again the next time it opens or reloads it. It keeps no copy of its own.
What happens to comments in my YAML files?
They are kept. Reading and writing is byte-identical; saving changes only the part you changed.
Does the collection have to be in Git?
No. A collection is a folder; Git is optional. With Git you get diffs, branches and reviews without special tools.

Your question isn’t here? Talk to me: +43 664 1964199 office@clouddna.at Get in touch

Contact

Requests in the repo instead of an account? Talk to us.

Free is free and stays free. For an early copy, for Enterprise, for the OData plugin on your SAP system or for a wish for Pro and Team: write to me. I reply within one working day, personally.

Martin KochManaging Director, CloudDNAI read every request myself and reply personally.