Ghostty 1.4.0, released October 27, 2026, changes selection-copy behavior. On macOS, copy-on-select now defaults to none. The official migration note says copy-on-select = primary restores the 1.3 selection behavior. An explicit true on macOS now targets the system clipboard instead, so it is not the same restoration.
Choose copying and pasting separately
The release accepts none, primary, clipboard and both for copy-on-select. The clipboard value now targets only the system clipboard; users wanting its previous dual-copy behavior should choose both. Separately, middle-click-action offers primary-paste, clipboard-paste or ignore, with primary-paste the default. These are documented settings, not results of our own application test.
Primary source: Ghostty 1.4.0 release notes, Breaking Changes and Full Changelog
Test the destination with disposable text
Before editing your configuration, save a copy and write down the behavior you want: selecting a word should copy somewhere, a copy shortcut should copy somewhere, or middle-click should paste from somewhere. Treat these as three separate expectations. This makes a surprising result easier to describe.
For a small proposed test, put the harmless word APRICOT in the system clipboard using a text editor. Display another harmless word, BLUEBELL, in your terminal and select it. Paste into the editor using its normal paste command, then record which word appears. Use no passwords or important clipboard contents during this exercise.
Check middle-click separately in a disposable editing area. Record the observed result beside the relevant setting rather than assuming it follows the copy shortcut. If your mouse or environment does not provide a middle-click action, mark that part untested.
Change one intention at a time
Compare the current configuration with your saved copy. Select a setting for the destination you actually want, apply the change through your normal configuration workflow and repeat the same small exercise. Avoid combining unrelated keybinding, theme and clipboard changes while diagnosing one behavior.
For a team migration note, include the application version, operating system, explicit setting and expected result. Keep observed behavior separate from documentation. A colleague should be able to tell whether a statement comes from the release notes or from a test on your particular machine.
Selection and paste check
