Unverified50% confidenceEventExact time
GitHub issue #66947 reports that each compaction or continuation appears to rewrite earlier records into the same transcript, using the same uuid and timestamp, with one message appearing five times in one file; Anthropic has not confirmed this issue.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/19/2026
First Seen
Valid until: 1/17/2027
Sources
Related Entities
Related Claims
UnverifiedGit records not complete file copies but differences between files (diffs).70% similarVerifiedGit's commit history records code diffs and commit messages, but this information is typically filled in by the author themselves and does not contain machine-verifiable proof material.70% similarUnverifiedA single-line configuration change can be placed in a Git commit record, but it cannot answer the question of why that particular line was changed.69% similarUnverifiedGitHub issue #64880 (still open) reports that under high server load, six independent sequential responses returned the same message.id; the reporter later re-checked during a normal-load window and found no instance of the same ID appearing under multiple requestIds.69% similarUnverifiedThe case in GitHub issue #87303 shows: a session contained 521 usage records but corresponded to only 323 distinct message IDs; directly summing gave cache_creation_input_tokens of 1,075,420, while deduplicating by ID gave 560,751, an overestimate of 1.92 times; the cache-read field was overestimated by 1.59 times.68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1067076API
curl https://kongchang.com/api/v1/knowledge/claims/1067076MCP
get_claim(id=1067076)