All pages
Lesson 8.1 · Make it yours · 10 min
Settings and sync
The Settings window, your Ghostty config, and moving to a new Mac.
After this lesson, you can find any setting quickly and understand how Settings relates to your Ghostty config file. You'll also be able to move your prompts, projects and agent preferences to another Mac.
Time: 10 minutes · Works on: macOS app
Open Settings and search it
- Press
⌘,, or choose TRMNLY → Settings… from the menu bar. - Type into the search bar at the top, for example "font size" or "MCP". The matching setting is highlighted in its tab.
The tabs are General, Account, Appearance, Font, Keybindings, Shortcuts, Integrations, API Keys, AI Agent, Notifications, Updates, Profiles, Security and Permissions. A few more cover single features: Containers, VibeHub and TestFlight.
Settings never rewrite your config file
TRMNLY is built on Ghostty, which reads a plain-text config file. TRMNLY doesn't edit that file. When you change something in Settings, TRMNLY writes it to a separate override file that loads after your config, so the Settings value wins. Reset a setting to its default and its line drops out of the override file.
This keeps your config file clean enough to keep in version control. Settings changes also survive a config reload.
- Choose TRMNLY → Open Config File… to see your own config.
- Change the theme in Settings → Appearance. The windows update straight away, and your config file stays the same.
- After a hand edit to the config, choose TRMNLY → Reload Configuration.
The tabs you'll use most
- Appearance has the theme picker with a live preview, light or dark chrome, UI density, ligatures and the cursor.
- Font sets the default font size, and a size per project.
- Keybindings rebinds TRMNLY's built-in actions. Press Record on a row, then press the new chord.
- Shortcuts creates new chords that send text, run a saved prompt or runbook, or take a screenshot. Custom shortcuts covers it.
- API Keys holds your model provider keys, in the macOS Keychain.
- Integrations lists every service TRMNLY holds a key for, with its status. Verify asks one service whether its key still works. Verify all checks every one. Nothing is checked in the background unless you ask.
- AI Agent covers agent behavior, the MCP server, remote control, the network allowlist and the filesystem sandbox.
- Updates picks the channel, Stable or Beta (tip), and the auto-update mode: Off, Check and notify, or Download and install.
- Permissions shows each macOS privacy grant TRMNLY uses, with its status and a button to request or open it.
Tip: Integrations separates a key the service refused from a service that never answered. Don't replace a key just because a service was unreachable.
Save sets of settings as profiles
Profiles stores named snapshots of your overrides: theme, font size, keybindings, update settings and agent preferences. Use one for screen sharing with a large font and a light theme, and another for everyday work.
- Set things up the way you want, then open Settings → Profiles.
- Type a name such as "Work" and press Save as Profile.
- Later, press Apply on a profile to switch everything back to it at once. Update from current settings saves your changes into an existing profile.
Move to another Mac
There's no live sync between Macs. Instead you export a bundle file and import it on the other machine.
- Choose TRMNLY → Export TRMNLY Settings….
- In the save panel, decide on Include agent sessions and runbooks. Leave it off for a small file with prompts, projects and agent preferences.
- Save. If TRMNLY finds anything that looks like a key or token in the bundle, it asks first. Export redacted is the default and replaces each finding with a placeholder. Export raw (unsafe) writes it as it is.
- Move the file to the other Mac with AirDrop, iCloud Drive or Dropbox.
- On the other Mac, choose TRMNLY → Import TRMNLY Settings… and pick the file.
- If anything differs, a resolver opens. Pick local or incoming for each setting. For prompts, projects, sessions and runbooks, you can keep local, use incoming, or Merge by id (newest wins). Keep all local and Use all incoming settle everything at once.
API keys are never in the bundle, because they live in the Keychain. Theme, font and keybinding overrides stay on each Mac too. Connections, tab-monitor rules and plugins don't travel in the bundle.
Importing the same bundle twice doesn't duplicate anything, because prompts and projects merge by id.
Check yourself
- Search Settings for "ligature" and land on the toggle.
- Change the theme, then open your config file and confirm it didn't change.
- Export a bundle with Include agent sessions and runbooks off, and see that your API keys aren't in it.