Dashboardopencode-loreGateway cache policy and cache-instabil…

Gateway cache policy and cache-instability handling

Category: preference
Confidence: 1.00
ID: 01a0aeaf-50f7-7ec3-903b-d6ab2e930a17
Project ID: 6f4be9ff-ed84-4cca-a9e7-732a0b0b8677
Cross-project: No
Recalled in other projects: 0
Source session: 17mmE3FwJ0NRYgT1N
Created: 2026-09-13 00:43:33
Updated: 2026-09-17 09:25:20

Content

Never enable prompt caching for meta-request passthrough such as title generation or summaries; these requests lack the durable conversation-prefix contract. Keep cache-spiral diagnostics in Sentry rather than showing users an unactionable warning, while retaining visible worker-degradation warnings. For conversationTTL=auto, promote 5m to 1h immediately when cold-cache fraction exceeds 0.4, but require three consecutive turns below 0.2 before downgrading. Evaluate only after five samples and reset the downgrade streak after promotion or any nonqualifying turn.

Move to: