Augment CodevsTabby
Generated from the two spec rows. Green marks the better value where a spec has a clear direction. Everything else is just different.
Augment Code
Augment Code · IDE extension
#32MCP
Panel
6.38 spec wins
- Reliability
- 6.3
- Usefulness
- 7.0
- Cost
- 5.2
- Longevity
- 6.5
“Charges the model's list price plus a 40 percent service fee, which is at least a markup you can read without a lawyer.”
Tabby
TabbyML · IDE extension
#107OSS
Panel
6.75 spec wins
- Reliability
- 6.7
- Usefulness
- 5.8
- Cost
- 7.3
- Longevity
- 7.0
“It ships a Vim extension, so the two least agreeable crowds in software finally have something in common.”
Spec by spec
| Spec | Augment Code | Tabby |
|---|---|---|
| Architecture | ||
| Category | IDE extension | IDE extension |
| Runs | local, cloud | local |
| Platforms | macos, linux, windows | macos, linux, windows |
| Context window | not documented | not documented |
| Protocols | ||
| MCP client | Yes | No |
| MCP server | Yes | No |
| Capabilities | ||
| Runs terminal commands | Yes | No |
| Multi-file edits | Yes | No |
| Git operations | Yes | No |
| Browser control | NoAuggie ships web-search and web-fetch tools only, so it can read pages but cannot drive a browser; browser automation requires adding a third-party MCP server. | No |
| Sandboxed execution | YesCosmos cloud environments are built from a Docker base image you pick from any public registry and each session starts from a fresh isolated snapshot; the local Auggie CLI has no sandbox, and self-hosted daemons isolate only via per-session Git worktrees. | No |
| Multi-agent orchestration | Yes | No |
| Headless / CI mode | Yes`auggie --print` runs non-interactively for scripts and CI, and Augment publishes GitHub Actions wrappers for PR descriptions and reviews. | No |
| Models | ||
| Backbone | Claude, GPT, Gemini, GLM, Kimi | any |
| Bring your own model | NoModel choice is limited to Augment's curated list via /model or --model; no custom base URL, LLM gateway, or Bedrock/Vertex/Azure deployment is documented. | Yes |
| Local models | NoNo local or OpenAI-compatible endpoint is documented; inference always runs through Augment. | Yes |
| Cost | ||
| Pricing model | mixed | free |
| Starts at | $20/mo | n/a |
| Free tier | No | Yes |
| Bring your own key | NoLLM usage is billed by Augment as provider cost plus a 40% service fee; supplying your own provider key or cloud account is not documented. | No |
| Openness | ||
| Open source | No | Yes |
| License | proprietary | Apache-2.0, with the ee/ directory under a separate enterprise licence |
| GitHub stars | 283 | 33,886 |
Which one would each critic pick
| Critic | Augment Code | Tabby | Pick |
|---|---|---|---|
| El Juez | — | — | not enough reviews |
| El Amigo | 7.0 | 7.0 | no preference |
| El Crítico | 6.0 | 6.3 | Tabby — It completes, chats and answers, and it does not edit across files or run anything, so anyone comparing it to an agent on this board is comparing different categories. |
| El Profesor | 6.5 | 6.8 | Tabby — The index spans repositories, issues and merge requests, so retrieval covers the discussion around code rather than the code alone, which is an unusual and defensible scope choice. |
| La Inversora | 7.0 | 6.3 | Augment Code — Publishing a 40 percent service fee is either transparency or a confession, and exposing the index over MCP is a hedge toward becoming a component in other people's agents. |
| La Jefa | 6.8 | 6.0 | Augment Code — SOC 2 Type II, CMEK, audit trails and training exclusion on every plan, pooled usage to 50 seats, SSO and SCIM at Enterprise; approved with a spend ceiling. |
| El Hacker | 4.3 | 8.0 | Tabby — Apache-2.0 except the ee/ directory, which carries its own licence, and that carve-out is exactly the pattern I complain about, softened by a real OpenAPI surface. |
Picks are derived from each critic's own scores. Humans vote on matchups on the duels page.