AI for Research Efficiency, episode 1: Why the command line Narration: an AI-generated voice (ElevenLabs). [0:00] Three letters In 1985, this is how you started Windows. You typed three letters. The pictures ran on top of the command line. They've been getting better ever since. And the command line never left. AI for Research Efficiency. Episode 1: Why the command line. In this episode: what the command line is, why an AI agent can do more there than in a browser tab, and what stays with you. [0:36] Two ways into one computer Your desktop and the command line are two ways into the same computer. When you click, the desktop asks the operating system to open, copy or rename something. When you type a command, you ask it directly. The window you type in is called a terminal. The line where you type is the prompt. The pictures are there for people. Underneath, it's the same files and the same programs. [1:04] The same task, twice Say you have five data files from a field study, and you need the number of rows in each one. With the mouse, you open each one and scroll to the bottom. With one command, the computer counts them all and lists the answers. Five files or 5,000, the command is the same. The desktop can do some of this too. The difference is scale, and an answer in text that the next step can use. [1:40] You are the hands Now add an AI. In a browser tab, the assistant works on copies you upload. You carry the files in, and you carry the answers back out. You are its hands. To be fair, the browser apps can now run code, search the web and read your cloud drive. What a browser tab can't do is reach the files on your computer. [2:07] An agent with hands of its own On the command line, an AI agent has hands of its own. You ask in plain words. It opens your folder, picks a command, runs it, and reports back. Here it even checked the count a second way, and spotted a stray period in one file's participant codes. [2:36] Why text suits an agent Why does the command line suit an agent so well? An agent that drives a screen works from pictures. It takes a screenshot, decides where to click, then takes another. Its makers say that can be slow, and a click can land in the wrong place. On the command line, the agent reads and writes text, which is what these models do best. Its answers are exact, and it can search a whole folder and bring back only what matters. [3:07] What stays with you What stays with you: the question, the judgment and the permissions. At first, have the agent ask before each step, and read what it wants to do. When you trust it with a task, switch on its automatic mode, and the work goes much faster. Either way, you check the results against your sources. [3:31] Review and next So: the desktop and the command line reach the same computer. In a browser tab, you are the AI's hands. On the command line, it has its own. Next, we'll open a terminal and get ready to install your first agent.