Repository navigation
fleetdiff v0.14.0
Released October 29, 2026.
Compare two periods of LiteLLM spend logs or Langfuse exports to see which
recorded agents drove token and spend changes. Choose an explicit agent ID or
request-tag source; the report does not guess agent identities.
Agent Attribution
- Use
--group-by agent --agent-source agent_idfor LiteLLM's recorded agent IDs. - Use
--agent-source request-tag --agent-tag-prefix 'agent:'for LiteLLM or
Langfuse tags. Identical repeated tags resolve to one agent; distinct matching
labels remain ambiguous, and unknown/ambiguous rows retain their accounting. - Rank signed token changes, or add
--rank-by recorded-spend-changefor exact
recorded-USD changes. USD-unavailable agents stay visible even with--top. - See the answer sentence, before/after tokens and USD, period shares and
unattributed changes. Cost-coverage columns appear only for incomplete
displayed costs. Recorded USD is not a provider invoice. - Raw selected labels require both disclosure flags and are escaped in text.
Identical Langfuse labels remain project-scoped and use project aliases;
raw project names are not displayed. - Keep invalid LiteLLM tag-element rows as unknown identity with separate
coverage. Langfuse retains string-only validation. Exact agent counting is
bounded to 1,024 identities; no silent truncation occurs.
The synthetic fixture records 300 -> 620 tokens and USD 3 -> 6.20. Alpha adds
200 of the 320-token net increase (62.5%). See the
agent guide for commands and limits.
Breaking Routing Label Disclosure
Routing --show-labels now also requires --acknowledge-sensitive-labels.
Replace an existing routing command such as:
fleetdiff investigate --litellm-spend spend.csv --routing-audit --show-labelswith:
fleetdiff investigate --litellm-spend spend.csv --routing-audit \
--show-labels --acknowledge-sensitive-labelsThe same two flags disclose selected agent labels. User, session, end-user and
key rankings remain aliased. Default exports and reports remain byte-identical
to v0.13.1; the agent JSON section retains its independently versioned contract.
No new runtime dependency is introduced.
Publication Gates
Follow RELEASING. Published archives, checksums, SBOM/provenance,
anonymous installer tests, packaged-binary and pinned database checks, and site
version/provenance verification cannot pass from an unpublished local checkout.
Site re-pinning and the new agent guide remain unpublished until the released
artifact checks pass. Do not create a tag merely to test packaging.
Code authors: Vijay and Codex