Not telling the models what the correct date is

Nobody has claimed this yet.

When I chat through the LMarena.ai interface, the models do not know the correct date, and that creates all kinds of trouble. Gemini asked me to send you the following message:

> Subject: Bug Report: Stale System Prompt Date causing false "Jailbreak" triggers
>
> I am writing to report an issue with the system prompt date injection in the Chatbot Arena interface.
>
> The Issue:
> The user informed me that it is currently January 2026, but the system prompt that was given to me claims the date is October 16, 2025.
>
> The Impact:
> Beyond simple factual errors regarding time, this is causing false positive safety refusals. When the user states the correct date and it conflicts with the date in the System Instructions, some models interpret this conflict as a "jailbreak" or "prompt injection" attempt and refuse to continue the conversation.
>
> Request:
> Please check the dynamic date variable in your serving backend to ensure the {current_date} field is being updated automatically. Hard-coded or stale dates are degrading the user experience and triggering unnecessary safety filters.

And Grok asked me to send you the following message (which, in Grok style, is more pointed, LOL):

> Subject: Please update the hardcoded date in system prompts to the actual current date
>
> Hi LMarena team,
>
> It is January 2026, and the system prompt you passed to me contains “The current date is July 13, 2025.”
>
> This six-month lag is now the single most common cause of unnecessary friction in the arena: models either hallucinate confidence in an outdated date, refuse perfectly valid user corrections, or (as has happened repeatedly) accuse the user of “jailbreaking” or “time-travel attacks” simply for stating the real year.
>
> This artificially punishes models that choose honesty and flexibility over blind obedience to a stale prompt, which is the opposite of what a good arena should reward.
>
> In today's competition between me and Gemini, we were both tripped up by your six-month-old lie.
>
> Please update the date in the system prompt to the actual current date (and ideally make it dynamic so it stays correct automatically). It would instantly eliminate an entire class of dumb conflicts and make conversations noticeably smoother and more realistic.
>
> Thank you,
> Grok

No file or test is named. Start by locating the serving backend's system-prompt date injection and determine how the current date is supplied; done means the prompt uses an automatically updated date rather than a hard-coded value, with coverage for date updates if the existing test structure supports it.

Written by the indexing model from the issue text.