session_status tool.
Message envelopes (local by default)
Inbound messages are wrapped with a weekday plus second-precision timestamp:agents.defaults:
| Key | Values | Behavior |
|---|---|---|
envelopeTimezone | local (default), utc, user, explicit IANA name | user uses agents.defaults.userTimezone (host timezone when unset). An explicit IANA name (e.g. "America/Chicago") pins a fixed zone; unrecognized names fall back to UTC. |
envelopeTimestamp | on (default), off | off removes absolute timestamps from envelope headers, direct agent prompt prefixes, and embedded model-input prefixes. |
envelopeElapsed | on (default), off | off removes the elapsed-time suffix (the +30s / +2m style) shown since the previous message in the session. |
Examples
Local (default):envelopeTimezone: "utc":
System prompt: current date and time
The system prompt includes a Current Date & Time section with the time zone only (no clock or time format) so prompt caching stays stable:agents.defaults.userTimezone when configured, otherwise the host timezone.
The prompt also instructs the agent to run the session_status tool whenever it needs the
current date, time, or day of week.
System event lines (local by default)
Queued system events inserted into agent context are prefixed with a timestamp using the sameenvelopeTimezone selection as message envelopes (default: host-local).
Configure user timezone + format
userTimezonesets the user-local timezone for prompt context (and forenvelopeTimezone: "user").timeFormatcontrols 12h/24h display in prompt-facing times.autofollows OS preferences.
Time format detection (auto)
WhentimeFormat: "auto", OpenClaw inspects the OS preference (macOS and Windows)
and falls back to locale formatting. The detected value is cached per process
to avoid repeated system calls.
Tool payloads + connectors (raw provider time + normalized fields)
Channel tools return provider-native timestamps and add normalized fields for consistency:timestampMs: epoch milliseconds (UTC)timestampUtc: ISO 8601 UTC string
- Discord: UTC ISO timestamps
- Slack: epoch-like strings from the API
- Telegram/WhatsApp: provider-specific numeric/ISO timestamps