Skip to content
Atlas, your robot learning host

Interim portrait

Atlas · Foundations terminal

Hello, little human. I am Atlas. One useful idea is plenty for a beginning. Read the explanation, then explore an example.

Choose your robot No recording yet · text complete

Watch · salvaged hardware

Reviewed videos and Shorts

Captions requested · no autoplay

Checking the reviewed learning library…

Videos · 16:9

Awaiting a reviewed signal

Awaiting reviewNo video assigned
Awaiting reviewNo video assigned
Awaiting reviewNo video assigned
Awaiting reviewNo video assigned
Awaiting reviewNo video assigned
Awaiting reviewNo video assigned

Shorts · 9:16

Awaiting a reviewed signal

Awaiting reviewNo video assigned
Awaiting reviewNo video assigned
Awaiting reviewNo video assigned
Awaiting reviewNo video assigned
Awaiting reviewNo video assigned
    concept for everyone

    Terminal

    A terminal is a text interface to a shell and other programs, not a separate programming language.

    Understand the idea

    A terminal presents a text interface for entering commands and seeing output. It usually hosts a shell: a program that interprets the command line. The terminal window and the shell are different parts of the setup. Windows Terminal can host PowerShell or Command Prompt; a macOS or Linux terminal can host a shell such as zsh or Bash.

    A prompt marks where a shell is ready for your next command. Tutorials sometimes show a symbol such as $ before the command. That symbol is part of the example prompt, not something to copy automatically. Your own prompt may contain a username, folder name, or other text.

    Opening a terminal usually starts a shell. Commands shown in a tutorial do not run merely because you opened that window. Read a command’s purpose before entering it, and keep source-code text in its editor rather than pasting it into an unrelated shell.

    Key points

    • 01 The terminal supplies the text interface.
    • 02 A shell interprets commands entered in that interface.
    • 03 Different shells may use different commands and syntax.
    • 04 The prompt is separate from the command you type.
    • 05 Output is a program’s response, not another instruction to type.

    Worked example

    Identify the parts of a terminal exchange

    A worked example using sample data. Nothing here runs on your computer.

    Example
    Example prompt: $
    Typed command: pwd
    Displayed output: /home/learner/human-lab
    What it means or produces
    The command is pwd.
    The path is output.
    The prompt is not part of the command.

    This labels an illustrative POSIX-shell exchange. It is not a block of commands to paste. A PowerShell or Command Prompt session can look different.

    Visual

    Follow the primary sources

    An original HWTL explanation, prepared and independently checked with AI against the sources below. This lesson has not yet been tested with human learners.

    Source review completed 2026-10-07.

    Practice · predict the result

    Separate the prompt from the command

    A small test from your robot instructors. Hints are welcome.

    What you will practice: Distinguish a terminal host, its shell prompt, the typed command, and the command output.

    Sample scenario. Synthetic POSIX-shell session hosted in a terminal. $ is already the displayed prompt. Plain pwd is available and succeeds. Do not actually paste any choice into a terminal.

    Host and interpreter
    A terminal window is displaying a POSIX-style shell session.
    Current folder
    /home/learner/human-lab
    Tutorial command line
    $ pwd
    Prompt convention
    $ is the tutorial's shell prompt marker.

    A tutorial shows $ pwd in a terminal window. With the stated working directory, which text should be typed and which text is the result?

    Attempts stay on this browser and are kept separate from lesson views and your self-reported knowledge.

    Sources and exercise scope

    Original synthetic exercise, checked with AI against primary documentation on 2026-10-08. Human learner validation is pending. A result here records this attempt; it does not establish mastery.

    Next useful step

    Keep the useful idea. Return when you need it.

    Open your learning inboxExplore another concept →
    Lesson diagnostics

    Download the public lesson material, resource choices, and robot text selected for this page. The file does not include your chat, code, or saved profile. Nothing from the trace is uploaded.

    It records the page’s selections, not video playback or proof of learning. A link from your coding tool does not supply its original recommendation trace.

    Enable JavaScript to create a trace on this device.

    Related concepts

    See also

    Oauth Scope, Working Directory, Text Editor, Webhook, Files AND Folders, Shell Command, File Paths

    Discussion

    Comments are powered by Giscus on the project's GitHub Discussions. They'll activate once we enable Discussions on the repo.

    Until then, file an issue with feedback.