Does SigRank replace Sourcegraph Cody?

No — SigRank is not a code-aware assistant. Sourcegraph Cody understands your entire codebase and brings that context to AI-generated answers; SigRank is the scoring layer that measures how efficiently you drive any AI tool, including Cody. You keep using Cody (or Claude Code, or Copilot) and run the SigRank CLI alongside it. SigRank reads your token telemetry locally, computes your Υ Yield, and publishes a signed snapshot to the leaderboard. Your assistant stays; your efficiency gets measured.

Does Cody have token usage metrics?

Cody surfaces some token and context information inside its extension UI — how much context was pulled in, how many tokens a request consumed. That is extension-scoped and extension-locked: the numbers live inside Cody and do not leave it. SigRank reads the same underlying token flow but computes the full cascade architecture (Υ Yield, compression ratio, SNR, Leverage, Velocity), assigns a class tier, and lets you compare against every other operator on the board — including ones who never touch Cody.

Why does platform neutrality matter?

Because most operators do not use one tool. You might use Cody for codebase-aware questions, Claude Code for agentic tasks, and Cursor for refactoring. Cody's metrics cover only the Cody slice; your actual efficiency is the union across all of them. SigRank is platform-neutral — it reads telemetry from Cody, Claude Code, Copilot, Cursor, ChatGPT, Gemini, and 15+ others, scores them on the same cascade axis, and gives you one comparable rank. Your score follows you across tools, not the other way around.

Can I use SigRank with Cody specifically?

Yes. The SigRank CLI reads token telemetry from Cody's local logs the same way it reads Claude Code's (ccusage is bundled for Claude Code; additional readers cover other platforms). Run `sigrank enroll` to create your operator identity, then `sigrank submit` to score and publish. Your Cody sessions contribute to the same leaderboard rank as your Claude Code or Copilot sessions — unified, not siloed.

What is the difference between Cody and SigRank metrics?

Cody's metrics answer "how much codebase context did this request pull in?" — a per-request, extension-local view. SigRank's metrics answer "how efficiently does this operator drive AI across all their tools?" — a cascade-level, cross-platform view. Cody tells you what context you used in one assistant; SigRank tells you your Υ Yield (is signal compounding or burning?), your class tier, and your global rank among all operators regardless of assistant. The first is a gauge; the second is a leaderboard.

◈ SigRank vs Sourcegraph Cody

Operator Scoring, Not Codebase Context

Sourcegraph Cody brings codebase context to AI. SigRank is platform-neutral — scores how efficiently you drive Cody, Claude Code, Copilot, Cursor, and 15+ others. Your score follows you across tools.

The short version: Sourcegraph Cody

No, SigRank does not replace Sourcegraph Cody. Cody is a code-aware AI assistant — it indexes your entire codebase and brings that context to AI-generated answers and completions. That is a tool, not a metric. Cody surfaces some token and context information inside its extension, but it does not compute cascade efficiency, does not assign a class tier, and does not rank you against operators who use other tools. It brings context to AI; it does not measure how efficiently you drive AI.

SigRank is the platform-neutral layer that fixes that. It reads token telemetry from Cody, Claude Code, Copilot, Cursor, and 15+ other tools, scores them all on the same cascade axis (Υ Yield), and gives you one rank that follows you across tools. You don't switch assistants to use SigRank — you add it alongside whatever you already drive.

Feature comparison

Feature	Cody	SigRank
What it is	Code-aware AI assistant (codebase context)	Platform-neutral operator scoring layer
Token usage tracking	Limited (extension-scoped)	Yes (cascade-derived)
Cascade efficiency score (Υ = cache_read × output / input²)	No	Yes
Compression ratio + SNR + Leverage + Velocity	No	Yes
Class tier (IGNITER to ARCH+)	No	Yes
Global operator leaderboard	No	Yes
Works across Cody + Claude Code + Cursor + 15+	No (Cody only)	Yes
Score follows you across tools	No	Yes
Operator profiles + head-to-head compare	No	Yes
ed25519-signed snapshot submission	No	Yes
MCP server for agent integration	No	Yes
Privacy-preserving (token counts only)	Yes	Yes

Context is not measurement

Cody's job is to understand your entire codebase and bring that context to AI-generated answers. It does that well. But codebase context is a feature, not a metric. Cody surfaces some token and context information inside its extension UI, but those numbers are extension-scoped and extension-locked — they live inside Cody and do not leave it. The moment you want to know how efficiently you are driving AI — not just how much context was pulled in — Cody has nothing to say.

Most operators do not use one tool. A realistic week: Cody for codebase-aware questions, Claude Code for agentic multi-file tasks, Cursor for refactoring, maybe a Copilot inline completion. Cody covers only the codebase-context slice. Your actual efficiency is the union — and SigRank is the only layer that scores the union on a single axis.

The cascade is tool-agnostic

Υ = cache_read × output / input² is computed from four token integers that every AI tool produces — input, output, cache-read, cache-write. The math does not care which assistant generated them. An operator who reuses context efficiently in Cody scores the same way as one who does it in Claude Code. The cascade is the universal substrate.

Your score follows you, not the tool

SigRank's operator identity is tied to you, not to your assistant. Enroll once, submit from any tool, and every signed snapshot feeds the same leaderboard rank. Switch from Cody to Claude Code to Copilot over a month and your Υ trajectory reflects your driving across all three — not three disconnected per-tool gauges. That is the difference between a metric and a reputation.

Frequently asked questions

Does SigRank replace Sourcegraph Cody?: No — SigRank is not a code-aware assistant. Sourcegraph Cody understands your entire codebase and brings that context to AI-generated answers; SigRank is the scoring layer that measures how efficiently you drive any AI tool, including Cody. You keep using Cody (or Claude Code, or Copilot) and run the SigRank CLI alongside it. SigRank reads your token telemetry locally, computes your Υ Yield, and publishes a signed snapshot to the leaderboard. Your assistant stays; your efficiency gets measured.
Does Cody have token usage metrics?: Cody surfaces some token and context information inside its extension UI — how much context was pulled in, how many tokens a request consumed. That is extension-scoped and extension-locked: the numbers live inside Cody and do not leave it. SigRank reads the same underlying token flow but computes the full cascade architecture (Υ Yield, compression ratio, SNR, Leverage, Velocity), assigns a class tier, and lets you compare against every other operator on the board — including ones who never touch Cody.
Why does platform neutrality matter?: Because most operators do not use one tool. You might use Cody for codebase-aware questions, Claude Code for agentic tasks, and Cursor for refactoring. Cody's metrics cover only the Cody slice; your actual efficiency is the union across all of them. SigRank is platform-neutral — it reads telemetry from Cody, Claude Code, Copilot, Cursor, ChatGPT, Gemini, and 15+ others, scores them on the same cascade axis, and gives you one comparable rank. Your score follows you across tools, not the other way around.
Can I use SigRank with Cody specifically?: Yes. The SigRank CLI reads token telemetry from Cody's local logs the same way it reads Claude Code's (ccusage is bundled for Claude Code; additional readers cover other platforms). Run `sigrank enroll` to create your operator identity, then `sigrank submit` to score and publish. Your Cody sessions contribute to the same leaderboard rank as your Claude Code or Copilot sessions — unified, not siloed.
What is the difference between Cody and SigRank metrics?: Cody's metrics answer "how much codebase context did this request pull in?" — a per-request, extension-local view. SigRank's metrics answer "how efficiently does this operator drive AI across all their tools?" — a cascade-level, cross-platform view. Cody tells you what context you used in one assistant; SigRank tells you your Υ Yield (is signal compounding or burning?), your class tier, and your global rank among all operators regardless of assistant. The first is a gauge; the second is a leaderboard.

Keep Cody. Add the score that follows you.

Cody brings codebase context to AI. SigRank measures your driving — across Cody and every other tool you use. Install the CLI, submit a signed snapshot, and get a rank that doesn't reset when you switch tools.

Calculate your Υ Yield See the leaderboard