Cross-Tool Token Metrics, Not Editor Lock-in
Continue is an open-source IDE extension for AI autocomplete and chat. SigRank is platform-neutral — works with Continue, Claude Code, Copilot, Cursor, and 15+ others. Your score follows you across tools.
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
| Feature | Continue | SigRank |
|---|---|---|
| What it is | Open-source IDE extension for AI autocomplete and chat | Platform-neutral operator scoring layer |
| Token tracking | Limited (extension-scoped) | Yes (cascade-derived) |
| Cascade efficiency score (Υ = cache_read × output / input²) | No | Yes |
| SNR + Leverage + Velocity | No | Yes |
| Class tier (IGNITER to ARCH+) | No | Yes |
| Global operator leaderboard | No | Yes |
| Works across Continue + Claude Code + Copilot + Cursor + 15+ | No (Continue 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 |
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.
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 extension generated them. An operator who reuses context efficiently in Continue 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 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. Continue is a separate coding tool; SigRank measures token efficiency from supported sources. The current SigRank CLI has no dedicated Continue log adapter, so merely installing SigRank does not import Continue sessions or publish them to the leaderboard.
- Does Continue have token usage metrics?
- Usage or cost figures displayed by Continue belong to that tool's own interface. SigRank does not automatically read Continue logs; it measures supported local adapters and can separately calculate metrics from supplied four-pillar token counts. A manual calculation alone is not a verified leaderboard submission.
- Why does platform neutrality matter?
- Using multiple AI tools makes cross-tool comparison valuable, but input coverage matters. SigRank can aggregate two or more supported active sources when explicitly invoked with `npx sigrank submit --platform multi`; it does not automatically include Continue. The default `npx sigrank submit` uses Claude telemetry.
- Can I use SigRank with Continue specifically?
- You can use Continue alongside SigRank, but there is no dedicated Continue log adapter at present. To publish from a supported local source, first create a connect code under SignalAF Settings, run `npx sigrank enroll`, preview with `npx sigrank submit --dry-run`, and then submit. The bare submit command uses Claude; other supported sources require an explicit --platform selection.
- 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.
Keep Continue. Add the score that follows you.
SigRank can measure supported local token sources while you keep using Continue. It has no dedicated Continue log reader at present. To compare, use SigRank's manual calculator for supplied counts or enroll to submit signed telemetry from a supported platform.
Related: AI Coding Efficiency Tools · Measure AI Coding Efficiency · SigRank vs Cursor