shell
A shell is a program where you control the computer by typing commands: you manage files, launch programs, and automate tasks without using the mouse.
In plain terms
A computer can be controlled in two ways: by clicking icons and buttons, or by typing text commands. The shell is the second path. It acts like an interpreter between you and the machine: you describe what you want, it translates it for the machine, then writes back the result.
It is similar to when, in a restaurant, you do not point at pictures on the menu but tell the waiter your order. If you know what you want, this is faster and more accurate, but you must know the language for it.
It is important in the AI era because coding agents also work largely through the shell. If an agent installs a program, runs a test, or organizes files, it issues the same commands a developer would type. These commands run with your user privileges, so it matters a lot which commands you allow the agent to run.
How it works
- You open a terminal window where the shell waits for your command with a blinking cursor. The short indicator at the beginning of the line (such as $ or >) is called a prompt; this is not the same as a prompt written to an AI.
- You type a command, for example to list the contents of a folder, and press Enter.
- The shell interprets the line: it executes some simple commands itself, and for others, it finds which program to launch and passes the given data to it.
- The program runs, the result appears as text in the window, and the shell waits for the next command.
- You can chain commands together and save them to a file. This creates a script that executes an entire workflow with a single launch.
An everyday example
You ask a coding agent to fix a bug on your website. Before running the tests, it asks: "Can I run this command?" At this point, it requests permission to use the shell, and what it can do on your machine depends on your approval.
Who is affected
A common misconception
Limits and risks
- The shell rarely asks for confirmation; a poorly written delete command can erase files in moments, irreversibly.
- Never copy and paste or run a command you do not understand, even if a website or an AI suggests it.
- If you give an agent unlimited shell access, it can do almost anything on the machine in your name, so it is advisable to restrict it with permission rules or an isolated environment (sandbox).
- Commands differ by system: what works on Linux or Mac is often phrased differently on Windows.
Similar, but not the same
- terminal – The terminal is the window where you type, while the shell is the program running inside it that interprets and executes your commands.
- command line – The command line generally refers to the method of text-based control, while the shell is the specific program (for example, Bash or PowerShell) that implements it.
- operating system – The operating system runs the machine; the shell is merely a wrapper around it through which you issue commands.
Related concepts
user interface, operating system, developer tools
Bash, PowerShell, Zsh, shell-szkript
A brief history
Ken Thompson wrote the first Unix shell in 1971. Among today's most widespread variants, Bash appeared in 1989 and Microsoft PowerShell in 2006.
Where things stand
The shell has been a basic tool for development and operations for decades. By the end of 2026, it is also one of the most important work surfaces for coding agents, so attention is focused on its secure, permission-based use.
In the news
- Ghostjacking and fake repos: prompt injection used to hijack coding agentsAug 10, 2026 · Code
Also known as
shell · command interpreter · shell · shell · command shell · command shell · command-line shell · Unix shell
Sources
This entry was machine-edited and has undergone machine expert review; the “In the news” section updates automatically from Agent Age stories.