All pages

Docs · Configuration

Settings

Availability: macOS.

⌘, opens the Settings window. It has tabs for General, Account, Appearance, Font, Keybindings, Shortcuts, Integrations, API Keys, AI Agent, Notifications, Updates, Profiles, Security, Permissions, and a few feature panes (Containers, VibeHub, TestFlight). A search bar at the top jumps straight to any setting. The first thing to know: TRMNLY does not edit your Ghostty config file.

How overrides work

When you change something in Settings, TRMNLY writes the change into a temp override config file (UserOverrides). On launch and on reload, libghostty loads your normal config first and then the override file last — so the override always wins. Reset a field to its default and its line drops out of the override file.

What this buys you:

  • Your config file stays clean and version-controllable
  • Settings UI changes survive :reload-config
  • You can hand-edit your config to test something and the UI override gets out of the way

What lives in overrides (today):

  • Theme (and per-project theme)
  • App chrome appearance (Auto / Light / Dark)
  • Default font size
  • Ligature on/off
  • Keybindings
  • Update channel + auto-update mode
  • Cursor color / style / blink / trail length / trail color

Sections

General

Sleep prevention (keep the Mac awake for running commands, draining queues, or always), quit behavior when something is still running, opening terminal links in the in-app browser, and open/reload buttons for your config file.

Appearance

Theme picker (with live preview), app chrome appearance (Auto / Light / Dark), UI density, ligature toggle, cursor style / blink / trail. Theme changes apply immediately to all open windows.

Font

Default font size plus per-project font sizes, and the ligature toggle again for good measure.

Keybindings

Rebind TRMNLY's built-in actions: click Record on a row and press the chord. See Keybinds for the defaults and the recording flow.

Shortcuts

User-defined chords that trigger new actions — send text, run a saved prompt or runbook, capture a screenshot. See Custom shortcuts.

Integrations

Every service TRMNLY holds a credential for — the model providers, Whisper, ElevenLabs, VibeHub — with a live status for each: Not set, Stored, Verified , Rejected, or Unreachable. Verify asks the service whether the key still works; Verify all does the lot. Nothing is checked in the background, so no probe runs that you didn't ask for (bar one automatic check right after you save a key). Configure jumps to whichever pane owns the field.

"Rejected" and "Unreachable" mean different things on purpose: the first is the service refusing the key, the second is us never getting an answer. Don't go re-issuing a key over an unreachable badge.

API Keys

Paste a key for Anthropic, OpenAI, Google Gemini, or OpenRouter, plus a voice transcription key and endpoint, and Web Search keys (Brave Search, Tavily, Exa, Serper, Perplexity) for the agent's web_search. Stored in the macOS Keychain — never in your config or settings export. Ollama / LM Studio endpoints live in the agent sidebar's provider sheet.

Saving verifies the key against the provider straight away. If the Keychain refuses the write you get an error, not a green check — and if the cause is a replaced app bundle (a rebuild while TRMNLY was running) the message says so and offers to relaunch.

If a key for one of these providers is sitting in the Keys vault instead, the empty row offers to copy it across. TRMNLY's own provider calls only ever read this pane.

AI Agent

Default model, agent behavior, project context (TRMNLY.md, wired into CLAUDE.local.md), the trmnly-code CLI installer, Claude Code sessions, Conversation archive, Terminal history, External MCP clients (the MCP server bridge), Remote Control (trmnly.dev) — pairing, connected devices, transport — then Web search, network allowlist, filesystem sandbox, voice & speech, local telemetry, and shortcuts to the agent sidebar's sheets.

Account

TRMNLY's hosted Cred wallet. Sign in, top up a balance, see your usage. The session lives in the Keychain; signing out clears the local copy but leaves your account intact.

Notifications

Quiet hours, long-running command toasts, and tab-monitor rules.

Updates

  • Stable — releases from the main branch only.
  • Beta (tip) — pre-release builds; cuts more often and rolls back less.
  • Auto-update mode — Off / Check and notify / Download and install.

Check for Updates Now shows its answer under the button — up to date, an update with Install Update, or the error.

A release build checks daily, downloads in the background, and installs on quit. A licence whose year of updates has ended is offered only versions released inside it — see Updates. Debug and ReleaseLocal builds never self-update, and on a time-limited test build this whole pane is disabled — see Updates.

Profiles

Named snapshots of your overrides (theme, font size, keybindings, update prefs, agent model) you can capture and swap as a unit — e.g. "work" vs "personal".

Security

  • Scripting consent — per-source enable / confirm-every-command / rate-limit for external scripting surfaces
  • Agent network egress — Open vs Allowlist mode for the agent's web_fetch; loopback and private addresses are always blocked
  • Audit log — append every tool call to a log file on disk
  • Diagnostics — keep crash & hang diagnostics
  • Plugin permissions — per-plugin bridge grants
  • Update channel — shows the pinned feed URL and signing key

See Agent safety for the full agent-side enforcement surface.

Permissions

OS-level privacy grants TRMNLY needs: Accessibility, Automation (Apple Events), Microphone, Notifications, Screen Recording, Full Disk Access. Each row shows a status pill, requests the grant in-app where supported, and deep-links to System Settings otherwise.

Plugins

Listed under the Plugins right-sidebar tab rather than Settings — see Plugins.

Export / Import

File → Export TRMNLY Settings… writes a JSON bundle containing saved prompts, projects, agent preferences, and (optionally) agent sessions and runbooks. Before writing, TRMNLY scans the bundle for key-shaped strings and asks whether to export redacted (the default), export raw, or cancel.

File → Import TRMNLY Settings… reads a bundle and applies it after a diff-style confirmation sheet.

API keys are deliberately not part of the bundle.

Sync

There is no live cross-Mac sync today — Sync uses the same Export/Import bundle. Put the bundle in iCloud Drive / Dropbox to round-trip between machines. See Sync.