Terminal and CLI Power-User Shortcuts

Terminal shortcuts are unusual compared to most of what's on this site because a large share of them come not from the terminal application itself but from the underlying shell and its line-editing library — most commonly Readline (used by bash and, via a compatible layer, by many other shells) or a comparable system. That means a big chunk of what makes someone fast in a terminal transfers across different terminal apps and even across operating systems, which isn't true of most other software categories covered here.

Line editing: the shortcuts that matter more than arrow keys

Ctrl+A moves the cursor to the start of the current line, and Ctrl+E moves it to the end — direct terminal equivalents of Home and End, and considerably faster to reach for than moving your hand to dedicated navigation keys, since your fingers are already resting near Ctrl. Ctrl+U clears the line from the cursor back to the start, and Ctrl+K clears from the cursor to the end — both far faster than holding Backspace or Delete to clear a long, mistyped command.

Ctrl+W deletes the word immediately before the cursor — used constantly for correcting a single mistyped argument without retyping an entire long command. Alt+B and Alt+F (Option+B/F on Mac) move the cursor backward and forward one word at a time, mirroring the word-jump behavior found in most text editors. Together, these five or six shortcuts eliminate almost all of the need to reach for arrow keys or Backspace repeatedly when editing a command before running it.

History search: the single highest-leverage terminal shortcut

Ctrl+R opens reverse incremental search through your command history — start typing any part of a command you've run before, and it jumps to the most recent match, live, as you type. Pressing Ctrl+R again cycles further back through matches. This is, without much competition, the single most valuable terminal shortcut that exists, because it means you almost never need to retype a complex command you've already figured out once — you just search for a fragment of it. Anyone who scrolls through terminal history with the Up arrow key repeatedly, one command at a time, is doing by hand what Ctrl+R does instantly.

Process control: stopping and backgrounding

Ctrl+C sends an interrupt signal to the currently running foreground process — the standard way to stop a runaway command, a stuck build, or a server you want to shut down. Ctrl+Z suspends the current foreground process and returns you to the shell prompt without killing it, and the `fg` command (typed afterward) resumes it in the foreground again — useful for briefly stepping away from a long-running interactive process to run a quick unrelated command, then returning to exactly where you left off.

Tab completion: use it more aggressively than you probably do

Tab completes the current file, directory, or command name, and most modern shells extend this to complete command flags, git branch names, and other context-aware suggestions if configured with completion scripts. Pressing Tab twice, when a completion is ambiguous, lists every possible match instead of doing nothing — a genuinely underused habit, since most people abandon a partial Tab completion and start typing manually rather than double-tapping Tab to see their options.

Clearing the screen without losing your place

Ctrl+L clears the visible terminal screen without clearing your command history or losing any running process — functionally similar to typing `clear` and pressing Enter, but instant and without needing to type a command at all. This matters more than it sounds like it should for anyone running a long series of commands where visual clutter starts to make it hard to see recent output.

Where terminal apps add their own layer on top

Everything above comes from the shell's line-editing layer and works close to identically whether you're in Windows Terminal, iTerm2, or a plain default terminal app. On top of that shared foundation, individual terminal applications add their own shortcuts for tab and pane management. iTerm2, popular on Mac, has an extensive set for split panes (Cmd+D for vertical split, Cmd+Shift+D for horizontal) and broadcasting input to multiple panes simultaneously — genuinely useful for running the same command across several servers or environments at once. Warp Terminal takes this further with its own command-palette-driven shortcut set and AI-assisted command features layered on top of the same underlying shell conventions.

If you're on Windows and using PowerShell

PowerShell supports a broadly similar set of Readline-style line-editing shortcuts through its PSReadLine module, including Ctrl+R-style history search, though the default keybindings differ slightly from bash's defaults out of the box — worth checking explicitly rather than assuming full parity if you're moving between a Mac/Linux shell and PowerShell regularly.

For a genuinely different keyboard-first paradigm: vim

If your terminal work extends into text editing inside the terminal itself, vim's modal editing system is worth understanding on its own terms — it's a fundamentally different interaction model from the line-editing shortcuts above, built around switching between distinct modes (normal, insert, visual) rather than holding modifier keys, and it rewards a completely separate deliberate-practice investment. Interestingly, VS Code's own shortcut philosophy (covered in the VS Code deep-dive post) borrows some of vim's efficiency ideas around multi-cursor and multi-selection editing, even though it uses a conventional modifier-key model rather than vim's modal one.

Command-line tools that extend the same philosophy

The same 'fast, keyboard-first, minimal mouse' philosophy that makes a shell genuinely productive extends to specialized command-line tools built on top of it — httpie, a popular command-line HTTP client, follows the same terminal conventions covered above (history search, line editing) while adding its own syntax for constructing requests quickly, worth knowing if you find yourself testing APIs from the terminal rather than reaching for a GUI tool like Postman for quick one-off checks.

Getting these into muscle memory

Terminal shortcuts reward deliberate practice more than almost any other category on this site, because a huge fraction of terminal usage is repetitive command editing and history recall — exactly the kind of high-frequency action where automaticity pays off fastest. Ctrl+R alone, drilled until it's a reflex rather than a fallback, will change how you use a terminal more than any other single shortcut covered here.