claude-code - 💡(How to fix) Fix Feature request: Let users disable prompt caching for prompt hooks, especially Stop hooks [1 participants]

Feature Request

Problem

Prompt hooks (PreToolUse, PostToolUse, Stop) execute with unpredictable timing gaps. For hooks like Stop hooks, the interval between invocations can easily exceed the 5-minute prompt cache write TTL. This means:

1. The prompt gets cached on first hook invocation (paying the cache write cost)
2. By next invocation, the cache has expired
3. The prompt gets re-cached again (paying the write cost again)
4. Repeat — effectively paying cache write overhead every time with zero cache read benefit

Proposed Solution

Add a configuration option (per-hook or global) to disable prompt caching for prompt hooks. For example, in hook configuration:

{
  "hooks": {
    "Stop": [
      {
        "type": "prompt",
        "prompt": "Review the changes made...",
        "cache": false
      }
    ]
  }
}

Why This Matters

• Cost: Cache writes cost 25% more than base input tokens. If the cache never gets a read hit, users pay more than without caching.
• Latency: No benefit from caching if the cache always expires between invocations.
• User control: Users know their hook invocation patterns better than the system — let them opt out when caching is counterproductive.

Additional Context

This is most relevant for:

• Stop hooks (fire only when the agent stops, which can be minutes apart). Unused cache writes are especially expensive for Stop hooks that verify the whole session (e.g. check that outcome has been achieved, check that the whole plan has been executed correctly).
• Any hook with prompts that are invoked infrequently relative to the 5-minute cache TTL