# Understanding Bash: The Language Your AI Agent Speaks to Your Computer > Terminals, command lines, and why AI coding tools like Cursor, Claude Code and Codex become so much more capable when they can run Bash commands. Source: https://www.peregianhub.com.au/articles/understanding-bash/ If you have used an AI coding agent recently — Cursor, Claude Code, Codex, Windsurf — you may have noticed it doing something that looks different from a normal chat conversation. Instead of just writing text back to you, it runs commands. It creates files, installs software, checks for errors, and fixes them. It does this through Bash. This article explains what Bash is, what a terminal is, and why access to both of them turns an AI from a conversational assistant into something closer to an autonomous operator. Play with the demos along the way to build intuition. ## Start with the terminal Before we get to Bash, we need the room it lives in: the terminal. A terminal is a text-based interface to your computer. Instead of clicking icons and dragging windows, you type short instructions and the computer executes them immediately. It prints the results back as text. Every modern computer has one. On a Mac it is called Terminal. On Windows it is called PowerShell or Windows Terminal. On Linux it is usually just called the terminal. Think of it this way: - The graphical desktop is the dashboard of a car. Designed for ease, with dials and buttons in familiar places. - The terminal is direct access to the engine. You can inspect, adjust and control things that the dashboard was never designed to show you. The dashboard is great for everyday driving. But when you need to diagnose a problem, automate a task, or do something the menus do not offer, you open the terminal. ## What the command line is The command line is the conversation that happens inside the terminal. You type a command. The system executes it. Output appears as text. The terminal is the room. The command line is the conversation. Bash is one specific language used in that conversation. Try clicking through some basic commands below to see how this conversation works. Try it A simulated terminal session $ Click a command below to run it This is a simulated terminal. Click the command buttons in any order to see what they do. Notice how each command is short and does one specific thing. `pwd` tells you where you are. `ls` shows what is here. `cd` moves you somewhere else. `cat` reads a file. These are the building blocks. ## Anatomy of a command Every Bash command follows a pattern: the command name, optional flags that modify its behaviour, and arguments that tell it what to act on. Explore Break a command into its parts Command Flag / Option Argument Once you can read a command’s parts, the output of any AI agent becomes much less mysterious. You can see what it is doing and why. ## The pipe: chaining commands together Bash follows a philosophy: build small tools that each do one thing well, then connect them. The pipe symbol `|` sends the output of one command into the input of the next. This is called composability, and it is one of the most powerful ideas in computing. Build Chain commands into a pipeline $ Click commands to build a pipeline Available commands Output Each command transforms the data and passes it to the next. This is how simple tools combine into powerful operations. A single `ls` shows files. Add `grep` and you filter them. Add `wc -l` and you count them. Three small tools, one pipeline, a precise answer. This is the pattern AI agents use constantly — chaining small operations to accomplish complex tasks. ## Why this matters for AI agents Here is the key insight. An AI model on its own can reason, write and explain. But it cannot act on your computer. It has no hands. Bash gives it hands. When an AI agent like Cursor, Claude Code or Codex has access to a Bash tool, it gains the ability to read your project, make changes, run code, observe results, and fix problems — all autonomously. The real power is not any single command. It is the loop. Watch The autonomous loop: how an AI agent uses Bash Task "Create a Python script that fetches the weather and handles errors gracefully." 1 Read Check current state ls -la && cat requirements.txt 2 Change Write the code cat > weather.py << 'EOF' import requests response = requests.get(url) print(response.json()) EOF 3 Run Execute and test python3 weather.py 4 Observe Read the error NameError: name 'url' is not defined 5 Fix Edit and add error handling cat > weather.py << 'EOF' import requests import sys API_URL = "https://api.weather..." try: response = requests.get(API_URL) response.raise_for_status() print(response.json()) except requests.RequestException as e: print(f"Error: {e}", file=sys.stderr) sys.exit(1) EOF 6 Verify Run again — it works python3 weather.py {"temp": 24, "condition": "sunny"} **This is the loop.** Read, change, run, observe, fix. The same cycle a human developer follows — but the agent executes it in seconds through Bash commands. Each step is a command. Each command gives the agent information to decide what to do next. Without Bash, the AI is advisory. It can tell you what to do. With Bash, it is operational. It can do the thing, check if it worked, and fix it if it did not. ## What agents actually run When you watch an AI agent work, most of what it does falls into a handful of command categories. Here is a quick reference. Reference Commands you will see AI agents use ls List files and directories ls -la src/ cd Change directory cd my-project/ cat Display file contents cat package.json mkdir Create a directory mkdir -p src/components cp / mv / rm Copy, move, or delete files cp config.yml config.backup.yml grep Search for text patterns grep -r "TODO" src/ find Find files by name or type find . -name "*.py" python3 Run a Python script python3 app.py node Run a JavaScript file node server.js curl Make HTTP requests curl -s https://api.example.com git status Check what has changed git status git diff See exact changes in files git diff src/app.py git commit Save changes with a message git commit -m "fix login bug" pip install Install Python packages pip install requests flask npm install Install Node.js packages npm install express ## The practical takeaway You do not need to become a Bash expert to work effectively with AI agents. But understanding what the terminal is and why Bash matters gives you three advantages: 1. **You can read what the agent is doing.** When Cursor runs a command, you can follow along instead of treating it as a black box. 2. **You can guide it better.** Knowing that the agent has file system access, can run scripts, and can install tools helps you give it clearer instructions. 3. **You can intervene when needed.** If something looks wrong, understanding the command being run helps you decide whether to let it continue or stop it. Bash is the reason AI coding agents feel so capable. It is not magic. It is a well-designed, decades-old interface to the machine — and it turns out to be exactly what an AI needs to go from thinking to doing. Share this article [ Articles ](https://www.peregianhub.com.au/articles/)