This article was drafted with AI and edited by a human (me), but every tool listed here is one I actually use daily. They all come from my shell history.
AI coding is here to stay, and I love it. But as John Naughton wrote in the Guardian, you may no longer need code to be a programmer, you still need expertise. A good part of that expertise is unglamorous: knowing your way around a terminal. Like a handyman who keeps a screwdriver next to their power tools, every developer needs command-line fundamentals. Pipes, files and text streams have lasted decades because they are composable and universal.
They are also what LLMs rely on: the terminal is the oldest tool-use interface we have, and Rémi Louf’s talk AI needs its Unix moment even argues for treating LLMs as command-line tools, a path I find promising. A house still needs solid foundations, and those are the modern CLI. I assume that is why OpenAI acquired Astral, the company behind uv and Ruff, to build the tooling around Codex.
Here are the tools that make my workflow smoother, with Claude Code at the end.
Terminal emulators
- iTerm2: I switched from the default Terminal.app years ago and never looked back. Split panes, search, autocomplete. It does everything you need without being fancy about it.
Shell and prompt
- Zsh: the default on macOS since Catalina, so you might already be using it. I pair it with Oh My Zsh for plugins, though the lighter zinit is worth a look if you find Oh My Zsh too heavy.
- Starship: my prompt. It shows git status, language versions, and cloud context right in the prompt line. Works across shells and you barely need to configure it.
- Zoxide: probably the tool with the best effort-to-reward ratio on this list. It learns your most-used directories so you can type
z bloginstead ofcd ~/Documents/projects/my-blog.
Modern replacements for classic tools
There is a whole wave of Rust and Go rewrites of classic Unix tools with better defaults and colour output. I still type plain ls, cat, and grep out of muscle memory. I do use The Silver Searcher (ag) for code search, which is already a big step up from grep. The rest are on my list to try.
| Classic | Modern replacement | Why |
|---|---|---|
ls | eza | Colour, icons, git status, tree view |
cat | bat | Syntax highlighting, git integration, paging |
find | fd | Simpler syntax, respects .gitignore, faster |
grep | ripgrep (rg) | Much faster, smart defaults, .gitignore aware |
du | dust | Visual directory size breakdown |
top | btop | Beautiful resource monitor with mouse support |
sed | sd | Simpler regex syntax, string literal mode |
diff | delta | Syntax highlighting, side-by-side view, git integration |
curl | xh | Coloured output, simpler syntax for JSON APIs |
man | tldr | Community-maintained cheat sheets with practical examples |
If you want to try these without changing your habits, alias them so your muscle memory keeps working:
alias ls="eza --icons --group-directories-first"
alias cat="bat --style=auto"
alias find="fd"
alias grep="rg --smart-case"
alias du="dust -r"
alias top="btop"
alias sed="sd"
alias diff="delta --side-by-side"
alias curl="xh"
alias man="tldr"
File navigation
- fzf: hard to explain until you try it. It is a fuzzy finder: you pipe anything into it and get an interactive selector. It gets interesting once you compose it with other tools,
rg "pattern" | fzfto search code interactively, orgit log --oneline | fzfto pick a commit. Once installed it also gives youctrl+tfor file search andctrl+rfor a much better history search.
Multiplexing
- tmux: the classic terminal multiplexer, and another tool that has survived the test of time. I use it mostly to keep dev servers running in the background while working in another pane. Persistent sessions mean you can disconnect and come back later without losing anything. Pair it with tpm for plugins.
Developer utilities
- jq: if you work with JSON (and you probably do), this is essential. The query syntax takes a bit of learning, but it pays off fast. For a gentler start, try jnv, which gives you a live preview as you build your query.
- lazygit: I have this aliased to
lgand I open it before almost every commit. It makes rebasing, staging individual hunks, and resolving conflicts much less painful than raw git commands. If git’s CLI intimidates you, start here. - Fork: I use this alongside lazygit.
fork .opens the current repo in a clean native GUI, which is useful when you need to visualise branch history or understand the big picture across branches. - lazydocker: same idea as lazygit but for Docker. View logs, restart containers, manage volumes, all from one TUI.
- tectonic: if you use LaTeX, this saves a lot of pain. It downloads packages on demand, no manual
tlmgrsetup.tectonic document.texjust works.
SSH config
This one is a config trick, and it saves me time every day. Instead of typing ssh -i ~/.ssh/key user@long-hostname.example.com -p 2222, you can define short aliases in ~/.ssh/config:
Host dev
HostName my-server.example.com
User deploy
Port 2222
IdentityFile ~/.ssh/my_key
Then just ssh dev. Six characters instead of sixty. It also works with scp, rsync, and VS Code remote.
AI in the terminal
- Claude Code: a CLI to use Claude for coding. It is the tool that prompted me to write this article.
Learning resources
- The Art of Command Line: a long guide that I revisit from time to time. Covers everything from basic navigation to tricks I had never thought of.
- Modern Unix: where I discovered most of the tools in the table above.
- Julia Evans’ zines: the best way I know to build intuition about how networking, bash, git, and DNS actually work. Short and illustrated, and deeper than they look.
- Command Line Interface Guidelines: if you are building CLI tools yourself, this is the style guide to follow.
Install everything on macOS
Most of these are available via Homebrew. Here is a single script to install them all:
#!/bin/bash
set -e
# Check for Homebrew
if ! command -v brew &> /dev/null; then
echo "Installing Homebrew..."
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
fi
# Terminal emulator
brew install --cask iterm2
# Shell and prompt
brew install starship zoxide atuin
# Modern replacements
brew install eza bat fd ripgrep dust btop sd git-delta xh tldr the_silver_searcher
# File navigation
brew install fzf yazi
$(brew --prefix)/opt/fzf/install --key-bindings --completion --no-update-rc
# Multiplexing
brew install tmux
# Developer utilities
brew install jq lazygit lazydocker tectonic
brew install --cask fork
# AI
brew install claude-code
echo ""
echo "Done! Add the following to your ~/.zshrc:"
echo ""
echo '# Starship prompt'
echo 'eval "$(starship init zsh)"'
echo ""
echo '# Zoxide'
echo 'eval "$(zoxide init zsh)"'
echo ""
echo '# Atuin'
echo 'eval "$(atuin init zsh)"'
echo ""
echo '# Modern tool aliases'
echo 'alias ls="eza --icons --group-directories-first"'
echo 'alias cat="bat --style=auto"'
echo 'alias find="fd"'
echo 'alias grep="rg --smart-case"'
echo 'alias du="dust -r"'
echo 'alias top="btop"'
echo 'alias sed="sd"'
echo 'alias diff="delta --side-by-side"'
echo 'alias curl="xh"'
echo 'alias man="tldr"'
echo 'alias lg="lazygit"'
Save this as install-cli-tools.sh, run chmod +x install-cli-tools.sh, and execute it. If you already have some of these installed, Homebrew will skip them.
This list reflects what I actually use. I will update it as I find new tools worth adding.