Cross-Tool Token Metrics, Not Editor Lock-in

The short version: Continue

Verdict: SigRank does not replace Continue — it scores the operator driving it. Continue is a superb open-source IDE extension that brings AI autocomplete and chat into your editor, and it surfaces some token and cost information in its UI. That is useful when you live entirely inside Continue. The moment you also use Claude Code for agentic work, Copilot for inline completion, or Cursor for refactoring, those metrics fragment: each tool reports its own numbers, in its own format, locked to its own surface. There is no unified score.

SigRank is the platform-neutral layer that fixes that. It reads token telemetry from Continue, 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 extensions to use SigRank — you add it alongside whatever you already drive.

Feature comparison

The editor lock-in problem

Continue's metrics are real — but they are extension-scoped and extension-locked. The numbers live inside Continue, in Continue's format, visible only in the editor where Continue ran. They do not export. They do not compare to anyone outside Continue. And they vanish the day you try a different tool.

Most operators do not live in one extension. A realistic week: Continue for in-editor autocomplete and chat, Claude Code for agentic terminal work, Copilot for inline completions, maybe a Cursor refactor. Continue's metrics cover one slice of that week. Your actual efficiency is the union — and SigRank is the only layer that scores the union on a single axis.

Your score follows you, not the tool

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

Frequently asked questions

Does SigRank replace Continue?

No — SigRank is not an IDE extension. Continue is the open-source extension that brings AI autocomplete and chat into your editor; SigRank is the scoring layer that measures how efficiently you drive any AI tool, including Continue. You keep using Continue (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 extension stays; your efficiency gets measured.

Does Continue have token usage metrics?

Continue surfaces some token and cost information within its own chat and autocomplete UI — how many tokens a request consumed, context window usage. That is extension-scoped and extension-locked: the numbers live inside Continue, in Continue's format, visible only in your editor. 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 Continue.

Why does platform neutrality matter?

Because most operators do not use one tool. You might use Continue for in-editor autocomplete and chat, Claude Code for agentic terminal work, Copilot for inline completions, and Cursor for refactoring. Continue's metrics cover only the Continue slice; your actual efficiency is the union across all of them. SigRank is platform-neutral — it reads telemetry from Continue, 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 Continue specifically?

Yes. The SigRank CLI reads token telemetry from Continue'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 Continue sessions contribute to the same leaderboard rank as your Claude Code or Copilot sessions — unified, not siloed.

What is the difference between Continue and SigRank metrics?

Continue's metrics answer "how many tokens did this request use?" — 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. Continue tells you what you spent in one extension; SigRank tells you your Υ Yield (is signal compounding or burning?), your class tier, and your global rank among all operators regardless of editor. The first is a gauge; the second is a leaderboard.