Garm 084678df7c fix(proxy): strip cache_control before hashing turn_id ... compute_turn_id hashed the raw message dicts, which meant the same user-text message produced a different hash on each call of one agent loop because clients (notably Claude Code) move the cache_control breakpoint to the newest message per call. The user-text block carries cache_control on call 1 and not on call 2, so the serialized prefix differs and the turn_id rolls over. Effect downstream: every API call becomes its own "turn" and any prompt-level aggregation (e.g. the Headroom desktop app's prompt all-time record) collapses to the largest single call, not the sum across the prompt. Add a small recursive normalization pass that strips cache_control from the hashed prefix and from list-shaped system prompts before hashing. Two new tests cover cache_control moving between calls on both the messages array and the system prompt. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-23 16:04:57 +02:00
..
test_compute_turn_id.py	fix(proxy): strip cache_control before hashing turn_id	2026-04-23 16:04:57 +02:00
test_transformations_feed.py	feat: add live transformations feed to dashboard	2026-04-20 23:47:43 -05:00