Every Tetiva setting lives in one window: press Cmd/Ctrl+, or click the gear at the bottom of the left bar — it opens even with no tabs at all. There is no Save button; changes apply as you make them. Five sections: Appearance, Editor, MCP / DevTools, Updates and About.
Appearance#
The theme is three buttons: Light, Dark, System. System is the default — the app follows the operating system and reacts when you switch it. The theme is applied before the first paint, so launching never flashes a white window at you.
Editor#
Two settings shared by every code editor and the response viewer: font size (12, 13, 14 or 16 px, defaulting to 13) and line wrapping, on out of the box. Both apply to request bodies, to scripts and to the response viewer without reopening tabs.
MCP / DevTools#
This is where the built-in MCP server is turned on: server status, the SSE endpoint, a Copy config button with presets for Claude Desktop and Cursor, the Enable switch and the address field. Changes take effect on the next launch, which the section states plainly with "Restart required to apply". The full story is on the MCP server page.
Updates#
"Check for updates automatically" is on by default. At startup the app reads the manifest at api.tetiva.app/updates/latest.json at most once every ten days, and sends no headers with the request — the version number cannot be traced back to who asked. Switch the toggle off and no request is made at all.
When a newer version exists, a dot appears on the gear icon and settings gain a row with the version and a Download button. Check now runs a check on demand and reports in words: "You're up to date", "vX.Y.Z available", or "Couldn't reach the update server". A failure is never dressed up as "up to date". Updates are installed by hand, by downloading the new build.
Three links sit in the same section. What's New opens the release notes for your installed version — they are bundled with the app and work offline. Show welcome replays the first-launch screen with its "work locally" / "connect an account" choice and the four-screen tour. Documentation opens these docs.
Where the data lives#
Everything is kept in one SQLite file: ~/.tetiva/data.db (on Windows, %USERPROFILE%\.tetiva), with WAL sidecar files next to it. Inside are workspaces, collections, requests, environments and variables, history, the cookie jar, the sync outbox and the MCP settings.
The directory is overridden with the TETIVA_DATA_DIR environment variable; the older GOPHERCOURIER_DATA_DIR still works as a fallback. If a ~/.gophercourier directory is left over from the app's previous name, it is renamed to ~/.tetiva on first launch — there is nothing to migrate by hand.
Not everything lives there. Theme, font size, line wrapping and the "already seen these notes" markers are stored separately, in the embedded browser's storage, and do not travel with the database. The sync refresh token sits in the system keychain under the service name tetiva, mirrored into the database in case the keychain is unavailable.
Logs#
Tetiva writes JSON logs to standard output. There is no log file, so seeing them means starting the app from a terminal. Troubleshooting has the exact commands for macOS and Windows and a list of what to attach to a bug report.
About#
The About section shows the installed version — worth quoting whenever you report a problem.