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 →

Companion rt agent

The web app runs the RequestTailor core in the browser – so the browser’s rules apply: no request to a server without CORS headers, none of the forbidden headers, no client certificates, no gRPC. The rt agent companion runs on your machine and sends such requests for the web app, with the same native transport as rt send. It listens on 127.0.0.1 only, checks every request and pairs through a single-use code.

Start
rt agent in a terminal
Address
127.0.0.1:47812 (default)
Pairing
single-use code, valid for 10 minutes
Tokens
in memory only; a restart revokes all

What the companion is for

The Mac app and rt send natively and know none of these limits. Only the web app needs the companion, and only for:

  • Requests the browser blocks – usually a server without CORS headers or a header the browser does not allow. The web app then asks “The browser blocked this request. Send it through the RequestTailor companion?” and offers Send through companion.
  • Sessions: gRPC, WebSocket and server-sent events always run through the companion in the web app (see gRPC, WebSocket, SSE and GraphQL).
  • Git networking: the web app’s pull and push go through the companion.
  • External secrets from 1Password, HashiCorp Vault, AWS Secrets Manager, Azure Key Vault and Google Secret Manager, if you allow it (below).

Client certificates exist only natively, that is in the Mac app and in rt; the browser and the companion refuse them with a clear TLS error.

Start and pair

  1. Install rt (see Download) and start rt agent in a terminal.
  2. The companion prints a pairing code and a pairing link for each allowed origin, such as Pairing code: 7KQ2-M9XD (single use, valid for 10 minutes).
  3. Open the link in the browser or type the code where the web app asks for it (Pairing code).
  4. The web app exchanges the code for a token and uses the companion from then on whenever you choose it. Stop it with Ctrl+C; a restart revokes every pairing.
OptionMeaning
--port PORTListen on 127.0.0.1:PORT (default 47812, where the web app looks)
--allow-origin ORIGINA web app origin (scheme://host[:port]) that may pair and send; repeatable. Replaces the default list (the web app’s local dev server on port 5173)
--allow-secretsAlso read external secrets for the web app. Default: off

External secrets in the web app

The browser cannot start op, vault and similar programs. With rt agent --allow-secrets, a paired web app sends the references of an environment’s external secrets to the companion, which reads them with the providers’ command lines – with your existing logins, without a shell, with a 60-second timeout. The web app keeps the values in memory for the session only, only to send; they are masked in reports and never stored, not in the companion either.

Security model

The companion is a local server that sends requests with your machine’s network access, internal hosts included. That is why these rules apply, each with tests in the core repository:

  1. Loopback only. It binds 127.0.0.1, never 0.0.0.0; other machines cannot reach it.
  2. Host check against DNS rebinding: every request needs Host: 127.0.0.1:<port> or localhost:<port>, otherwise 403.
  3. Allowed origins (CORS): a request with a foreign Origin gets 403 without CORS headers, never *.
  4. Pairing: the code has 40 random bits, is valid once and for 10 minutes; after 5 wrong attempts it is replaced. The token has 256 bits and is bound to the origin.
  5. Tokens in memory only, compared in constant time; nothing is written to disk.
  6. Secrets only when asked for, with --allow-secrets, without caching, with Cache-Control: no-store.
  7. Nothing else: five endpoints, no file access, no configuration over HTTP; it refuses requests to itself.
  8. Logging: one line per request with method and host, never paths, headers or bodies; for secrets only provider, count and origin.

What it does not protect against: other programs running as your user can reach 127.0.0.1 too – but they can pair only with the code from your terminal. A compromised page on an allowed origin can use that origin’s token like the web app itself; allow only origins you trust.

Typical problems

Message or situationWhat helps
“The companion did not accept this code. Use the newest code `rt agent` printed.”Every used, expired or replaced code is followed by a new one in the terminal. Type the newest.
The web app does not find the companionIs rt agent running? With a custom port, the web app must know the same one; the default is 47812.
Pairing from a hosted web app failsAllow its origin with --allow-origin https://…; the default list contains only the local dev server.
External secrets are not readRestart rt agent with --allow-secrets and pair again; the provider’s command line must be installed and signed in.

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

    The rt agent companion for the web app ↑Product · RequestTailor core repository, crates/rt-cli/src/agent, crates/rt-cli/README.md (Sicherheitsmodell) · 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.

Do I need the companion in the Mac app?
No. The Mac app and rt send natively. Only the web app needs the companion, for requests the browser blocks, for sessions such as gRPC and WebSocket, for Git networking and for external secrets.
Can someone on the network use my companion?
No. rt agent listens on 127.0.0.1 only, checks the host and origin of every request and sends only for a web app that paired with the single-use code from your terminal.
Does the companion store my requests or secrets?
No. It logs only method and host per request, never paths, headers or bodies. Tokens live in memory only, and secret values are not cached.

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.