Home → Compare
aico vs the alternatives
There are a lot of good AI coding agents. This page is about where aico is genuinely different, and — because a comparison that only flatters itself is worthless — where the alternatives are ahead.
Start with the honest part. Claude Code, OpenCode, OpenHands, Cline and Aider have between tens of thousands and a hundred thousand-plus users each. aico does not. If what you want is the best-supported tool with the largest community, the most extensions and the most Stack Overflow answers, one of those is the better choice today and it is not close.
What follows is about design decisions, not popularity.
At a glance
| aico | Claude Code | OpenCode | Aider | Cline | Cursor | |
|---|---|---|---|---|---|---|
| Open source | MIT | No | MIT | Apache | Apache | No |
| Bring your own key | Yes | Anthropic | Yes | Yes | Yes | Subscription |
| Runs local models | Yes | No | Yes | Yes | Yes | Limited |
| Terminal | Yes | Yes | Yes | Yes | No | No |
| Own web UI | Yes | No | Desktop app | No | In VS Code | Is an editor |
| Editor extension | VS Code | Yes | Yes | No | Yes | n/a |
| Inline completion | No | No | No | No | No | Yes |
| Community size | New | Very large | Very large | Large | Large | Very large |
Compiled August 2026 from each project's own documentation. Fast-moving software — check the source before relying on a row.
What is actually different about aico
It opens what it builds
This exists because of a specific failure: three models were asked for a single-file 3D space planner, and a keyword check scored two of them twelve features out of twelve. Opened in a browser, one threw on load and rendered nothing; the other was a shell. Nothing in the loop had ever run the thing.
VerifyApp opens the page in a real browser and reports what a
person would hit — uncaught exceptions, console errors, failed requests,
whether a <canvas> was ever painted, and whether named
controls do anything when clicked. Most agents check that the code looks
right. This one checks that it works.
The session is a log, not a chat buffer
Every fact is an append-only event with a sequence number. That is not architecture for its own sake — it is what makes a session resumable after a crash with real tool results rather than a summary, forkable from any message, and compactable without deleting anything. It is also why prompt caching actually hits: the cacheable prefix only ever grows.
One ledger for everything running
Sub-agents, background jobs, dev servers, scheduled runs and watchers share one record and one id space, and it survives a restart. You can ask "what is running, and what failed while I was away?" and get an answer. Limits — spend, deadline, idle — are set once and enforced by the platform rather than checked by the model. How that works.
It waits without burning turns
Asking most agents to wait for a build means a command, a sleep, and another command — a full turn and a full prompt per check. aico registers a watcher and stops; the platform wakes it. One turn to set, one to be woken by.
It can be driven by another AI
aico mcp-serve speaks MCP on stdin and stdout, so Claude Code or
any MCP client can delegate a task to it and collect the result. Nothing
listens on a port. Several tools consume MCP servers; being one is
less common.
In VS Code, deliberately thin
The extension does not reimplement the agent. aico's server already owns runs, survives a closed tab and ships the whole workspace, so the extension starts it against your open folder, embeds that workspace in a panel, and adds the three things an editor can do that a browser cannot:
- Ask about a selection — highlight code, press Ctrl+Alt+A, and the file and line numbers go with the question, so the agent is not sent hunting for what your editor already knew.
- Background work in the status bar — a run started an hour ago, or a scheduled job that failed overnight, without opening anything.
- Server lifecycle — started for the folder you have open, stopped when you are done.
That is the whole of it. Rebuilding the conversation UI natively would duplicate several thousand lines to arrive somewhere worse, and there is no inline-completion feature — that is a different product, and Cursor and Copilot do it well.
Not on the Marketplace yet; it is built from the repository.
Where the alternatives are ahead
| If you want… | Use |
|---|---|
| The largest community, most extensions, most answers when stuck | OpenCode or Claude Code |
| Disciplined, git-native editing where every change is a reviewable commit | Aider |
| To stay inside VS Code, with an extension marketplace | Cline |
| A polished editor with inline completion and a company behind it | Cursor |
| A managed cloud service, or Kubernetes deployment for a team | OpenHands |
aico has no hosted service and no plan for one. There is a VS Code extension, but it is a thin one — it starts the server, embeds the same workspace in a panel, and adds the few things an editor can do that a browser cannot. It is not a second implementation of the agent, and it is not an inline-completion tool.
Who it is actually for
- You want to keep your keys and pay providers directly, or run a local model.
- You want the agent to prove web work runs, not assert that it does.
- You run long or background work and want to see and bound it.
- You want to read the code that is running as you — it is MIT and heavily commented about why.
If none of those is a live problem for you, one of the tools above is probably the better pick, and saying so is more useful than pretending otherwise.