Terminal agent

A terminal agent is an AI coding assistant that runs in the user's terminal — Claude Code, Aider, OpenAI Codex CLI — interacting with the file system and shell rather than an IDE editor.

Terminal agents in 2026 are the engineer's choice for delegated work — "run the tests, fix the failures, open a PR". The interaction model: user types a task, agent reads relevant files, plans, edits files, runs shell commands, reports. Differs from IDE agents in that there's no editor surface — diffs are previewed in the terminal, no inline autocomplete. Claude Code is the production leader for Anthropic-native; Aider is the OSS leader; OpenAI Codex (2026) is the cloud-based alternative. Best for engineers comfortable in CLI who want delegation rather than IDE autocomplete.

When to use terminal agent

• Delegated autonomous engineering tasks.
• Terminal-first engineering workflows.

Common mistakes

• Letting terminal agents run destructive commands without confirmation.
• No log retention — losing the trace of what the agent did.

FAQ

Related terms

• AI agent — An AI agent is a system where a language model autonomously plans and executes a sequence of tool calls to accomplish a goal.
• Agent loop — An agent loop is the repeating cycle of an AI agent — observe state, decide on an action (usually a tool call), execute, observe the result, and repeat — until a goal is reached or a stop condition fires.
• IDE agent — An IDE agent is an AI coding assistant embedded inside an integrated development environment — Cursor, Cline, Windsurf, Roo Code, GitHub Copilot agent mode — that can edit multiple files, run commands, and run tests autonomously from inside the editor.

Last updated: 2026-06-01. Raw markdown: https://promtable.com/glossary/terminal-agent.md.