Words You’ll See

Computer basics we will use

Terminal (also: shell, command line)

A text window where you type commands for the computer. On a Mac, open the app named Terminal. On Windows, use PowerShell, Windows Terminal, or Git Bash. Grok Build runs inside a terminal.

Command

A short line of text you type and run by pressing Enter. Example: grok --version asks the computer to print which version of Grok is installed.

Folder / directory

A place that holds files. Paths look like ~/projects/my-game. The character ~ means "my home folder."

Working directory

The folder your terminal is “in” right now. Grok usually works on files inside that folder (your project).

PATH

A list of folders your computer searches when you type a program name like grok. Installers usually add Grok to PATH so the name works from any folder.

Keyboard shortcut / chord

Keys pressed together. Ctrl+O means hold Control (on Mac, often Control—not Command—unless we say Cmd) and press O. We always spell shortcuts out when they matter.

Grok Build words

Grok Build

An AI coding assistant that lives in your terminal. You describe a goal in English; it can read files, edit them, and run commands (with your permission).

Agent

Software that takes multi-step actions toward a goal—not just chat. Grok is an agent: it plans, uses tools, checks results, and continues.

TUI (Terminal User Interface)

The full-screen Grok interface inside the terminal: history above, typing box below, menus, colors. This is the normal way humans use Grok day to day.

Prompt

(1) The text box at the bottom where you type instructions. (2) The message you send (“fix the login bug”). Both meanings appear in this site.

Scrollback

The history area above the prompt. It shows your messages, Grok’s answers, and tool results (file edits, command output).

Turn

One round: you send a message, Grok works (possibly for a while), then finishes or waits for you. While a turn is running, Grok is “busy.”

Tool

An action Grok can take: read a file, edit a file, run a shell command, search the web, and more. Tools may ask for your approval first.

Session

One saved conversation with history. Sessions are stored on disk so you can leave and come back later.

Slash command

A special instruction that starts with /, like /help-style menus. Example: type /new and press Enter to start a fresh session. Not the same as chatting with the AI—these control Grok itself.

Context / context window

How much of the conversation and files Grok can “see” at once. Long chats fill it up. Commands like /compact free space by summarizing older parts.

Diff

A view of what changed in a file: lines added and removed. When Grok edits code, you can read the diff to understand the change.

Headless mode

Running Grok with a single prompt from the command line (often grok -p "…") without the interactive full-screen UI. Used for scripts and automation.

Always-approve (sometimes called YOLO)

A mode where Grok does not stop to ask permission for most tools. Faster, riskier. Only use on computers and projects you trust.

Software project words

Repository (repo)

Your project folder, often tracked by Git. “Open the repo” means open that project’s folder in the terminal.

Git

A common tool that records versions of your files so you can undo and share changes. Helpful with Grok so you can reverse bad edits.

Test / test suite

Small programs that check your code automatically. “Run the tests” means run a command (often npm test) that reports pass/fail.

Stack

The technologies your project uses (e.g. “vanilla JavaScript in the browser,” “Unity C#,” “React + Node”).

CI (Continuous Integration)

Automated checks that run on a server when you push code—tests, lint, builds. Headless Grok can plug into CI later; you do not need CI on day one.

Safety words

Permission prompt

A pause where Grok asks “May I edit this file?” or “May I run this command?” You choose allow or deny.

Agent Dashboard

A multi-session overview for jumping between Grok chats, dispatching work, and seeing what is running. Advanced—learn after your first ship.

Sandbox

Optional OS-level limits so Grok’s processes can only write certain folders. Extra protection for untrusted code.

Credentials / API key

Secrets that prove who you are. Treat them like passwords. Never paste them into public chat or commit them to Git.