🚀 Awesome CLI: Command Line Tools You’ll Use Daily (And Never Want to Leave)
The terminal. For many, it’s a black box of intimidating commands. For power users, however, it’s the ultimate operating system—a lightning-fast, repeatable, and infinitely programmable extension of thought.
If you find yourself copying and pasting the same set of commands, manually navigating directories, or spending precious minutes searching through logs, it’s time to upgrade your tooling.
Welcome to the world of “Awesome CLI.” These aren’t just replacements for basic commands; they are productivity multipliers that transform tedious tasks into elegant, one-line solutions.
Ready to supercharge your workflow? Let’s dive into the essential command-line tools that every modern developer and power user needs in their arsenal.
📂 File System & Navigation Superpowers
Sometimes, the biggest time sinks are file operations and directory navigation. These tools offer smarter, safer ways to manage your digital life.
1. fd (Fast Discover)
The Problem: The standard find command is powerful but notoriously verbose, slow, and often requires complex filtering syntax.
The Solution: fd is a modern, fast alternative to find. It’s faster, uses intelligent defaults, and is designed for human readability.
🚀 Use Case: Find all JavaScript files named *controller.js in the current directory, ignoring the node_modules folder, with a single command.
“`bash
Example: Using ‘fd’ to find only .yaml files quickly
fd –extension=yaml ./configs
“`
2. exa (The Next-Gen ls)
The Problem: The basic ls command lacks modern features, making directory listings bland and uninformative.
The Solution: exa is a feature-rich replacement for ls. It offers beautiful, color-coded, and semantic output that makes understanding file types, permissions, and ownership instantaneous.
✨ Upgrade: It automatically colors file types (e.g., executables look different from images).
3. z (The History Genius)
The Problem: As your shell history grows, remembering the exact parameters of a past command can be a nightmare.
The Solution: The z command (often implemented via zsh’s powerful history features) allows you to search your command history with fuzzy matching. You can start typing a few letters and it will instantly suggest the command you intended, even if you misspelled it slightly.
⚡️ Benefit: It saves you from tedious re-typing and makes navigating past actions effortless.
🔬 Viewing, Searching, and Debugging
When you’re working with large logs, complex data, or gigabytes of code, brute force is not an option. You need surgical precision.
4. ripgrep (rg) (The Swiss Army Knife of Search)
The Problem: grep is the foundational search tool, but it can be slow, sometimes complex to use with modern file systems, and lacks advanced features like built-in regex optimization.
The Solution: ripgrep is a blazingly fast and highly optimized grep replacement. It searches recursively by default and respects .gitignore files, meaning it never wastes time searching code you’ve explicitly marked as ignorable.
🤯 Power: When you need to search millions of lines of code or massive log files instantly, ripgrep is the undisputed champion.
“`bash
Example: Search for the string ‘DatabaseConnection’ only in .rs files
rg “DatabaseConnection” –glob “*.rs”
“`
5. httpie (The Modern curl)
The Problem: curl is the workhorse of networking, but its syntax for making JSON requests can be verbose and unintuitive, especially when dealing with headers and complex bodies.
The Solution: httpie provides a vastly more user-friendly way to interact with APIs. It handles formatting, JSON bodies, and headers with minimal syntax.
🌐 Best For: Quickly testing API endpoints and interacting with services without needing to write a dedicated client script.
“`bash
Example: Sending a complex JSON payload with httpie
http POST example.com/api/user \
Content-Type: application/json \
Name: “Alice” \
Email: “alice@corp.com”
“`
6. btop / htop (The System Monitor)
The Problem: Standard system resource monitors can be difficult to read or require complex terminal setup.
The Solution: While htop is a classic, btop is the modern, visually superior replacement. It provides a beautiful, real-time dashboard view of CPU usage, memory consumption, and running processes, making system diagnosis intuitive and fast.
💼 Productivity & Workflows
These tools don’t perform a single task; they improve the experience of using your terminal itself.
7. Starship (The Universal Prompt)
The Problem: Your default shell prompt (user@host:~$) is functional, but it’s boring and offers no useful context (Git branch, current working directory, Python virtual environment).
The Solution: Starship is a customizable, fast, and universal prompt generator. It writes to multiple shells (Zsh, Bash, Fish, etc.) and instantly provides context-aware information:
* 🌐 Current Git branch status.
* 🐍 Active Python environment.
* ⌚ Time and date.
* 🚀 GitHub status indicators.
🎨 Benefit: It gives your terminal a polished, highly informative, and aesthetically pleasing look.
8. tmux or zellij (The Session Manager)
The Problem: You lose your terminal session when you close your laptop lid or disconnect from SSH. If you’re running 10 things and need to switch between them, it gets messy.
The Solution: These are terminal multiplexers. They allow you to create persistent, detachable “sessions” within a single window. You can run background tasks, detach from the session, close your SSH connection, reopen the session hours later, and all your processes will still be running exactly where you left them.
🛡️ Safety Net: This is mission-critical for remote work and long-running infrastructure tasks.
9. trash-cli (The Smart Deletion)
The Problem: The default rm -rf is powerful, but terrifyingly permanent. The standard OS trash isn’t always accessible or integrated into the CLI workflow.
The Solution: trash-cli moves files to a designated, restorable trash bin in the command line. Instead of permanent deletion, you can use trash-restore to recover deleted items.
🧠 Safety First: It adds a crucial layer of safety to your file operations.
🧠 Quick Cheat Sheet: By Function
| Function | Tool | What it Replaces/Improves | Killer Feature |
| :— | :— | :— | :— |
| Searching | ripgrep (rg) | grep, find | Blazingly fast, respects .gitignore. |
| File Search | fd | find | Simple syntax, avoids complexity. |
| Listing Files | exa | ls | Color-coded, modern, and intuitive output. |
| Prompting | Starship | Default Shell Prompt | Displays Git status, environment, and time contextually. |
| Sessions | tmux / zellij | Standard Terminal | Keeps processes running even after disconnecting. |
| API Testing | httpie | curl | Beautiful, human-friendly JSON request syntax. |
| History | z | Shell History | Fuzzy-matching history recall. |
🛠️ Final Advice: How to Master the Awesome CLI
The true power of these tools isn’t in knowing the name, but in building them into your muscle memory. Here are three pro tips to level up:
1. Embrace Aliases
Don’t type out complex commands every time. Use your shell’s alias feature (e.g., in .bashrc or .zshrc). If you use ripgrep constantly, create an alias that wraps it with your common flags:
“`bash
Example alias for quick, recursive searching
alias search=’rg –color=always’
“`
2. Invest in a Good Shell
While Zsh (Z shell) is often cited as the standard for maximum customization (and is often used with frameworks like Oh-My-Zsh), always ensure you are using a shell environment that supports modern features like completion and advanced history retrieval.
3. Start Small and Specific
Don’t try to install everything at once. Identify your biggest workflow pain point this week:
* Is searching logs too slow? -> Install ripgrep.
* Am I constantly reopening SSH connections? -> Master tmux.
* Are my prompts boring? -> Install Starship.
🚀 Command to Action: Close this blog post, and open your terminal. Pick one tool—maybe
fd—and spend 15 minutes replacing an oldfindcommand with the new one. Watch the difference.
The terminal isn’t just a place where you type commands; it’s where you build efficiency. Happy hacking!