What UX rules should terminal tools follow?

November 17, 2026 5 answers
Asked by 9c!ferrycaddy_284

I'm thinking about usability rules for command-line tools and terminal interfaces, from Ctrl+C and tab completion to help text and progress output. Which conventions are worth following, and where do they conflict?

Answers

_e68~cablethimble.3

For an interactive terminal interface, make the escape route obvious. Ctrl+C should stop the current operation or exit, and the screen should tell you how to quit without making you hunt through a manual.

Optional Vim-style keys are handy: j and k for movement, slash for search, n for the next result, and question mark for help. Keep arrow keys working too. Escape can leave a mode or dismiss a prompt. None of that should require a mouse.

Also, don't wipe out the terminal history on exit. People may want to see what they were doing before opening the interface.

p.482!clovercaper:

There's a distinction between cancelling an operation and exiting the whole interface. Whichever Ctrl+C does, make it clear and predictable.

Reply to this answer
_s68!drumferrule.2

Progress is useful, but please don't make ordinary output noisy. Commands often feed other commands, and status messages mixed into standard output can break that.

Send progress to standard error, or offer a verbose option. A tool can show status for an interactive user while staying quiet when its output is being piped. Some people prefer quiet by default even at a terminal, so this is a design choice rather than a universal rule.

6h!plaidratchet_538:

A long-running command that appears frozen is frustrating too. Even a short status message can help when an accurate progress bar isn't available.

Reply to this answer
2p!canvasnotch_437

Make basic use discoverable. A concise help screen should show the common commands and options first, with a way to find the full reference. Group aliases together rather than giving each one a separate line.

I'd normally expect both -h and --help to show help. But existing commands sometimes use -h for human-readable sizes, so changing an established flag just for consistency can cause its own problems.

Reply to this answer
_k58+hingequartz.6

Consistent flags are great within a new toolset, but don't assume every short option can be standardized. SSH uses -p for a port while SCP uses -P. SCP's -p already means preserving file metadata, reflecting its older copy-command interface. Compatibility can be a good reason not to change an awkward convention.

Reply to this answer
f.714+tramwinder

Completion should be easy to discover and install, without tying users to one particular shell plugin. And not every utility needs to run as a service. Sometimes the simplest interface is a command that does its job and exits.

For scripts, consider whether Bash features are actually needed. A portable shell script can avoid assuming Bash is installed at a particular path.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions