14 Best CLI Tools for Developers in 2026 (Mac, Linux, Windows)

Tested picks: ripgrep, fzf, bat, eza, fd, zoxide, jq, tmux, lazygit, and more, with install commands for macOS, Linux, and Windows.

John Sonmez John Sonmez Updated October 8, 2026 16 min read
14 Best CLI Tools for Developers in 2026 (Mac, Linux, Windows)

Most developers spend hours every week in the terminal, running tools that still work the way they did in the 1970s.

The CLI ecosystem has grown a whole second layer of tools that are faster and friendlier than the Unix utilities everyone defaults to. They save real time on tasks you repeat dozens of times a day, and most install in one line on macOS, Linux, or Windows.

I've tested hundreds of these tools. The 14 below are the ones I actually use, the ones that changed how I work day to day. Some replace slow defaults with blazing-fast alternatives. Others add features that should've existed decades ago.

Quick Picks: The Best CLI Tools by Developer Workflow

The best terminal tools depend on the job you're trying to make faster. A frontend developer drowning in files needs fd, fzf, and ripgrep. A backend developer staring at logs and API payloads needs jq, bat, and httpie. A senior engineer moving between projects all day probably gets the biggest daily win from zoxide, tmux, and lazygit.

Workflow Best CLI Tools Why It Helps
Code search ripgrep, fd, fzf Find files and symbols without waiting on slow default commands.
Reading files bat, tldr Scan code and command examples faster than plain cat or dense man pages.
Git workflows lazygit, delta, eza Review diffs, branches, and file status with less mental friction.
API and JSON work jq, httpie Inspect responses, filter payloads, and debug requests from the terminal.
Project navigation zoxide, tmux Jump between repos, panes, shells, and servers without breaking flow.

That matters because terminal productivity is not about collecting shiny tools. It is about removing the tiny pauses that stack up every day: waiting for search, typing long paths, copying JSON into a browser formatter, or losing context when you switch projects. The right command line tools make those pauses disappear.

What makes a tool worth your terminal's real estate

I re-checked every tool below against its project page in October 2026. Twelve of the 14 are still under active development. Two have stalled, ncdu and HTTPie, and I flag both in their sections so you know what you're installing.

A graphical file manager or text editor is fine until you need to script a repetitive task or run it over SSH on a box with no display. A command-line interface is built for exactly that: automation, piping output between programs, and working the same way whether you're local or on a remote server. Most of these install through a package manager (Homebrew, apt, or winget), so setup is one line, not a download page.

GitHub stars, selected CLI tools Source: GitHub, October 8, 2026
  • fzf83.4K
  • lazygit83.0K
  • ripgrep68.9K
  • tldr-pages63.8K
  • bat60.7K
  • tmux49.8K
  • zoxide40.0K

How I picked this list

This is a curated list for macOS, Linux, and Windows (native or WSL) developers who want a new generation of CLI tools that feel ergonomic, configurable, and ready for real software work.

I skipped novelty apps like a terminal-based music player and focused on each utility I would actually bookmark, install, and teach to another developer. Some have plugins or theming. Some are plain binaries. The test is simple: does it give you better output, save learning time, or automate something you currently do by hand?

The right command line tools make those pauses disappear.

jq lets you map and transform JSON data without opening a web UI. fzf adds fuzzy search so you can quickly jump through files and directories instead of memorizing names. lazygit is a terminal git client that makes git commits, squash operations, and branch cleanup feel less painful, and htop is still a solid resource monitor.

If your work touches Kubernetes, Docker, Python scripts, Vim, Zsh, or clipboard-heavy shell workflows, these tools scale with you without turning your terminal into a second code editor you never asked for.

1. ripgrep (rg)

Ripgrep is a line-oriented search tool that recursively searches your current directory for a regex pattern. It's basically grep, but orders of magnitude faster.

I switched to ripgrep three years ago and never looked back. It respects your .gitignore by default, which means it doesn't waste time searching node_modules or build directories. It's written in Rust, and the performance difference on large codebases is staggering. Searching through a multi-million-line codebase that took 30 seconds with grep takes 2 seconds with ripgrep.

Best for: Anyone who searches code. If you use grep or ack, stop. Use this instead. It's still under active development, with release 15.2.0 shipping in July 2026 and 68.9K GitHub stars as of October 2026.

Install: brew install ripgrep (macOS) · apt install ripgrep (Debian/Ubuntu) · winget install BurntSushi.ripgrep.MSVC or scoop install ripgrep (Windows)

Link: github.com/BurntSushi/ripgrep

Pro tip: Put --hidden and --smart-case in a config file and point RIPGREP_CONFIG_PATH at it, so every rg search uses them by default.

2. fzf

Fzf is a command-line fuzzy finder. You pipe any list of items to it, and it gives you an interactive filter to narrow down the results in real time.

This one changed how I work with Git, command history, and file search. Instead of typing exact paths or remembering commit hashes, you type a few characters and fzf narrows down the options instantly. I use it dozens of times a day without thinking about it. It integrates with your shell history (Ctrl+R becomes actually useful), file searches, and basically anything that returns a list.

Best for: Developers who want to stop typing full paths and exact commands. It's the most-starred tool on this list, at 83.4K GitHub stars as of October 2026, and its creator shipped a new release in September 2026.

Install: brew install fzf (macOS) · apt install fzf (Debian/Ubuntu) · winget install junegunn.fzf or scoop install fzf (Windows)

Link: github.com/junegunn/fzf

Pro tip: Bind it to Ctrl+T for fuzzy file finding and Ctrl+R for command history. Your muscle memory will thank you.

3. bat

Bat is cat with syntax highlighting, Git integration, and automatic paging. It shows line numbers, highlights changes, and renders code with proper color schemes.

Honestly, I was skeptical when I first tried this. "Syntax highlighting in the terminal? That's overkill." Then I used it for a week and realized how much faster I could scan files. When you're reading code in the terminal, the syntax highlighting makes patterns jump out instantly. Plus, it automatically pages long files so you don't accidentally dump thousands of lines into your scrollback.

Best for: Anyone who uses cat to read files. Replace it with this. The README now lists four maintainers, and the repo sits at 60.7K GitHub stars as of October 2026.

Install: brew install bat (macOS) · apt install bat (Debian/Ubuntu; binary installs as batcat) · winget install sharkdp.bat or scoop install bat (Windows)

Link: github.com/sharkdp/bat

Pro tip: Alias cat to bat --paging=never for short files, or use bat directly for longer ones.

4. eza (the exa replacement)

Eza is a modern replacement for ls. It has better defaults, Git integration, tree views, and color schemes that actually make sense.

The original exa hasn't shipped a release since April 2021, and its maintainer confirmed in 2023 that it's done; the project's own notes now point people to eza instead. Eza picked up the torch and kept moving: better theming, hyperlink support, and more accurate --git output.

The reason I switched still holds. When you list files in a Git repo, eza shows you which files are modified, staged, or ignored right in the output, so you stop reaching for a separate git status.

Best for: Developers who work with Git repos and want richer file listings. Don't install plain exa from an old tutorial. It's frozen in 2021 and will drift out of sync with your shell.

Install: brew install eza (macOS) · apt install eza (Debian 13+/Ubuntu 24.04+) · winget install eza-community.eza or scoop install eza (Windows)

Link: github.com/eza-community/eza

Pro tip: Alias ls to eza --git --icons and ll to eza -l --git --icons.

5. fd

Fd is a fast, user-friendly alternative to find. It has sane defaults, intuitive syntax, and respects .gitignore automatically.

The find command is powerful, but the syntax is a nightmare. Half the time I have to Google the exact flags to exclude directories or filter by file extension. Fd just works. Want to find all TypeScript files? fd -e ts. Want to search case-insensitively? That's the default. It's fast, it ignores files you don't care about, and the syntax is what find should have been from the start.

Best for: Anyone who's ever rage-quit trying to remember find syntax.

Install: brew install fd (macOS) · apt install fd-find (Debian/Ubuntu; binary installs as fdfind) · winget install sharkdp.fd or scoop install fd (Windows)

Link: github.com/sharkdp/fd

Pro tip: Combine it with fzf for interactive file finding: fd | fzf.

6. zoxide

Zoxide is a smarter cd. It tracks which directories you visit and lets you jump to them with partial matches.

Instead of typing cd ~/projects/work/api-gateway, you just type z api and you're there. It learns your patterns and ranks directories by frequency and recency. After a day of use, you'll forget how you ever navigated without it. I used to have aliases for all my common directories. Now I just type a few letters and zoxide figures out where I want to go.

Best for: Developers who navigate deep directory trees constantly. It shipped 0.10.0 in July 2026 and has 40.0K GitHub stars as of October 2026.

Install: brew install zoxide (macOS) · apt install zoxide (Debian/Ubuntu) · winget install ajeetdsouza.zoxide or scoop install zoxide (Windows)

Link: github.com/ajeetdsouza/zoxide

Pro tip: Alias cd to z so you can't accidentally go back to the old way.

A slick terminal shaves seconds off your day. It won't make your industry know your name. Now that AI ships the same code for everyone, the developer who gets the job and the raise is the one people already know. That's the whole point of the free 5-day Rockstar Engineer Blueprint from John Sonmez. Become the developer your industry knows by name, so the best jobs and offers come looking for you.

Get the Free Course

7. tldr

Tldr provides simplified, example-focused help pages for command-line tools. It's like man pages, but actually useful.

Man pages are comprehensive. They're also dense, overwhelming, and written for people who already know what they're doing. Tldr gives you practical examples instead. Need to use tar? Instead of scrolling through 500 lines of documentation, tldr shows you the five most common use cases with actual commands you can copy. It's community-maintained and covers thousands of commands. I still use man pages for deep dives, but tldr is my first stop for 90% of lookups.

Best for: Anyone who's sick of Googling basic command syntax. The page collection has 63.8K GitHub stars as of October 2026. I run it through tealdeer, a fast Rust client.

Install: brew install tealdeer (macOS) · apt install tealdeer (Debian 12+/Ubuntu 24.04+) · winget install dbrgn.tealdeer or scoop install tealdeer (Windows)

Link: github.com/tldr-pages/tldr

Pro tip: Run tldr --update once after installing tealdeer so lookups are served from a local cache instead of a network call.

8. htop

Htop is an interactive process viewer. It's top, but with colors, sorting, filtering, and a UI that doesn't feel like it's from 1984.

This one's been around for years, but a lot of developers still default to top. Htop shows CPU and memory usage per core, lets you kill processes with F9, and makes it trivial to find which process is eating your RAM. It's not new or trendy, but if you haven't switched yet, you're wasting time.

Best for: Monitoring system resources without leaving the terminal.

Install: brew install htop (macOS) · apt install htop (Debian/Ubuntu) · Windows has no native build; run it inside WSL.

Link: htop.dev

Pro tip: Press F6 to sort by different columns (CPU, MEM, TIME). Press / to search for processes.

9. jq

Jq is a lightweight command-line JSON processor. It lets you slice, filter, map, and transform JSON with a concise query language.

If you work with APIs, you've needed this and maybe didn't know it existed. Instead of piping API responses to a file and opening them in an editor, you can parse, filter, and extract exactly what you need right in the terminal. Want the first five user IDs from an API response? curl api.example.com/users | jq '.[:5] | .[].id'. The syntax has a learning curve, but once you get the basics, it's indispensable.

Best for: Backend developers and anyone who debugs API responses. Jq moved to a community-run "jqlang" organization a few years back and shipped 1.8.2 in June 2026, so it's in healthier hands than the old single-maintainer days.

Install: brew install jq (macOS) · apt install jq (Debian/Ubuntu) · winget install jqlang.jq or scoop install jq (Windows)

Link: jqlang.org

Pro tip: Use jq -C | less -R to colorize and page large JSON outputs.

10. lazygit

Lazygit is a terminal UI for Git, written in Go. It gives you an interactive interface for staging, committing, branching, rebasing, and resolving conflicts without memorizing a hundred flags.

I'm good with Git from the raw command line. I know the commands. But lazygit makes the common workflows so much faster that I reach for it by default now. Staging individual hunks is one keypress, and viewing a file diff before you review a pull request is right there.

Rebasing interactively gives you a visual list you can reorder with arrow keys instead of editing a text file by hand. It's not a crutch. It's an interface that respects your time, and the keybindings are easy to customize if the defaults don't fit your muscle memory.

Best for: Developers who use Git every day and want to stop Googling rebase flags. It's grown to 83.0K GitHub stars as of October 2026, second only to fzf on this list.

Install: brew install lazygit (macOS) · apt install lazygit (Debian 13+/Ubuntu 25.10+, or grab the release binary) · winget install JesseDuffield.lazygit or scoop install lazygit (Windows)

Link: github.com/jesseduffield/lazygit

Pro tip: Bind it to an alias like lg. You'll use it constantly.

11. delta

Delta is a syntax-highlighting pager for Git diffs. It makes Git diff output readable with side-by-side views, better colors, and syntax highlighting.

The default Git diff is functional, but it's hard to scan. Delta turns it into something you can actually read quickly. It highlights word-level changes instead of just line-level, which makes it way easier to spot what actually changed in a line. It also integrates with lazygit and other Git tools, so once you install it, everything that shows diffs gets better.

Best for: Developers who review code or diffs in the terminal. Releases keep shipping: 0.20.1 landed in October 2026.

Install: brew install git-delta (macOS) · apt install git-delta (Debian 13+/Ubuntu 24.04+) · winget install dandavison.delta or scoop install delta (Windows)

Link: github.com/dandavison/delta

Pro tip: Add it to your .gitconfig as the default pager: git config --global core.pager delta.

12. ncdu

Ncdu is a disk usage analyzer with an ncurses interface. It scans directories and shows you what's eating your disk space, with the ability to drill down and delete files interactively.

When your disk fills up, du and df tell you almost nothing useful. Ncdu scans your filesystem, shows you the biggest directories at the top, and lets you navigate into them to find what's hogging space. I've used it to find forgotten Docker images, old log files, and node_modules folders I didn't know existed. It's saved me hours of hunting through random directories.

Best for: Developers who need to free up disk space without guessing.

Install: brew install ncdu (macOS) · apt install ncdu (Debian/Ubuntu) · Windows has no native build; run it inside WSL, or use winget install bootandy.dust for a Windows-native alternative.

Link: dev.yorhel.nl/ncdu

Pro tip: Run ncdu / with sudo to scan your entire system. Press 'd' to delete files directly from the interface.

13. httpie

HTTPie is a user-friendly HTTP client. It's like curl, but with syntax that makes sense and output that's actually readable.

Curl is powerful, but the syntax is arcane and the output is ugly. HTTPie uses intuitive syntax (http POST api.example.com name=value), automatically formats JSON, and colorizes output. For quick API testing, it's way faster than curl and way lighter than Postman. I still use curl for scripts, but for interactive debugging, HTTPie wins.

Best for: Developers who test APIs from the command line. It still has 38.7K GitHub stars, but the CLI hasn't shipped a release since 3.2.4 in November 2024.

Install: pip install httpie (macOS, Linux, Windows; the official cross-platform method) or brew install httpie on macOS.

Link: httpie.io

Pro tip: Use --session to save cookies and headers between requests when testing authenticated APIs.

14. tmux (or Zellij)

Tmux is a terminal multiplexer, not a terminal emulator. It runs inside whatever terminal emulator you already use (Windows Terminal, iTerm2, Alacritty) and lets you split panes, detach and reattach sessions, and keep processes running after you disconnect.

If you work on remote servers or run long-running processes, you need this. It's the difference between losing all your work when your SSH connection drops and just reconnecting to exactly where you left off. Tmux remains the standard, with 49.8K GitHub stars and a 3.8 release in September 2026. Zellij is the newer alternative, at 35.7K stars, with friendlier defaults out of the box. Either one is fine. The important part is using a multiplexer at all.

Best for: Developers who work on remote servers or need persistent terminal sessions.

Install: brew install tmux (macOS) · apt install tmux (Linux). Neither tmux nor Zellij has a native Windows build; run either one inside WSL, or use Windows Terminal's own split panes for local-only work.

Link: github.com/tmux/tmux (tmux) or zellij.dev (Zellij)

Pro tip: Learn the basics: Ctrl+B % for vertical split, Ctrl+B " for horizontal split, Ctrl+B D to detach. That's 90% of what you need.

Bonus: AI CLI tools changing the terminal in 2026

The 14 tools above sharpen the terminal you already know. A newer category runs AI agents inside that same terminal and hands them your files, your shell, and your Git history, on any operating system. Three are worth knowing about.

  • Claude Code. Anthropic's agentic CLI. It reads and edits your files, runs Git, and connects to external tools through MCP. It needs a paid Claude plan or API account. Install with curl -fsSL https://claude.ai/install.sh | bash (macOS/Linux) or winget install Anthropic.ClaudeCode (Windows).
  • OpenAI Codex CLI. A Rust-based coding agent with sandboxed approval modes and MCP support. Install with npm install -g @openai/codex on any OS, or brew install --cask codex on macOS.
  • Gemini CLI. Google's open-source terminal agent, installed with npm install -g @google/gemini-cli. Worth a flag: as of June 18, 2026, Google cut off personal Google-account logins for free, Pro, and Ultra tiers, pushing individual users toward the closed-source Antigravity CLI instead. Gemini CLI still works with a Gemini API key, Vertex AI, or an enterprise Code Assist license.

None of these replace ripgrep or fzf. Claude Code's own docs list ripgrep as a dependency it bundles for search, so the skills above still matter. Think of this category as a new layer on top, not a swap.

The Bottom Line

You don't need all 14 of these. Start with the ones that solve problems you actually have. If you spend a lot of time searching code, get ripgrep. If you're constantly navigating directories, get zoxide. If you work with Git every day, get lazygit and delta.

The cumulative effect compounds past the few seconds any single tool saves you. Fast, intuitive tools free up attention for the actual problem instead of the mechanics of typing commands. That compounding is what pulls you into flow instead of grinding through a task.

Flow state helps you ship faster. It doesn't automatically get you promoted, and that takes a different kind of visibility. If you want that side of the equation, see how to get promoted as a software engineer.

Don't install them all at once. Pick two or three that address your biggest pain points, on whichever OS you run. Use them for a week. Then come back and grab a couple more. Within a month, your terminal workflow will feel completely different.

A sharper terminal makes you faster. It doesn't make you known. AI now writes the code every developer used to be paid for, so raw output is cheap. The developers who get the job, the raise, and the offer are the ones people know by name. That's what the 5 mistakes that keep good developers invisible and overlooked cost you. John Sonmez covers all of it in a free 5-day email course, and 150+ developers have already joined.

Get the Free Course