# Terminal (command line)

> VI: https://5ac.vn/wiki/terminal/ · EN: https://5ac.vn/en/wiki/terminal/ · lang: en · spec_as_of 2026-10-19 (spec no formal spec) · cluster C21

The text-only work window — type a command, the shell interprets, output returns as words. The native habitat of coding agents and the first landing point of AI on a Linux desktop.

---
## Definition

A terminal is the text-only work window: you type a command, the shell interprets it, and the result comes back as printed words. On Linux, what people call the terminal is really a terminal emulator — the Omarchy review lists Foot, Alacritty, Ghostty and Kitty, each with its own configuration and color scheme, and the default switched to Foot from release v4.0.0. The point that matters in the AI era: the terminal is the coding agent's native habitat. Because everything there is text, an agent can drive the machine without looking at pixels — running commands, reading files, watching output return. The "three species of agents" piece names the design in Pi: a minimal terminal harness with an agent loop of about 418 lines, very fast, self-extending, and terminal-only.

## Mechanism

A working session has three layers: the command you type, the shell that interprets it, the text that comes back. Agents walk exactly that path, which means an agent's reach equals the rights of the account running the shell — powerful, and harder to see than a mouse click. Compared with the desktop interface:

| Dimension | Terminal | Desktop interface |
| --- | --- | --- |
| Who operates it well | developers, broad rights | whole team, including non-technical staff |
| What agents do there | files, processes, builds, source code | email, spreadsheets, CRM, chat windows |
| Signature risk | excludes non-technical people from the workflow | wide touch rights, needs an approval layer |

The Windows-Native piece states why 5ac wants agents to leave the terminal: if an AI agent only lives in a terminal or on a server, the business still needs a translation layer between real users and the automation system. Terminals excel at technical work, while business processes happen in email, spreadsheets and CRM.

## Application context

The terminal is also the operating system's front door for AI users: Omarchy builds the coding agent into the desktop itself — nine lazy-installed agents, a keyboard shortcut or typing "a" opens an agent in its own window, and themes sync into it. One reading warning: "Terminal-Bench" is the name of a benchmark for agent coding with command-line tools (5ac's pricing strategy piece cites GPT-5.5 scoring 82.7% on it), not a kind of terminal window — do not merge the two when researching.

## Sources fetched

- [Omarchy: The Linux desktop that replaces your MacBook or Windows machine](/en/blog/omarchy-linux-desktop-replaces-macbook-windows/) — the emulator list, Foot as default from v4.0.0, agents launched from the terminal — accessed 2026-10-19
- [Codex, Pi, Hermes — Three Species of AI Agents, Not Three Rivals](/en/blog/three-species-of-ai-agents-codex-pi-hermes/) — Pi as a minimal terminal harness, ~418-line agent loop, terminal-only — accessed 2026-10-19
- [Windows-Native Desktop AI Agents: The New Automation Layer for Small Businesses](/en/blog/desktop-ai-agents-windows-native-small-business-automation/) — why terminal-only agents still leave a translation gap — accessed 2026-10-19
- [AI Agent Product Strategy in the Price War — The Model-Agnostic Advantage](/en/blog/chien-luoc-san-pham-ai-gia-re-doanh-nghiep/) — GPT-5.5 at 82.7% on Terminal-Bench, usage of the benchmark — accessed 2026-10-19

## Related

- [Coding agent](/en/wiki/coding-agent/)
- [Desktop agent](/en/wiki/desktop-agent/)
- [AI Agent](/en/wiki/ai-agent/)
- [Business automation](/en/wiki/business-automation/)
