Skip to content

Settings

Open the settings with the gear button at the right of the toolbar, Quena → Settings… (⌘ ,) on macOS, or Tools → Options… on Windows and Linux. Changes take effect when you click OK, except for the layout, theme and inspector-view choices, which apply immediately.

This manual uses the English names of menus and settings.

General

Setting Default Meaning
Layout Quena Quena — list left, request above response. Classic — dense list, request above response, more columns. View → Request Beside Response puts them side by side in either.
Theme Like the system Like the system, Light or Dark.
Language Like the system Like the system, English or Deutsch. Switching reloads the window and the menus.
Inspector views grouped Grouped: sections Headers, Body, Cookies, Auth, Raw, with the views that fit the body below them. Flat: all views in one row, as before 0.1.5. See Inspect.
Inspector views: remember on Remember the chosen view for each kind of content, separately for request and response (e.g. SOAP → XML, JSON → Body). Shows how many are remembered, with Forget remembered views.
Capture traffic on startup on Start capturing when Quena starts.
Stream responses (instead of buffering) on Same as the Stream toolbar toggle.
Decode compressed bodies in inspectors on Same as the Decode toolbar toggle.
Keep capture data after exit off Keep the capture database after a clean exit.
AutoSave the sessions every … minutes, keep the last … archives off, 10, 10 Save all sessions as .saz into the AutoSave folder when something changed (see AutoSave).
Offer to recover sessions after a crash on Offer the previous capture at the next start if Quena did not exit cleanly.
Importing into a non-empty list Ask Loading an archive or packet capture stops capturing; the sessions in the list are then asked about, removed (only the import is in the list) or kept (the import is added). See Archives.

Switching the layout also resets the columns to that layout's set. View → Request Above Response / Request Beside Response changes only the inspector arrangement.

Optional Classic layout: dense session list with more columns, request above response

Connections

Setting Default Meaning
Listen port 8866 The port Quena listens on.
Act as system proxy while capturing on See System proxy.
Allow remote computers to connect off Listen on all interfaces.
Allowed remote networks empty (local subnets) CIDR ranges or addresses, ;-separated.
Chain to the previous system proxy (upstream gateway) on Forward to the proxy that was active before.
Manual upstream proxy empty host:port; overrides the system upstream and PAC.
Do not capture (bypass Quena) empty Hosts (login.example.com; *.bank.example) that do not go through Quena at all: they become exceptions of the system proxy and of browsers and terminals Quena starts (--proxy-bypass-list, Firefox No proxy for, NO_PROXY). A client that sends them to Quena anyway gets them passed through without decryption. Changes apply to the system proxy at once; right-click a session → Filter Now → Do not capture this Host… adds its host.
Also bypass Apple services that pin their certificates on (macOS), off elsewhere *.push.apple.com, *.ess.apple.com, gs.apple.com, albert.apple.com, identity.apple.com, *.apple-cloudkit.com — push notifications, iMessage and FaceTime, activation and signing, Apple ID and CloudKit would fail behind any intercepting proxy.
Also bypass the domains of an active VPN off The DNS domains of a VPN connected when capturing starts (scutil --dns on macOS, resolvectl on Linux, the adapter's DNS suffix on Windows), e.g. *.corp.example: company traffic keeps its direct way. They are looked up when capturing starts (at most 5 s); start capturing again after connecting the VPN.
Bypass upstream for localhost;127.0.0.1;::1;*.local Hosts that go direct; also networks (10.0.0.0/8) and <local> (names without a dot). The previous system proxy's exceptions apply as well.
Use the system proxy auto-config (PAC) script on
PAC URL or file empty Overrides the system PAC.
Host remapping none Host Remapping… opens the host remapping entries (also Capture → Host Remapping…).
Reverse proxy ports none Reverse Proxy… opens the reverse proxy entries (also Capture → Reverse Proxy…).
SOCKS5/4 port off, 8868 A SOCKS port; from other computers too listens on all interfaces.
Transparent port off, 8869 A port for transparently redirected connections.
Throttle (kbit/s) / Added latency (ms) 0 Bandwidth simulation.

HTTPS

Decrypt HTTPS traffic (off by default), Decrypt traffic from, Skip decryption for, Ignore server certificate errors (unsafe), Ignore certificate errors for, Enable HTTP/2, Downgrade to HTTP/1.1 for, and Certificate management… (trust, export, import an existing CA, Warn about server certificates expiring within (days), default 30) — see HTTPS and devices.

Packet captures holds a TLS key log file (SSLKEYLOGFILE) used to decrypt HTTPS in every imported .pcap/.pcapng — see Packet captures.

Authentication

See Automatic authentication.

Bodies & Storage

Setting Default Meaning
Keep bodies in memory up to (KB) 64 Smaller bodies stay in memory; larger ones go to disk.
Record at most per body (MB) 2048 Longer bodies are forwarded completely but recorded only up to this size.
Storage quota (GB) 200 Disk space the capture may use.
Stop recording below free space (GB) 5 Recording is suspended when the disk gets this full; the status bar says Recording suspended (disk).
Max decoded size (GB) 64 Upper limit for decoded (decompressed) copies of bodies.
Max decompression ratio 2000 Protection against decompression bombs.
Headers only for hosts empty Record only headers for these hosts.
Headers only for content types empty Record only headers for these types, e.g. video/; audio/.
Lossless recording (forwarding waits for the disk) off Normally a recorder that falls behind truncates the recording instead of slowing traffic down; with this on, forwarding waits.
Protobuf schemas none .proto files and folders, import paths, and whether the gRPC view may fetch a schema from the server (server reflection). See gRPC and Protobuf with a schema.
LLM prices built-in list Where the estimated cost of LLM calls comes from: your own prices (Create llm-prices.json / Edit llm-prices.json), a price list fetched on request (Fetch prices / Update prices, Remove list), then the built-in list prices.
Agent cache off Cache every LLM call, the cached answers with their hits and what they saved (Show, ✕, Remove all), and calls asked more than once that are worth caching. See Agent cache.

llm-prices.json holds US dollars per million tokens by model name prefix: input, output, optionally cacheRead and cacheWrite, and context for the model's context window in tokens (used by the context map and the hints of the Agents panel):

{ "my-model": { "input": 1, "output": 4, "cacheRead": 0.1, "context": 128000 } }

AI agents (MCP)

Quena's MCP server for AI agents: on/off, port, what agents may do, whether they see secrets, their file folder and the token — see Quena's MCP server.

Data directory

Quena keeps everything it stores in one folder:

  • its settings, the capture database (captures) and the root certificate;
  • mock rules (autoresponder.json), rewrite rules (rewrite.json), the rules script (rules.js) and request collections (collections);
  • your plugins (plugins), the plugin cache (plugin-cache) and schemas fetched from gRPC servers (protobuf-reflection);
  • your own LLM prices (llm-prices.json), the fetched price list (llm-prices-litellm.json) and the agent cache (llm-cache);
  • recordings of quena-cli mcp-tap (mcp-tap);
  • the profiles of browsers Quena starts (browser-profiles), the start scripts of the terminals it opens on macOS and Windows (terminal) and, on macOS and Linux, the system's root certificates plus Quena's for those terminals (quena-ca-bundle.pem);
  • unless set elsewhere, the folder for AI agents' files (mcp-files) and AutoSave archives (autosave).
Platform Default location
macOS ~/Library/Application Support/Quena
Windows %APPDATA%\Quena
Linux ~/.local/share/Quena (or $XDG_DATA_HOME/Quena)

The environment variable QUENA_DATA_DIR points Quena to another folder. Captures are stored in the captures subfolder; the status bar's storage cell shows the capture folder in its tooltip.

Portable mode

If a folder named quena-data, or an empty file named portable, exists next to the Quena executable, Quena uses quena-data as its data directory — on every platform. The web view's cache and storage are kept there as well, and bundled plugins are found in a plugins folder next to the executable.

The Windows portable ZIP ships in this form. Delete the portable file (and quena-data) to use the normal per-user location again. The folder must be writable: on a read-only drive Quena shows a message on start and quits.

Things outside the folder that Quena touches only when you use them: the system proxy (restored on quit), a trusted root certificate (remove it in HTTPS Settings), and saved passwords in the OS secure store.