deepseek-ai/deepseek-harness · error · Error
TokenMeterConfig: unknown key "${key}" (no settings are supp
Error message
TokenMeterConfig: unknown key "${key}" (no settings are supported) What it means
Error "TokenMeterConfig: unknown key "${key}" (no settings are supported)" thrown in deepseek-ai/deepseek-harness.
Source
Thrown at packages/llm/token-meter/src/index.ts:63
return usage.inputTokens
+ (usage.cacheReadTokens ?? 0)
+ (usage.cacheWriteTokens ?? 0)
+ usage.outputTokens
}
/** Compare optional envelopes so a headerless estimate can track later surface deltas. */
function optionalHeaderEquals(
left: EpochHeader | undefined,
right: EpochHeader | undefined,
): boolean {
if (left === undefined || right === undefined) return left === right
return headerEquals(left, right)
}
/** Reject stale or misspelled keys before defaults can hide them. */
function validateConfigKeys(config: TokenMeterConfig): void {
for (const key of Object.keys(config)) {
throw new Error(`TokenMeterConfig: unknown key "${key}" (no settings are supported)`)
}
}
declare module '@deepseek-ai/cordis' {
interface Context {
tokenMeter: TokenMeter
}
}
/** Replay owner for one service-wide estimator and isolated per-session folds. */
export class TokenMeter extends Service {
// Schemastery preserves untrusted loader keys on an empty object schema;
// the public type excludes settings while validateConfigKeys rejects them.
static Config: z<TokenMeterConfig> = z.object({}) as unknown as z<TokenMeterConfig>
private readonly states = new WeakMap<Session, ReplayState>()
constructor(ctx: Context, config: TokenMeterConfig = {}) {View on GitHub (pinned to b150a551b8)
Solutions
- Remove the unknown key; TokenMeterConfig supports no settings.
When it happens
Trigger: Thrown at packages/llm/token-meter/src/index.ts:63 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of deepseek-ai/deepseek-harness@b150a551b8 (2026-08-24).
Data as JSON: /api/errors/3dfd72a6e78c498f.
Report an issue: GitHub.