What it means
The terminal accepts structured commands (git, npm, curl) that execute on the user’s machine or remote environment, often invoked by the agent via tool use.
Why designers should care
CLI agent UX needs command previews, allowlists for destructive ops, readable logs, and the same human-in-the-loop gates as GUI actions, not a hidden shell the user never sees.
Example
Cursor shows each terminal command in the agent timeline before run; destructive git operations require explicit approval while read-only ls commands proceed automatically.
Common mistakes
- Agents running shell commands with no preview or audit trail.
- Raw terminal dumps with no plain-language summary for non-engineers.
- Inconsistent approval rules between GUI tool calls and CLI commands.
Frequently asked questions
What is CLI (Command-Line Interface)?
A CLI is a text-based interface where users (or agents) run commands in a terminal instead of clicking through GUI screens.
Why should designers care about CLI (Command-Line Interface)?
CLI agent UX needs command previews, allowlists for destructive ops, readable logs, and the same human-in-the-loop gates as GUI actions, not a hidden shell the user never sees.
What are common mistakes with CLI (Command-Line Interface)?
Agents running shell commands with no preview or audit trail; Raw terminal dumps with no plain-language summary for non-engineers; Inconsistent approval rules between GUI tool calls and CLI commands.