Include current time (not just date) in system context

Problem

The currentDate system context only provides the date:

Today's date is 2026-03-14.

It does not include the current time or timezone. This causes the model to frequently misjudge the time — e.g., telling a user it's time to wind down at 9pm when wind-down is 9:30pm, or incorrectly assessing whether calendar events have already passed.

Impact

This is especially problematic for agents that manage calendars, schedules, and time-sensitive workflows. Without knowing the current time, the model has to run date via Bash to orient itself — wasteful when the system could just include it.

Suggestion

Include the full timestamp (date + time + timezone) in the system context, ideally refreshed each turn:

Current date and time: 2026-03-14T21:00:00-07:00 (America/Los_Angeles)

This would eliminate a whole class of time-related errors without any workaround needed.

🤖 Generated with Claude Code