Terminal tools
Tools tagged Terminal.
Tools tagged Terminal
This page updates when a tool gains or loses the tag in the master file.
Aider
AI pair programmer in the terminal that edits code in local git repositories with many LLM providers.
Amp Code
Amp is a frontier coding agent for terminal, web and mobile control with pay-as-you-go pricing and no markup for individuals.
Claude Code
Agentic coding tool that lives in the terminal, understands your codebase and handles routine tasks/git workflows.
Codebuff
Codebuff is an AI coding assistant for the terminal that edits codebases from natural language instructions and can run commands; the GitHub page describe…
Gemini CLI
Open-source command-line AI agent that brings Gemini into the terminal for coding, debugging, testing and workflow tasks.
Kilo Code
Open-source AI coding agent for VS Code, JetBrains, CLI and cloud with 500+ models, BYOK and zero markup claims.
OpenCode
Open source agent that helps write code in terminal, IDE, or desktop with LSP and multi-session support.
OpenHands
Open-source platform for coding agents that can plan, write, apply changes and automate software tasks.
Plandex
Plandex is an open-source terminal-based AI development tool designed to plan and execute large coding tasks that touch many files and require long contex…
Editorial purpose for Terminal tools
This page was flagged by the v45 audit as thin during proof review, so it now carries a proof review editorial repair layer until a final public article can be written.
How this page should help users
The page path tags / terminal should help visitors understand the tool, category, tag, comparison or alternative intent before they move to another page. For public launch, the content should explain who the page is for, what decision the reader is trying to make, what alternatives or related tools deserve attention, and which facts still need screenshots or official-source verification. This prevents doorway-style pages, duplicate canonical confusion and empty tag archives.
Before indexing, add unique evidence for pricing, platform support, free-plan limits, login requirements, export or watermark behavior, country availability, screenshots and comparison logic. The current repair text is deliberately marked proof review and should not be treated as final SEO copy. It exists so the staging build is honest about weak pages while giving editors a clear structure to complete them.
For Terminal tools, the final version should include a short verdict, a table of recommended tools or pages, internal links to alternatives and comparison hubs, a proof checklist, and a clear warning where data is not yet verified. Avoid unsupported claims such as invented ratings, fake screenshots, fake prices or claims that a tool is free/no-watermark without testing.