I Ditched GUI Tools and My Productivity Doubled — Here Are the 5 Terminal Tools That Did It

Source: Dev.to

I used to be a GUI person—Premiere for video, Tower for Git, Finder for files.
When I started building automation pipelines for video production, data processing, and server deployments, I kept hitting the same wall: GUI tools don’t scale. You can’t loop a drag‑and‑drop, and you can’t pipe a button click.

So I went terminal‑first, and I’m not going back. Here are the five tools that made the difference.

ripgrep (rg) — Search That Actually Respects Your Time

ripgrep works fast, respects .gitignore by default, searches recursively, and handles Unicode. In a 50 GB monorepo the time saved is measured in minutes, not seconds.

# Search for "TODO" across your entire project, skip node_modules automatically
rg "TODO" --type ts

# Case‑insensitive search with context lines
rg -i "deprecated" -C 3

Why it matters in 2026

Codebases are larger than ever, and AI‑generated code adds even more boilerplate. You need a search tool that scales.

Install

brew install ripgrep   # macOS
cargo install ripgrep   # from source

jq — JSON Surgery from the Command Line

Every API returns JSON, every config file is JSON, and many log pipelines output JSON. jq lets you slice, filter, and transform that data without opening a browser or writing a Python script.

# Extract all error messages from an API response
curl -s https://api.example.com/logs | jq '.entries[] | select(.level == "error") | .message'

# Reshape data — pull specific fields into a new structure
cat data.json | jq '[.users[] | {name: .name, email: .contact.email}]'

The real power is piping: curl | jq | xargs lets you build an API automation pipeline in a single line, with no extra dependencies.

Install

brew install jq   # macOS
apt install jq    # Debian/Ubuntu

FFmpeg — The Swiss Army Knife Nobody Teaches You

Most developers know FFmpeg exists, but few realize it can replace an entire video‑editing suite. I produced a 49‑second educational short—compositing layers, syncing audio, adding animated subtitles—entirely from the terminal.

# Trim a video with frame‑accurate precision
ffmpeg -ss 00:01:30 -to 00:02:45 -i input.mp4 -c copy trimmed.mp4

# Overlay a watermark with position control
ffmpeg -i video.mp4 -i logo.png -filter_complex "overlay=W-w-10:H-h-10" output.mp4

# Generate a thumbnail from a specific timestamp
ffmpeg -i video.mp4 -ss 00:00:15 -frames:v 1 thumbnail.jpg

Once you can script video processing, you can automate content pipelines: batch‑process hundreds of videos, auto‑generate thumbnails, convert formats at scale.

Install

brew install ffmpeg   # macOS
apt install ffmpeg    # Debian/Ubuntu

lazygit — Git, But You Can Actually See What’s Happening

lazygit provides a terminal UI for Git—staging hunks, interactive rebasing, cherry‑picking—without leaving the terminal or touching a mouse.

# Run it in any Git repository
lazygit

The visual diff panel lets you see exactly what you’re about to do before you do it. Interactive rebases become painless, and conflict resolution drops from “open VS Code” to “done in 10 seconds.”

Pro tip: press ? inside lazygit for the full key‑binding list. Space to stage, c to commit, p to push—covers about 90 % of a typical workflow.

Install

brew install lazygit                     # macOS
go install github.com/jesseduffield/lazygit@latest   # from source

zoxide — cd, But It Remembers Where You’ve Been

zoxide replaces cd with a smart directory jumper. It learns which directories you visit most and lets you jump to them with partial names.

# Instead of: cd ~/projects/company/backend/services/auth
z auth   # jumps to the most‑used "auth" directory

On an average workday I cd about 80 times. Each full path takes 3–5 seconds to type; zoxide cuts that to under 1 second, saving 5–6 minutes daily—nearly a full workday over a year.

Install

brew install zoxide
# or
curl -sSfL https://raw.githubusercontent.com/ajeetdsouza/zoxide/main/install.sh | sh

None of these tools are brand‑new, but together they changed how I think about work. GUI tools are great for one‑off tasks, but the moment you need to do something twice, the terminal wins—every time.

I went from “let me open the app” to “let me write the command,” and my throughput doubled. Not because I’m faster at typing, but because scripts don’t forget steps, don’t get tired, and don’t need a mouse.

What does your terminal setup look? I’m always looking for tools I’ve missed—drop your favorites in the comments below.

Some parts of this article were refined with AI assistance.