Command Line Interface

Most people operate a computer by clicking on images and buttons. But there is another way. With a command line interface, you type the desired command as text and press Enter. The computer executes it and likewise responds with text. The window in which this happens is called a terminal or console. There you see no icons, only lines of letters and numbers.

Why typed commands still survive today

One might think that operating a computer without images is outdated. The opposite is true. A typed command is exact: it states precisely what should happen to which file. A click is less precise, because it always only handles one thing at a time. Anyone who wants to rename a thousand images either clicks a thousand times or types a single line.

There is a second advantage on top of that. Commands can be written down and passed along. A set of instructions with five lines of text works the same for everyone. Instructions with click-paths become outdated as soon as a program changes its appearance. That is why many technical guides consist almost entirely of commands meant to be copied.

The third reason is distance. Servers in data centers have neither a screen nor a mouse. You connect to them over the network and control them exclusively via text. The large computers on which AI models are trained are also operated this way. Anyone working with such technology cannot avoid the command line.

From the typed word to the executed program

Between the user and the operating system sits a program called the shell. It reads the typed line and breaks it down into its components. The first word is the command itself, that is, the name of a program. Everything else consists of details about it, often file names or additional options. The shell then starts the appropriate program and hands it these details.

An example makes this tangible. The command “cp image.jpg backup.jpg” copies a file. “cp” stands for copy, followed by the source and the destination. Such abbreviations seem cryptic at first. But you only need to learn a few dozen of them to cover everyday use.

The matter becomes especially powerful through chaining. You can pipe the output of one program directly into another program. This turns small tools into a chain, similar to an assembly line. One program filters, the next sorts, the third counts. These building blocks have existed since the 1970s, and they still work today.

Terminals in developer products and AI tools

Anyone who programs almost always has a terminal open. The code editor, the version control system Git, and the tools for publishing software are all controlled via commands. Cloud providers such as Amazon or Google also ship a matching command line tool with their services. This allows hundreds of servers to be set up at once.

In the news, the term currently comes up mainly because of AI assistants. Tools like Claude Code or Codex run directly in the terminal. There, you describe in plain language what the program should do, and the AI writes code or executes commands itself. This is remarkable: the command line is thus simultaneously the oldest and the newest way of operating a computer.

A common misconception is that the command line and the graphical interface are opponents. In fact, almost every professional uses both in parallel. For reading an email, text is impractical, but for searching through ten thousand log files, it is ideal. You choose the tool based on the task, not on principle.