Configuration

Configuration lives in ~/.config/infiniterm/, four files in two pairs:

settings.json              yours, only what you changed
settings.default.json      every setting with its default, commented
keybindings.json           yours, only what you rebound
keybindings.default.json   every binding, commented

The .default files are rewritten at every launch, so editing them does nothing. Read them to see what exists, copy a line into your file and change it there. An upgrade never touches your files; new settings appear in the defaults.

Cmd , opens settings and Cmd Shift , keybindings, each as a pair of editor cards. Changes apply on save, no restart.

Settings

Keys are flat and dotted, so an override is one line:

{
  "terminal.fontSize": 16,
  "ui.showFps": true
}

Comments and trailing commas are allowed. Every setting is on the settings reference.

Keybindings

{
  "cmd+shift+k": "card.clear",
  "cmd+k": null
}

A binding set to null is removed, which gives the key back to the terminal. Every chord must hold cmd, with two exceptions: ctrl plus a digit, and ctrl+tab. A terminal needs Ctrl, Alt and bare keys for itself, but Ctrl plus a digit mostly means nothing to a shell. (On an xterm-compatible terminal Ctrl 3 sends Escape; if you live in vim, rebind it.)

Chords follow the physical key, not the character your layout prints on it, so cmd+= is the key right of - on every keyboard. Cmd H, Cmd M and Cmd Q belong to the menu and cannot be rebound. Every command id is on the commands reference.

Themes

All 500-odd schemes from iTerm2-Color-Schemes ship with the app; Catppuccin Mocha is the default. Your own .itermcolors files go in:

~/Library/Application Support/dev.ekinertac.infiniterm/themes/

“Switch theme” in the palette applies each scheme as you move through the list. Escape puts back the one you started on; Enter keeps the new one. The theme colours the app’s chrome, the editor’s syntax and the card labels too.

Snippets

Cmd Ctrl S lists your snippets and pastes the one you pick into the focused card, the same way Cmd V would, so Claude takes a multi-line prompt as one block.

Snippets are plain files in ~/.config/infiniterm/snippets/, one per snippet. The file name without its extension is the snippet’s name; the contents are pasted as written, less one trailing line break. The picker’s last row opens the folder.

What the app touches

• Your shells, one per card, started as your login shell with INFINITERM_CARD_ID in the environment. Nothing is typed into them that you did not type.
• ~/.config/infiniterm/ for settings, keybindings and snippets, and ~/Library/Application Support/dev.ekinertac.infiniterm/ for the canvas, drafts, themes, the window frame, agent.log, the browser profile and address-bar history. Deleting workspace.json there resets the canvas and leaves your settings alone.
• ps, lsof and git as subprocesses, to label cards and for the diff and blame cards.
• The network only from browser cards, the update check, and address-bar suggestions from Google, which are off unless you turn on browser.suggestions.

No account, no telemetry.