Skip to main content

​
Opening

⌘F opens and closes search for the active pane.
Also via right-click in the terminal → Search in terminal. The box appears in the pane’s top-right corner. The search belongs to the pane — each terminal has its own history, and search only sees that one. The ▲ ▼ arrows in the box do the same as ⇧↵ and ↵. As you type, TYBA already marks the first result — no need to press Enter to see where it hit.

​
The counter

To the right of the field: Results are painted with your theme’s colors: every match gets one marking, and the active one another. Change the theme and search changes with it.

​
It comes pre-filled

If you had something selected when you opened search, the query starts with that text — already selected in the field, ready to be replaced if it isn’t what you wanted.
This only applies to single-line selections. A selection with a line break pre-fills nothing: search is for running text, and a three-line query would never find anything.
The flow this unlocks: you spot a commit hash, a request ID or a filename in the output, double-click it, ⌘F, ↵ — and you’re walking through every other time it appeared.

​
The 10,000-line limit

The terminal keeps 10,000 lines of scrollback. Fixed.
Whatever went past those 10,000 lines doesn’t exist anymore. Search doesn’t find it because there’s nothing to find — the line was discarded when the 10,001st arrived.
This isn’t a number you can raise: there’s no field in Settings, no hidden preference, no file to edit. A cat of a huge log, a verbose build, an agent dumping a diff — any of them pushes out whatever was there before. If what you need to find is half an hour and a thousand commands back, the place to look isn’t the terminal’s search — it’s the file, the log or git.

​
What search doesn’t see

​
See also

Using the terminal

Selecting and copying — what feeds search.

Shortcuts

Where to remap ⌘F.