Cache killers

These look harmless. They zero the hit.

×

Timestamp or UUID in the system prompt

The left edge changes every call. Matching dies at token 0.

×

Shuffled tool JSON

Same tools, different key order. The prefix hash is not the same.

×

Random few-shot sampling

Picking 3 of 20 examples per request is diversity for you, a miss for the cache.

×

Editing earlier chat turns

Summarizing, redacting, or resorting history invalidates everything after the edit.

×

Toggling tools, thinking, or images

tool_choice, web search, effort, and extra images are part of the prefix.

×

Breakpoint on the changing tail

Claude writes a new hash every time. Lookback will not rescue a write that never existed.

×

Idle past the TTL

A four-minute generation burns a five-minute cache. The follow-up must start before expiry.

×

Parallel first requests

The write is not readable until the first response begins. The herd all miss together.