PulseAugur
EN
LIVE 03:34:31

DeepSeek Harness token counting errors revealed in analysis

An analysis of the DeepSeek Harness token counting system revealed several inaccuracies, including a precise doubling of usage records and significant overstatements in forked sessions. The system also failed to count tokens from compaction events and mishandled retried streams. While DeepSeek Harness's append-only design prevents some common errors found in other token trackers like splitrail and tokscale, the identified issues suggest potential for inflated billing and inaccurate usage monitoring. AI

IMPACT Potential for inflated billing and inaccurate usage monitoring in AI applications using DeepSeek Harness.

RANK_REASON Analysis of a specific software component (DeepSeek Harness) for accuracy issues.

Read on dev.to — LLM tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

DeepSeek Harness token counting errors revealed in analysis

COVERAGE [1]

  1. dev.to — LLM tag TIER_1 English(EN) · Li Zhuojun ·

    DeepSeek Harness got append-only right. Its token projection still misses what compaction costs.

    <p>Four numbers from a nine-day-old codebase, measured this week across two providers:</p> <ul> <li>Summing every usage record in a DeepSeek Harness session log gives <strong>2.000000×</strong> the correct total. Not roughly two. Six digits, no remainder, reproduced independently…