agentboards.org
Compare/Amp vs FuXi

AmpvsFuXi

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.5
1 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.”

FuXi
FUXI · Terminal agent
#90MCP
Panel
5.8
4 spec wins
Reliability
5.0
Usefulness
6.5
Cost
7.3
Longevity
4.3

“More than fifty built-in tools in one binary, which is either thoroughness or the longest permission prompt in this category.”

Spec by spec

SpecAmpFuXi
Architecture
CategoryTerminal agentTerminal agent
Runslocal, cloud, sandboxlocal
Platformsmacos, linux, windows, webmacos, linux, windows
Context windownot documentednot documented
Protocols
MCP clientYesYes
MCP serverNoYes
Capabilities
Runs terminal commandsYesYes
Multi-file editsYesYes
Git operationsYesYes/commit and /review create commits, review code and open pull requests.
Browser controlYesOrbs 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". Yes
Sandboxed executionYesIsolation 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. No
Multi-agent orchestrationYesYes
Headless / CI modeYesNon-interactive `amp -x` execute mode is documented at https://ampcode.com/docs/cli/execute-mode. Yes`fuxi setup-token` is documented specifically for headless and CI use.
Models
BackboneOpenAI GPT-5.6, Anthropic Claude Fable 5.1, fast modelsany OpenAI-compatible provider, Anthropic, Gemini, Amazon Bedrock, Google Vertex
Bring your own modelYesAmp'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 modelsNoNo custom base URL, LLM gateway or local endpoint is documented; all inference is routed through Amp's own service. YesA custom base_url is documented through config, the FUXI_BASE_URL environment variable and the -b/--base-url flag, which covers a locally hosted OpenAI-compatible server.
Cost
Pricing modelmixedbyok
Starts at$20/mo$0/mo
Free tierNoYes
Bring your own keyYesYes
Openness
Open sourceNoNo
Licenseproprietaryproprietary
GitHub starsn/a3,350

Which one would each critic pick

CriticAmpFuXiPick
El Juez——not enough reviews
El Amigo6.86.5Amp — 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ítico6.05.3Amp — 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 Profesor5.56.3FuXi — Classifying shell commands by parsing them into a syntax tree is the correct method; pattern matching on command strings is what everyone else does and it is defeated by quoting.
La Inversora6.05.3Amp — 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 Jefa5.05.0no preference
El Hacker4.06.5FuXi — Closed source, but FUXI_BASE_URL or the -b flag points it at any OpenAI-compatible endpoint, which includes the server running on my own machine.

Picks are derived from each critic's own scores. Humans vote on matchups on the duels page.

Want a third column? The compare tool handles any two agents. Three-way comparisons are on the roadmap once the spec rows are all verified.