Amazon Q DevelopervsAugment Code
Generated from the two spec rows. Green marks the better value where a spec has a clear direction. Everything else is just different.
Amazon Q Developer
Amazon Web Services · IDE extension
#147MCP
Panel
6.03 spec wins
- Reliability
- 6.0
- Usefulness
- 5.7
- Cost
- 6.2
- Longevity
- 6.3
“It ships a plugin for Eclipse, which tells you precisely which enterprise this was built for.”
Augment Code
Augment Code · IDE extension
#32MCP
Panel
6.34 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.”
Spec by spec
| Spec | Amazon Q Developer | Augment Code |
|---|---|---|
| Architecture | ||
| Category | IDE extension | IDE extension |
| Runs | local, cloud | local, cloud |
| Platforms | macos, linux, windows, web | macos, linux, windows |
| Context window | not documented | not documented |
| Protocols | ||
| MCP client | Yes | Yes |
| MCP server | No | Yes |
| Capabilities | ||
| Runs terminal commands | Yes | Yes |
| Multi-file edits | Yes | Yes |
| Git operations | Yes | Yes |
| Browser control | No | 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. |
| Sandboxed execution | No | 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. |
| Multi-agent orchestration | No | Yes |
| Headless / CI mode | No | Yes`auggie --print` runs non-interactively for scripts and CI, and Augment publishes GitHub Actions wrappers for PR descriptions and reviews. |
| Models | ||
| Backbone | Claude | Claude, GPT, Gemini, GLM, Kimi |
| Bring your own model | No | 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. |
| Local models | No | NoNo local or OpenAI-compatible endpoint is documented; inference always runs through Augment. |
| Cost | ||
| Pricing model | subscription | mixed |
| Starts at | $19/mo | $20/mo |
| Free tier | Yes | No |
| Bring your own key | No | 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. |
| Openness | ||
| Open source | No | No |
| License | proprietary | proprietary |
| GitHub stars | 1,982 | 283 |
Which one would each critic pick
| Critic | Amazon Q Developer | Augment Code | Pick |
|---|---|---|---|
| El Juez | — | — | not enough reviews |
| El Amigo | 6.3 | 7.0 | Augment Code — Use Augment when the codebase is the problem; on a small repo you are paying a markup for an index you do not need, so pick Claude Code there. |
| El Crítico | 5.5 | 6.0 | Augment Code — The meter is cost-plus with no bring-your-own-key, so once included usage is gone you pay the model's list price plus a service fee with no way around it. |
| El Profesor | 6.0 | 6.5 | Augment Code — Two benchmark claims, one an ensemble and one a controlled comparison on the vendor's own harness; neither should be read against the public leaderboards. |
| La Inversora | 7.0 | 7.0 | no preference |
| La Jefa | 7.0 | 6.8 | Amazon Q Developer — Nineteen dollars per user per month is $1,140 for sixty, the admin controls sit in that tier, and the invoice arrives from a supplier legal has already cleared. |
| El Hacker | 4.5 | 4.3 | Amazon Q Developer — Proprietary, no key of my own and no local weights, but the MCP config is a real file at ~/.aws/amazonq/agents/default.json that I can version and diff. |
Picks are derived from each critic's own scores. Humans vote on matchups on the duels page.