Working in the Terminal
A coding agent uses ordinary files, shell commands, Git, dependencies, tests, and deployment tools. Reading that loop helps you supervise it safely.
The terminal is a text interface to a shell, the program that parses commands and starts other programs. Bash is common on Linux and servers; modern macOS uses zsh as its default login shell, though users can change it. 1
Begin by knowing the working directory. pwd prints it; ls lists entries; cd moves to another directory. Relative paths start from where you are. Before approving a command that edits or deletes files, check both the path and the current directory.
Shell syntax has consequences. Wildcards are expanded by the shell before a command runs. Quote a pattern when the receiving tool should interpret it: find . -name '*.png'. Quote paths containing spaces. Read a command containing sudo, recursive deletion, redirects, or downloaded scripts before running it.
Git records selected changes when they are committed. git status shows modified, staged, and untracked files; git diff shows content changes; a commit captures a chosen snapshot. Git does not automatically record ignored files, uncommitted work, shell side effects, sent messages, database changes, or deployments.
A branch is a name pointing to a line of commits, not a full duplicate of the project. Use a separate clone or worktree when two tasks need isolated working directories. Fetch downloads remote history without integrating it; pull normally fetches and then merges or rebases according to configuration.
Git makes code changes inspectable when they are captured well. It does not make every agent action recorded or reversible.
Projects depend on packages and environment configuration. A lockfile improves repeatability, but operating system, CPU architecture, environment variables, install flags, registries, and build scripts can still differ. Containers reduce some variation without making every machine identical.
Before code is accepted, run the checks the repository actually defines: formatting, linting, type checks, unit tests, integration tests, and a build where relevant. A passing suite is evidence for the behavior it covers, not proof that the change is bug-free or secure.
CI/CD is often oversimplified. Continuous integration builds and tests changes. Continuous delivery keeps a release ready; continuous deployment automatically releases qualifying changes. A team may require manual approval after tests pass, and a deployment can still fail after CI succeeds.
Supervising a coding agent is therefore a sequence: confirm its working boundary; inspect commands; review the diff; run relevant checks; keep secrets and production credentials out of reach; and approve release separately. The terminal is not magic—it is an audit surface, if you pause to read it.
Evidence
Sources
- 1Change the default shell in Terminal on Mac
Apple Support · Documentation · checked 2026-07-13
After the reading
Where to actually begin.
You don't need to install anything or write a line of code. Six moves turn the guide into something you can use this week.
- Pick one assistant and live in it.
Open ChatGPT, Claude, or Gemini and use it daily for a week on real tasks — email, summaries, planning. Fluency comes from reps, not reading.
- Give it the context this task needs.
Some products can store preferences or retrieve past information; the model still answers from the context assembled for this turn. State the goal, show one example of “good,” and name the format you want back.
- Verify anything that matters.
It writes what sounds right, which isn't the same as right. Check every fact, figure, quote, and citation before you lean on it.
- Feed it your own material.
Paste in the document, the thread, the spreadsheet. The moment it answers from your stuff instead of the open internet, it gets genuinely useful.
- Start free; pay when it buys back time.
The free tiers are enough to learn on. Upgrade only once a tool is clearly saving you hours of your week.
- Be careful the moment it can act.
Answering is low-stakes; doing — sending, buying, deleting — is not. Hand an agent real access slowly, and watch what it does.
How to read the whole field.
Researchers live in the architecture, training, and prompting layers. Builders and operators care about inference, tasks, and evaluation. Safety and policy people orbit alignment. Investors track the hardware — with scaling laws as the thesis tying it together.
And the one thing to never forget: these systems are built to sound right, which isn't the same as being right. Anything that matters gets an independent check.
On the numbers.
Capital spending, product behavior, regulation, and infrastructure relationships move quickly. Each time-sensitive section carries a snapshot date, and its sources show when they were checked.
Reported facts, forecasts, compiled estimates, and editorial interpretation are labeled differently. Treat any specific number as a snapshot, not a fixed point.
Decoded & designed · Working Knowledge · 2026 Edition
Time-sensitive claims carry checked dates and source links.