Your agents know what day it is
No agent on any surface was told the date. Each one fell back on a guess from
its training data and stated it with complete confidence. The problem was never
that it could not find out, since a sandboxed agent can run date -u. The
problem was that it never thought to ask.
All four agent surfaces now open with the current UTC timestamp: the agentic run, both engagements of the agent watching a codified run, the interview, and the reviser that rewrites your procedure.
The timestamp rides in the first message rather than in the agent's instructions. Instructions have to rebuild identically when a run resumes, and a run can sit on an approval for days, so a date baked in there would come back stale and be wrong with exactly the same confidence as before.
Scheduled runs also learn which occurrence they are serving. A cron fire now carries the time it fired, so an agent can read it and a codified step can select it. Before this a scheduled run received an empty payload and could not tell one Monday morning from another.
This entry describes what shipped on the day it shipped. For how the capability behaves now, read /docs/runs.