Sign in with Google

Upgrade your terminal

Small command-line tools that make the terminal faster and nicer every day.

For developers who live in the terminal. Each tool replaces or adds to a command you type every day, and installs in a minute.

9 picks in 5 sections · checked by an editor on Oct 30, 2026 · How we pick

01Find3 picks

  1. fzfjunegunn/fzf

    Start here. Fuzzy search for files, history and anything else.

    CLI · MIT · active last week · ★ 84k

    87worth
  2. zoxideajeetdsouza/zoxide

    Pick this to jump to folders you use often with a few letters.

    CLI · MIT · active last week · ★ 40k

    74worth
  3. ripgrepBurntSushi/ripgrep

    Pick this to search the text of a whole project in a blink.

    CLI · Unlicense · active 5 days ago · ★ 70k

    74worth

02History1 pick

  1. Atuinatuinsh/atuin

    Pick this for shell history you can search and sync between machines.

    CLI · MIT · active 2 days ago · ★ 32k

    84worth

03Prompt1 pick

  1. Starshipstarship/starship

    Pick this for a fast prompt that shows Git and language info.

    CLI · ISC · active 2 days ago · ★ 61k

    82worth

04Git2 picks

  1. lazygitjesseduffield/lazygit

    Pick this to stage, commit and rebase from a simple screen.

    CLI · MIT · active yesterday · ★ 84k

    82worth
  2. Jujutsujj-vcs/jj

    Pick this to try a simpler version control that still works with Git.

    CLI · Apache-2.0 · active 21 hours ago · ★ 32k

    82worth

05Files2 picks

  1. batsharkdp/bat

    A cat with colors, line numbers and Git changes.

    CLI · Apache-2.0 · active 20 hours ago · ★ 61k

    75worth
  2. ezaeza-community/eza

    A modern ls with colors, icons and Git status.

    CLI · EUPL-1.2 · active 4 months ago · ★ 24k

    64worth

More in For developers

MCP servers to start with

Well-maintained Model Context Protocol servers that make coding agents immediately more useful.Inside: GitHub MCP Server, Playwright MCP, Context7 + 3 more6 picks

Other groups

See every project in this category on Explore →Missing a project? Suggest it →

How we pick

An editor picks 6 to 12 projects for one job and writes when to choose each one. Every pick had a commit in the last 6 months. It is not archived. Its worth score is 60 or more. An editor breaks a rule only for a reason, and writes that reason in the pick's note. We check every list again each quarter. A pick goes when it breaks a rule or a clearly better project appears.