CACrown ArchivesHistory · sources · collections
Menu
Research dossier · General Reference

Command-line interface

type of computer interface based on entering text commands and viewing text output

Cross-disciplinary reference desk with index cards, atlas, dictionary and catalogue
General referenceInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionSep 14, 2026
Entity authorityQ189053
Source-derived summary

A command-line interface (CLI), also known as a command-line shell, is a means of interacting with software via commands – each formatted as a line of text. The concept of interacting with a computer via text evolved over two decades, transitioning from physical hardware to sophisticated software. Before the CLI, computers were programmed using physical switches or punched cards. The shift toward a "command" style interaction began with the use of Teleprinters (Teletypes). Early systems like the Whirlwind I (1951) at MIT began utilizing typewriter-like inputs for direct control, moving away from batch processing where you'd hand a stack of cards to an operator and wait hours for a result. Devices like the Teletype Model 33, introduced in 1963, allowed operators to type a command and receive a printed response from the computer.

The command-line interpreter emerged when computers became powerful enough to handle multiple users at once, known as Time-Sharing. The Compatible Time-Sharing System (CTSS), developed in 1961 at MIT, introduced the first true command-line interpreter. For the first time, a user could type a command like LOGIN or PRINT, and a dedicated program (the supervisor) would parse that text and execute the corresponding function. In 1964, Louis Pouzin introduced the software we now recognize as a "shell" for the Multics operating system, providing a programmable environment for executing scripts.

Editorial summary

Begin with the source’s own compact description: “Command-line interface” is type of computer interface based on entering text commands and viewing text output. The dossier treats that line as a proposition to test through Command-line, interface and type, not as a finished interpretation.

Editorial reviewA dependable orientation record for establishing vocabulary, names and a first evidence trail. The current lead gives the account dated anchors—1951, 1963, 1961, 1964—that can be checked directly. The selected authority fields contribute no independent date. For this dossier, Command-line, interface and type is the immediate research focus.
Editorial analysis

Why this record matters

The phrase “type of computer interface based on entering text commands and viewing text output” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.

Evidence profile

Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Sep 14, 2026. The linked authority identifier is Q189053. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1951, 1963, 1961 and 1964.

Critical limits

Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.

Best used for
  • Subject orientation
  • Search vocabulary
  • Locating named sources
Verify next

The closest primary source, responsible institution and strongest cited specialist reference.

Three-step research path

  1. Establish the record: confirm the title “Command-line interface”, its source revision and the description used here.
  2. Expand the search: follow Command-line interface primary sources, Command-line interface archive and Command-line research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Command-line interface”?
  2. Which institution is responsible for the underlying evidence?
  3. Which cited source is closest to the event, object or claim?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from Command-line interface” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.