How to Browse Terminal Tools by Category or Language on Terminal Trove

Updated

Terminal Trove organizes its tool collection into two browse paths: Categories (what the tool does, such as TUI, CLI, AI/LLM, Git, or databases) and Languages (what it's written in, such as Rust, Python, Go, or Shell). Use the category path when you know the job you need done; use the language path when you want tools you can read, build, or contribute to in a stack you already know. Both paths are reachable from the homepage.

Browse by category

On the homepage, the Browse By Categories section lists the site's functional groupings. The categories shown are:

  • TUI
  • CLI
  • AI LLM
  • GIT
  • MONITORING
  • NETWORKING
  • SECURITY
  • DEVOPS
  • DOCKER
  • KUBERNETES
  • DATABASE
  • TEXT EDITORS

How to use it:

  1. Open terminaltrove.com.
  2. Scroll to Browse By Categories.
  3. Select the category closest to your task. For example, choose TEXT EDITORS if you want a terminal-based editor, or KUBERNETES if you need cluster tooling.
  4. Review the listed tools and open the one that matches your workflow.

Expected result: a filtered set of tools in that category, each with a short description. The homepage shows this pattern in its "Newly Added Tools" list, where entries carry a one-line summary — for example, edamame is described as "A terminal Markdown editor that stays rendered while you edit," and mitos as "A minimal modern, batteries-included, modal text editor."

When this path fits: you have a concrete task (editing Markdown, inspecting Git history, managing containers) and want options without caring about implementation language.

Browse by language

The Browse By Language section lists implementation languages:

  • RUST
  • PYTHON
  • C
  • HASKELL
  • GOLANG
  • JS
  • C++
  • SHELL

How to use it:

  1. From the homepage, go to Browse By Language.
  2. Pick your language.
  3. Scan the results for tools that match your task.

Expected result: tools implemented in that language. This is useful when you plan to read the source, vendor the tool into a project with a matching toolchain, or contribute fixes.

When this path fits: language compatibility matters more than feature category — for example, you want a Rust binary for easy distribution, or a Python tool you can extend.

Choosing between the two paths

Your situation Start with Why
You know the task but not the tool Categories Groups by function (Git, DevOps, databases, editors)
You want to read or modify the source Languages Groups by implementation language
You need something installable with an existing toolchain Languages Matches your build environment
You're exploring what exists in the terminal Categories, then "Explore All Tools" Broad functional overview first

If neither path narrows things enough, the homepage also offers Explore All Tools for the full collection and a random-tool option for discovery.

Practical tips

  • Combine the paths mentally. A category page tells you what a tool does; the tool's own entry and the language listing tell you what it's built with. Check both before committing to a tool you'll maintain.
  • Watch the "Newly Added Tools" and "Terminal Tool of The Week" sections. These surface recent entries with one-line descriptions — a fast way to spot tools before browsing full categories. The current featured tool, eprofiler-tui, is described as "A terminal based flamegraph viewer for OTLP and gRPC profiling data."
  • Use the descriptions to filter quickly. Entries like llamastash ("A zero-overhead, terminal-native local-LLM manager") or yq ("A lightweight and portable command-line YAML, JSON, INI and XML processor") show the site's convention of pairing each tool with a single-sentence purpose statement, which is often enough to decide whether to dig further.

The site also notes that it places tools and products in front of "92K+ tech professionals" through advertising, so sponsored entries may appear alongside organic listings — treat the description as a starting point and verify fit against the tool's own documentation.