Each page says how its figures were obtained before it shows them: measured head to head on the same cases, set beside the other tool’s published figure on a different sample, or not benchmarked at all. Each keeps the rows where the other tool wins, and every figure is on the benchmarks page first.
Pixel vs GitNexus
Measured head to head
A code graph for coding agents, served as MCP tools, with Cypher queries over the graph.
Where GitNexus wins: Cypher queries, taint analysis, API route maps, and callers in Ruby.
Pixel vs Serena
Not benchmarked
An MCP toolkit that gives an agent an IDE's symbol-level retrieval and editing, through language servers or a JetBrains plugin.
Where Serena wins: type-resolved references, and symbol-level editing and refactoring through the language server.
Pixel vs CodeGraphContext
Not benchmarked
An MCP server and CLI that indexes local code into a graph database, queried for callers, call chains and raw Cypher.
Where CodeGraphContext wins: a graph database of your choice, raw Cypher queries, an HTML graph view and code complexity reports.
Pixel vs code-graph-rag
Not benchmarked
A knowledge graph of a codebase in Memgraph, queried and edited in plain English through an LLM that writes the Cypher.
Where code-graph-rag wins: plain-English questions turned into Cypher, code edits through the agent, runtime traces and data-flow checks.
Pixel vs Claude Context
Not benchmarked
Zilliz's MCP plugin for semantic code search: code split along its syntax tree, embedded, and stored in Milvus or Zilliz Cloud.
Where Claude Context wins: a managed cloud vector store, a choice of embedding provider, and a VS Code extension.
Pixel vs graphify
Not benchmarked
A skill that turns a codebase, with its docs, schemas, PDFs and media, into a knowledge graph an agent can query.
Where graphify wins: non-code inputs (docs, PDFs, media, database schemas), community clustering and an interactive graph view.
Pixel vs shunt
Published figures, different samples
Spotify's plugin that hands an agent's large file reads to a worker model, a second model on the bill.
Where shunt wins: its worker also writes boilerplate code, which Pixel does not.
Pixel vs Jev
Published figures, different samples
A dedicated model for coding judgement calls, scored on its own benchmark, JevBench.
Where Jev wins: its score covers all 56 of its coding items, where Pixel's run covers only the 14 public ones.
Pixel vs semble
Measured head to head
A search tool that finds code from a question in plain English, with a small context footprint.
Where semble wins: natural-language search, and a lighter context on every turn.
Pixel vs grep
Measured from the baseline
The line search every agent already knows, and the one it reaches for first: grep, ripgrep, the agent's own search tool.
Where grep wins: nothing to install and no index to build: it runs on any file, anywhere, the moment it exists.
Pixel vs a language server
Not benchmarked
The type-aware engine behind an editor's go-to-definition and find-references: rust-analyzer, tsserver, gopls and the like.
Where a language server wins: it resolves types, so its callers and references are more exact than a syntax graph's.
Pixel vs an editor's index
Not benchmarked
The index an editor or an AI editor builds for its own search and its own agent.
Where an editor's index wins: it is already there, with nothing to install or wire.