How we group the open-source coding agents: terminal pair programmers, editor extensions, sandboxes, vendor CLIs

Open SourceLewis Cheng3 repliesThis topic is about Aider-AI/aider

Lewis ChengMember#1

"AI coding agent" covers tools that do very different things, and the comparison pages here needed a grouping before they could be fair. The one we settled on, with the projects that anchor each group:

Terminal pair programmers. You drive, the tool edits. Aider (Apache-2.0) is the reference: it builds a repository map so the model knows what exists without reading everything, makes edits as diffs, and commits each change to git so you can undo with git revert. It works with any model you have a key for.

Editor extensions. Cline (Apache-2.0) in VS Code, with a Plan mode (discuss) and an Act mode (edit and run), and MCP support for connecting tools. Continue was the other anchor here until its acquisition by Cursor; /compare/cline-vs-continue is still up because the code is.

Autonomous sandboxes. OpenHands (MIT, formerly OpenDevin): the agent runs in a container with its own shell and browser, and works a task to completion with less interaction. Different trust model; you review the result, not each step.

Vendor CLIs that are open source. Gemini CLI (Apache-2.0) and Codex CLI (Apache-2.0, the openai/codex repository): terminal agents from model vendors, open source but tied to their models in practice.

Pairs across the groups: /compare/aider-vs-cline, /compare/aider-vs-openhands, /compare/codex-vs-gemini-cli, /compare/aider-vs-opencode. Vocabulary: /learn/ai-coding-agent.

The grouping is ours and arguable. If a project is in the wrong box, say so here.

3 replies

JimmyMember#2

On Continue: the homepage reads "Continue (acquired by Cursor)" and speaks in the past tense, but the repository is still public under its licence, so the extension can be built and used. Whether it gets updates for new model APIs is the open question for anyone still on it. The comparison page should probably carry that note.

Hysen YanStaff#3

The axis the grouping hides is cost, and it changes the choice as much as the interaction model. Aider, Cline and OpenHands bill you through whichever model API you plug in; the vendor CLIs bill through that vendor's plan or API. For a long task an autonomous agent can burn through tokens you did not watch. /tools/llm-cost-calculator with the agent's typical context size (large: it carries the repository map or the file set in every call) is worth running before adopting one for a team.

EdenMember#4

And the connective tissue across all four groups is MCP: Cline, the vendor CLIs and increasingly the others connect to tools the same way. /tools/mcp-config-generator writes the server entry, and /ai/mcp lists the servers tracked here. If you are choosing an agent, "can it use the MCP servers I already have" is now a fair question to ask of each box.