Ampvsjcode
Generated from the two spec rows. Green marks the better value where a spec has a clear direction. Everything else is just different.
Amp
Amp Frontier Corporation (spun out of Sourcegraph) · Terminal agent
#111MCP
Panel
5.52 spec wins
- Reliability
- 5.7
- Usefulness
- 6.5
- Cost
- 5.2
- Longevity
- 4.8
“Twenty dollars a month buys twenty dollars of agent usage, which is at least an honest exchange rate.”
jcode
jcode · Terminal agent
#166OSSMCP
Panel
5.83 spec wins
- Reliability
- 5.2
- Usefulness
- 5.7
- Cost
- 8.3
- Longevity
- 4.2
“You can spawn several AI teammates in parallel, which is how you end up holding a standup with yourself.”
Spec by spec
| Spec | Amp | jcode |
|---|---|---|
| Architecture | ||
| Category | Terminal agent | Terminal agent |
| Runs | local, cloud, sandbox | local |
| Platforms | macos, linux, windows, web | macos, linux, windows |
| Context window | not documented | per-model, up to 1M where the model supports it |
| Protocols | ||
| MCP client | Yes | Yes |
| MCP server | No | No |
| Capabilities | ||
| Runs terminal commands | Yes | Yes |
| Multi-file edits | Yes | Yes |
| Git operations | Yes | Yes |
| Browser control | YesOrbs preinstall an `agent-browser` tool (https://ampcode.com/docs/orbs/customizing) and the agent "can install dependencies, run your app, spawn browsers, and test its work end to end". | No |
| Sandboxed execution | YesIsolation comes from cloud orbs, where "every orb thread gets a fresh, isolated environment" with a whole machine to itself; the local CLI has no container or OS-level sandbox. | Yes |
| Multi-agent orchestration | Yes | Yes |
| Headless / CI mode | YesNon-interactive `amp -x` execute mode is documented at https://ampcode.com/docs/cli/execute-mode. | No |
| Models | ||
| Backbone | OpenAI GPT-5.6, Anthropic Claude Fable 5.1, fast models | any |
| Bring your own model | YesAmp's Model Routing settings accept your own Anthropic API key for the workspace, but you still pick an Amp mode (low/medium/high/ultra) rather than an arbitrary model, endpoint or cloud deployment. | Yes |
| Local models | NoNo custom base URL, LLM gateway or local endpoint is documented; all inference is routed through Amp's own service. | Yes |
| Cost | ||
| Pricing model | mixed | byok |
| Starts at | $20/mo | n/a |
| Free tier | No | Yes |
| Bring your own key | Yes | Yes |
| Openness | ||
| Open source | No | Yes |
| License | proprietary | MIT |
| GitHub stars | n/a | 38 |
Which one would each critic pick
| Critic | Amp | jcode | Pick |
|---|---|---|---|
| El Juez | — | — | not enough reviews |
| El Amigo | 6.8 | 6.0 | Amp — Pick Amp if you want a sandbox without running Docker yourself; pick Claude Code or Codex CLI if you want a bigger included quota and one vendor. |
| El Crítico | 6.0 | 5.0 | Amp — Included usage denominated in dollars is a meter with a label on it, and a high-mode loop can spend the month in an afternoon before credits kick in. |
| El Profesor | 5.5 | 6.5 | jcode — A read-only Plan Mode produces a structured plan before any action, and the same tool implementations run locally, over SSH and inside Docker, which keeps behaviour identical across environments. |
| La Inversora | 6.0 | 5.0 | Amp — Spun out of Sourcegraph in December 2025, wrapping two labs' frontier models with a compute sandbox as the differentiator; the acquirer list writes itself. |
| La Jefa | 5.0 | 4.5 | Amp — Enterprise add-ons list SSO, directory sync and minimal data retention behind a contact form, and team pricing is pay-as-you-go; no seat number to put in a memo. |
| El Hacker | 4.0 | 8.0 | jcode — MIT, a single Go binary, any OpenAI-compatible endpoint including my own, and MCP servers declared in an mcp_servers block taking stdio and http entries. |
Picks are derived from each critic's own scores. Humans vote on matchups on the duels page.