Repository navigation
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are reported for the hourly UTC timestamp change intended to improve prompt-cache reuse.
No open issues 🎉
What changed in this PR
Reduces time-driven changes to conversational agents’ system prompts to improve prompt-cache reuse while preserving the current UTC date and hour.
Changes:
- Displays UTC time rounded down to the hour in a readable date format.
- Updates the prompt wording to make the reduced precision explicit.
- Adjusts the test to verify the hourly timestamp and exclude the original minutes.
| File | Description |
|---|---|
packages/uipath/tests/agent/react/test_conversational_prompts.py |
Verifies the new date format and hour-level precision. |
packages/uipath/src/uipath/agent/react/conversational_prompts.py |
Formats timestamps at hour-level precision and updates prompt wording. |
Review effort: Balanced
🚨 Heads up:
|
|
🚨 Heads up:
|



Jira
Reduces the granularity of conversational agent's time prompt to the nearest hour. This is for better prompt-caching behavior - in the past, the system prompt would change every minute. The LLM providers, like Claude, caches byte-by-byte from tools -> system prompt -> messages and would thus not hit the caching of the messages (which consists of most of the LLM-costs due to the conversation history).
We made the tradeoff to reduce granularity to the hour - that way, the caching would generally save costs on most turns unless crossing over hour boundaries (if the user is active on the chat for a while). And we would still preserve much of the old behavior if customers were using conversational agents' date+hour for logic or tools.