AI coding agent knowledge base

DevThrottle maintains a source-of-truth knowledge base for command-line coding agents. The public coding agents directory is the reader-friendly surface; the research corpus behind it tracks capabilities, source links, terminal behavior, history capture, strengths, and limitations.

What we track

For each serious CLI agent we track installation, authentication, model support, file editing, shell execution, git workflow, MCP and extension support, sub-agents, permission controls, session persistence, telemetry, and DevThrottle integration risks. The goal is to make cross-agent differences concrete instead of relying on vague claims that every agent can "write code."

Current primary agents

The deep-research set now covers 35 CLI or CLI-capable agents: Codex CLI, Claude Code, Antigravity CLI, Cursor CLI, Aider, OpenCode, Goose, Amp, GitHub Copilot CLI, Kiro CLI, Kimi Code CLI, Grok Build CLI, Crush, Codebuff, ForgeCode, Qwen Code, Devin CLI, Factory Droid CLI, Auggie CLI, Cline CLI, gptme, Open Interpreter, Plandex, SWE-agent, mini-SWE-agent, Trae Agent, Warp Agents, Rovo Dev, Pi, OpenHands, Potpie, Mistral Vibe, Letta Code, Amazon Q Developer CLI lineage, and the Gemini CLI transition. Additional CLI agents are tracked as candidates and promoted when their terminal workflow is real enough to evaluate.

How this reaches the website

The concise public matrix lives at AI Coding Agents Matrix. The deeper research lives in the repository underdocs/research/agents, where we keep source links, verification dates, and DevThrottle-specific integration notes.

Why it matters

DevThrottle is vendor-neutral. Users need to know which agent is strongest for their workflow, which one is safest to run unattended, which one exposes usable history, and which one is likely to block inside a full-screen terminal UI. That knowledge becomes product guidance, newsletters, support answers, and future agent-expert behavior inside DevThrottle.