Unverified50% confidenceFactExact time
In the experiment, "starting a new session for a new task" did not save tokens and instead used about 22% more, because the old task was short and still in the cache, and after /clear discarded the cache the new session had to be rebuilt at full price.
1
Sources
50%
Confidence
Long-term
Relevance
11/14/2026
First Seen
Sources
Hands-On Test: 5 Habits That Cut Claude Code Token Usage by 85%
youtubeSaurav Verma | Generative AI11/12/2026
Related Entities
Related Claims
UnverifiedIn one long conversation of 36 turns with approximately 1.78 million tokens, the full-retention configuration was actually the cheapest because 97% of the tokens hit the cache.65% similarUnverifiedRunning '/effort high' does not break the prompt cache, and the next question still reads about 19,000 tokens from the cache; however, this setting is saved as the default for all future sessions.64% similarUnverifiedFor short sessions or one-off tasks, Tokenade's token savings shrink noticeably, falling below the 39% average.63% similarUnverifiedIn a call with about ninety-seven thousand-plus input tokens, only the newest one thousand eight hundred-plus tokens were not cached; without caching the input cost was about 0.1 yuan, and with caching it was less than 0.004 yuan, 26 times cheaper.62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1169765API
curl https://kongchang.com/api/v1/knowledge/claims/1169765MCP
get_claim(id=1169765)