openclaw - 💡(How to fix) Fix [Bug]: System prompt timestamp injection breaks Anthropic prompt cache (always cache_creation, never cache_read) [1 comments, 1 participants]

TL;DR

Move the Current Date & Time block injection after the cache_control boundary or make it optional via configuration to prevent cache invalidation.

Guidance

• Identify the code responsible for injecting the Current Date & Time block and modify it to inject after the cache_control boundary.
• Consider adding a configuration option (e.g., injectTimestamp: false) to make the timestamp injection optional.
• Verify the cache behavior by checking the cache hit rate after applying the changes.
• Review the OpenClaw documentation to see if there are any existing configuration options or settings that can be used to control the injection of dynamic content.

Example

No code snippet is provided as the issue does not contain sufficient code details.

Notes

The solution assumes that the Current Date & Time block is being injected by the OpenClaw system and that modifying this behavior is feasible. Additional details about the OpenClaw codebase and configuration options may be necessary to provide a more specific solution.

Recommendation

Apply workaround: Move the Current Date & Time block injection after the cache_control boundary or make it optional via configuration, as this is a more feasible and immediate solution to prevent cache invalidation and reduce unnecessary token costs.