Skip to content

Settings and files

Open Preferences with the gear at the top right, or Ctrl+,. On macOS it’s also under Reqjet › Preferences… in the menu bar. They open as a tab.

Setting What it does
Theme System, light, dark or high contrast. System follows your operating system, and switches to high contrast when that’s turned on in Windows.
Zoom The size of everything. Also Ctrl+= and Ctrl+-.
Response history How many responses each request keeps for its History tab. The default is 20; 0 keeps none.
Proxy The system proxy (the default), no proxy, or a manual one with a bypass list and an optional user name and password.
Check for updates Whether Reqjet checks for a new release, at most once a day.
Settings file Where your settings are kept, with Open folder and Move….
Troubleshooting Copy diagnostic info and Open log folder, for reporting a problem.

Requests go through the system proxy unless you choose otherwise. With a manual proxy:

  • The bypass list takes hosts and patterns such as *.corp.local, 10.*. Local addresses always skip a manual proxy.
  • Without a user name, a proxy that asks you to sign in gets your Windows sign-in (NTLM or Kerberos), which is what most company proxies expect.

The proxy applies to every request, WebSocket and event stream.

Your settings are kept per user, never in your folders or workspace files:

System Folder
Windows %APPDATA%\Reqjet
macOS and Linux ~/.config/Reqjet

The folder holds:

  • settings.json: your preferences, open folders and tabs, window size and position, selected environments, and recent folders and workspaces.
  • workspaces/: each saved workspace’s own open tabs and environments.
  • runbooks/: progress through runbooks, so a long operation can carry on after a restart.
  • logs/: Reqjet’s own errors, never your requests, kept for a week.

To keep settings somewhere else, such as a folder synced between PCs, use Move… under Settings file. On managed machines, the REQJET_SETTINGS_DIR environment variable sets the folder.

If settings.json isn’t valid JSON, for example after a bad hand edit, Reqjet keeps it as settings.broken-<date>.json and starts with the defaults.

Kept in memory only, never written to disk: response history, OAuth tokens, cookies and # @prompt answers. Responses can hold tokens and personal data, so they go when you close Reqjet.

File What it’s for
*.http, *.rest Requests.
http-client.env.json Environments, shared with your team.
http-client.env.json.user Private environment values. Keep it out of git.
http-client.private.env.json JetBrains’ private environment values, read too.
.vscode/settings.json VS Code REST Client’s environments (rest-client.environmentVariables), read but never changed.
.env Values for {{$dotenv NAME}}.
*.reqjet-workspace A saved workspace: a list of folders.
*.md with an ```http block A runbook.
*.js that calls send("…") A script file.
__snapshots__/<file>.snap.json Saved snapshots for # @reqjet.snapshot tests. Commit them; the folder is hidden in the tree.
Command What it does
Reqjet Reopens what you had open: your folders, or the last workspace.
Reqjet ./api Opens a folder.
Reqjet ./api/orders.http Opens a .http file.
Reqjet orders.reqjet-workspace Opens a workspace.
Reqjet --new-instance Starts a separate copy, in its own window.

Opening a file or folder while Reqjet is already running opens it in the running window, which comes to the front.