Products · Broad category
Command-line tools
Raised as a usability problem by 393 people on Hacker News over 20 years (2007–2026), in 335 threads.
This is a broad category rather than one product, so its issues aren't ranked on the home page.
No issue was raised by at least 3 people in 3 threads this year.
- 1
- 2
- 3
- 4
- 5
- 6
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
Every issue, all time, most people first
Commands and options can't be discovered without prior knowledgeUnreviewed
20072026- Users struggle to discover which keyboard commands exist2026-08-28
- Terminal tools require memorizing commands and reading manuals to use2026-07-10
- Users must read manual pages to find the right flags2025-10-29
Commands can't be discovered or remembered, so man pages are browsedUnreviewed
20072026- Users must scroll through man pages to find commands, with no search for features2026-02-14
- Users can't discover or remember commands and must browse man pages2024-07-08
- Tool options differ by version or platform, so users must slowly hunt through man pages2024-05-21
Cryptic names and inconsistent argument order are hard to rememberUnreviewed
20072026- Too many positional arguments makes users forget which argument is which2025-03-23
- Positional argument order is easy to mistype when switching between systems2024-07-27
- Forces switches to come before positional arguments, which the commenter finds annoying2023-10-25
Man pages and help output are too verbose or too terseUnreviewed
20072026- Man page is hard to use; examples are scattered and don't show needed syntax2025-10-10
- Command syntax is terse, cryptic, baffling, with insane defaults and obscure man pages2024-07-27
- Default output is rarely useful and the man page is overly complicated2023-10-06
Hard to remember -l versus -L while typing a commandUnreviewed
20072026- Forgets to add flags before running; can't easily insert them after typing input2025-01-30
- Short flags are confusing and inscrutable, so the user rarely uses them2024-08-10
- Users must look up command-line flags again every time they use them2024-05-08
Can't tell how arguments will be read or if it will workUnreviewed
20072026- Running the tool with no arguments gives no useful guidance2026-02-23
- Argument-based command line tools are hard to use because the valid argument combinations are unclear2020-02-28
- Command line gives no obvious affordances, so users must guess what input works2019-09-08
Default colours make critical info unreadable on light backgroundsUnreviewed
20072026- Hard-coded custom colour themes are hard to read and ignore the user's terminal colour settings2026-02-18
- Tools override the user's chosen terminal colours by default, making text hard to read2024-10-03
- Default colours are distracting and some become unreadable across terminals2024-10-03
Windows terminal lacks basic editing featuresUnreviewed
20072026- Editing long previous commands to make variants is tedious, requiring moving the cursor through them2022-11-24
- Very hard to edit long commands in the terminal2022-06-01
- Editing long freeform text on the command line gets annoying fast2020-07-08
Browsing, copying and moving files harder than in a GUIUnreviewed
20072026- Newcomers find command-line tools confusing, harder than dragging files in Explorer2026-07-11
- Moving files in a terminal is less natural than dragging or copy-paste with the mouse2021-04-09
- Browsing, ordering, copying and moving files is harder in the command line than in a GUI2021-04-09
ip output is harder to read, and its help is hard to findUnreviewed
20072026- Ip man page is frustrating to navigate compared with ifconfig's2023-08-08
- Must recall many ip arguments or consult man page to see interface status2022-11-07
- Output is harder to read than ifconfig, and the ip keyword makes online help hard to find2018-05-25
Inconsistent flag syntax with too few clues about optionsUnreviewed
20072026- Inconsistent, cryptic flags and options are hard to remember and use2022-05-02
- Adding new options silently breaks scripts that rely on abbreviated flags2020-09-18
- Unclear which files get skipped, and the options are hidden behind two flags2017-10-09
Typing exact file names and finding locations is hardUnreviewed
20072026- Typing exact file and folder names is hard, and finding locations is hard too2021-04-09
- Long filenames are hard to type and find in file explorer2017-08-18
- Moving through folders requires typing long paths and commands, with no visual cues about location2012-11-09
Abbreviated command names like ls are hard to rememberUnreviewed
20072026- Single-letter command names are impossible to search for and docs are hard to find2021-12-19
- New developers can't tell what a command's short name does when reading scripts2019-08-17
- Obscure abbreviated command names like ls are hard to remember2011-07-07
Confirmation prompt for every file when deleting manyUnreviewed
20072026- Interactive rm prompts are a terrible UI; users glaze over and stop reading them2023-11-07
- Rm -i prompts for every file, which is inconvenient when deleting many files2022-02-20
- Prompts for confirmation on every file, so deleting many files is annoying2013-03-14
Single-dash long options leave it unclear what flags meanUnreviewed
20072026- Long-form --help and --version flags are rejected, forcing users to guess alternative syntax2025-02-10
- Single-dash long options make users guess whether -long means --long or separate flags2021-04-08
- Hyphen-based long options with hundreds of flags feel absurd and cluttered2018-01-28
Help pages show syntax but no quick usage examplesUnreviewed
20072026- Wrong usage gives terse error instead of help; --help dumps overwhelming unsorted option list2026-07-16
- Help is only at a webpage, and subcommand help needs the word order reversed2022-09-19
- Help pages show syntax and option lists but no quick usage examples2011-08-05
Cryptic errors leave people unsure how to recoverUnreviewed
20072026- Non-technical users must type commands, get cryptic errors, and have no guidance on recovery2025-01-08
- Failed commands give cryptic errors, leaving users unsure how to recover2022-05-08
- Users must guess commands blindly and get only cryptic syntax errors in response2020-06-16
Can't click and select text in the terminalUnreviewed
20072026- Terminal text editing works differently, so you can't simply click and select text2024-01-12
- Up-arrow loses edits and selecting text with shift+arrow keys doesn't work for editing commands2019-09-29
- Cannot select text in the shell prompt using keyboard shortcuts2011-08-06
xargs behaves differently, so first attempts fail or misfireUnreviewed
20072026- Xargs has different semantics, so first attempts error out or do the wrong things2017-10-09
- Could not figure out how to make xargs read from a file instead of stdin2010-02-10
- Hard to remember xargs options, so commenter prefers find -exec2009-06-06
Long option names are slow to type and error-proneUnreviewed
20072026- Long command options are hard to remember and easy to misspell, forcing repeated lookups2021-11-11
- Long option names are hard to remember, easy to mistype, and lack shell completion2021-11-11
- Long alphabetical option lists force readers to scan everything to find one option2020-03-04
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 50 complaints
- Typical CLI user interface design is abysmal for ordinary users2026-09-25
- CLI tools lack shared conventions, so each must be learned separately2026-09-22
- Ignores so many files that it seems basically useless2026-09-17
- Users struggle to discover which keyboard commands exist2026-08-28
- Each tool has its own non-standard command language, so learning complex ones is very steep2026-08-22
- Wrong usage gives terse error instead of help; --help dumps overwhelming unsorted option list2026-07-16
- Cryptic errors and path rules must be learned; spaces and relative paths break copies2026-07-12
- Newcomers find command-line tools confusing, harder than dragging files in Explorer2026-07-11
- Terminal tools require memorizing commands and reading manuals to use2026-07-10
- CLIs require tons of flags or config files to configure behavior2026-06-28
- No clean way to control scrollback, forcing awkward hacks or giving it up2026-06-22
- Thrown-together test CLIs are unpleasant to use and cause manufacturing staff errors2026-04-20
- Shell scripts grew numerous and overly complex, and the CLI experience felt cluttered2026-04-16
- Repeatedly bouncing between cd, cd .., tab completion and ls to move across projects2026-03-09
- Hard to spot disguised changes like whitespace and comment edits in diffs2026-03-03
- Running the tool with no arguments gives no useful guidance2026-02-23
- Hard-coded custom colour themes are hard to read and ignore the user's terminal colour settings2026-02-18
- Users must scroll through man pages to find commands, with no search for features2026-02-14
- Default settings hang or silently drop output unless every script is configured to disable tty2025-12-14
- Changing volume requires entering and exiting a CLI tool, too slow when audio starts unexpectedly2025-11-03
- Users must read manual pages to find the right flags2025-10-29
- Man page is hard to use; examples are scattered and don't show needed syntax2025-10-10
- On error, typed input is lost and must be copied back and forth2025-09-19
- Hard to discover options; errors point to manuals instead of helping2025-09-16
- Functionality only reachable by memorizing arcane command names2025-09-16
- Options depending on other options is unintuitive for users, so they struggle to use the tool correctly2025-09-07
- Two optional positional arguments force awkward empty-string placeholders to reach the search path2025-09-02
- Commands are too obscure and non-intuitive to remember2025-07-05
- Needs sh, ImageMagick, and LLM help just to perform a simple PDF task2025-06-26
- App crashes, hangs and logs user out when starting workouts or editing weights2025-06-18
- Code blocks and explanations split across pages, forcing constant back-and-forth scrolling2025-05-30
- Slow-starting scripts cause distraction and wait time when used2025-05-29
- Working with the command line feels like operating blindfolded, with no view of files2025-05-24
- Entering fields one at a time in the command line is too clunky2025-04-22
- Too many positional arguments makes users forget which argument is which2025-03-23
- Help output and manpages are so large with hundreds of options that users can't find what they need2025-03-22
- Defaults ignore git directories and dot files, so wanted results are hidden2025-03-20
- Ignores many folders by default, and the options to include them are hard to remember2025-03-19
- Same flags behave differently between fd and rg, causing confusion when switching2025-03-19
- Command interfaces are obtuse, need heavy memorization, and make it easy to make costly mistakes2025-03-11
- Users must memorize exact command names, argument order, and dash styles, or get punished2025-03-10
- Must learn hundreds of different command DSLs, varying across platforms, slowing productivity2025-02-10
- Long help dumps on errors bury the one useful line and confuse beginners2025-02-10
- Categories view is useless; user must navigate extra steps before reaching the list2025-02-10
- Long-form --help and --version flags are rejected, forcing users to guess alternative syntax2025-02-10
- Occasional users find CLI glitches and cruft frustrating and hard to remember commands2025-02-06
- Forgets to add flags before running; can't easily insert them after typing input2025-01-30
- Non-technical users must type commands, get cryptic errors, and have no guidance on recovery2025-01-08
- Must remember command syntax and output format, competing with debugging context2025-01-06
- Command-line tools have horrible, unintuitive UX that users must learn2024-12-27