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 →

Environments and variables

Values that differ between systems live in environments. Values that must stay secret never enter the collection folder: the file names only the variable, the value lives in the operating system’s keychain or comes from your secret manager.

Edition
Free
Layers
global, collection, environment, folder, request, runtime
Files
environments/<name>.yml
Secrets
keychain (Mac), encrypted in the browser (web)
Vaults
1Password, HashiCorp Vault, AWS, Azure, Google

Where a variable comes from

You write variables as {{name}}. They are resolved in layers; a later layer wins:

  1. Global
  2. Collection (opencollection.yml)
  3. Environment (environments/<name>.yml)
  4. Folder (folder.yml)
  5. Request
  6. Runtime (for example --var on the command line or values set by scripts)

The precedence is the same as in Bruno. Hover over a variable in the URL and RequestTailor shows its value and the layer it comes from.

Tooltip over the variable baseUrl in the URL with the text baseUrl, environment Local and the value http://127.0.0.1:47811
Where a value comes from: name, layer and value right at the URL.

The JSON report of rt send also names the origin of every variable and lists placeholders without a value under unresolved.

Create and switch environments

At the top right you choose the active environment; a dot in front shows its state. Environments next to it opens the manager.

Environments dialog with the environments Local (active) and PRD, variables baseUrl and token, token as a secret with stored securely and Reveal, below it External secrets and Client certificates
The Environments dialog: variables, secret checkbox, external secrets and client certificates.
  1. The environments on the left; New environment creates one.
  2. Rename, Duplicate and Delete for the chosen environment.
  3. Per variable: Enabled, Name, Value and the Secret checkbox. A secret shows stored securely; Reveal shows the value briefly.
  4. External secrets picks a secret manager.
  5. Client certificates for servers that require mutual TLS.
  1. Open Environments at the top right and choose New environment.
  2. Create the variables with Add variable, for example baseUrl.
  3. For a password or token, create a variable and tick Secret; enter the value once.
  4. Click Save. RequestTailor writes only the name into the file; the value goes into the keychain.

Secret variables

A secret variable is declared in the environment file without a value:

name: Staging
variables:
  - name: baseUrl
    value: https://api.staging.example.com
  - secret: true
    name: apiToken

The Mac app keeps the value in the operating system’s keychain, the web app keeps it encrypted in the browser’s storage. It is added only when a request is sent, and reports show it as ***. OAuth 2.0 tokens are kept the same way. Whoever clones the collection gets the names but no values and enters their own.

Secrets from a secret manager

An environment can read secrets from a secret manager through that manager’s own command line, with your existing login. The file holds only the reference:

name: Staging
externalSecrets:
  type: one-password
  variables:
    - name: apiToken
      secretReference: op://Staging/api/token
typeCommand line
one-passwordop
hashicorp-vault-server, hashicorp-vault-cloudvault
aws-secrets-manageraws
azure-key-vaultaz
gcp-secrets-managergcloud

Values are held in memory only and masked in every report. The command line runs without a shell and with a 60-second timeout; if it or the login is missing, RequestTailor says what to install or which login command to run. The web app cannot start these programs; there the rt agent --allow-secrets companion reads them (Companion rt agent). The fields per provider are in rt command line.

Client certificates

You configure client certificates (PEM or PKCS#12) per collection or per environment; paths are relative to the collection folder. The passphrase belongs in a secret variable such as {{certPassphrase}} so that it stays out of the file. The Mac app and rt use the certificates; browsers do not let web pages present client certificates, so the web app reports a clear TLS error.

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

    Variables in six layers with origin ↑Product · RequestTailor core repository, crates/rt-core (vars::Scope), website/docs/environments · checked on 2026-11-22

  2. 2

    Secrets in the keychain and from external vaults ↑Product · RequestTailor core repository, CLAUDE.md (Produktprinzip 3), crates/rt-cli/README.md (externe Secrets), website/docs/environments · checked on 2026-11-22

Frequently asked

Short answers.

Are passwords stored in the YAML files?
No. A secret variable is in the file without a value. The value lives in the operating system’s keychain (Mac app) or encrypted in the browser (web app), or comes from a secret manager.
Which secret managers does RequestTailor support?
1Password, HashiCorp Vault (server and cloud), AWS Secrets Manager, Azure Key Vault and Google Secret Manager, each through the provider’s command line with your login.
In which order do variables apply?
Global, collection, environment, folder, request, runtime; a later layer wins. That matches Bruno’s precedence.

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.