TimeAwareConfig
Configuration for time-aware LLM generation. Controls injection of temporal context (current time, message timestamps, file timestamps) into the LLM context during generation.
Usage profiles
| Usage | Fields and validation |
|---|---|
| In requests | View fields |
| In responses | View fields |
| In webhook payloads | View fields |
In requests
API JSON uses JSON field names (camelCase).
| Field | Type | Presence | Meaning |
|---|---|---|---|
includeCurrentTime | boolean | Optional | Append the current date and time to the system prompt as temporal context. Default: true. |
includeMessageTimestamps | boolean | Optional | Include timestamps on messages in the model context. Requires the message timestamp to be populated. Default: false. |
includeFileTimestamps | boolean | Optional | Include upload/modification timestamps when resolving FILE_ID content. When true, resolved file references include "[Uploaded: <timestamp>]" annotations. Default: false |
timezone | string | Optional | Timezone for formatting (IANA format, e.g., "America/Los_Angeles"). Default: "UTC" Maximum length: 50. |
timestampFormat | string (``, friendly, iso8601, date_only) | Optional | Format pattern for timestamps. "friendly" (default): "Jan 2, 2026 at 3:04 PM MST" "iso8601": "2026-01-02T15:04:00-08:00" "date_only": "2026-01-02" Maximum length: 50. |
Request validation
These rules apply when this value is supplied in a request. Request validation does not guarantee that response fields are present or satisfy the same rules.
| Applies to | Rule | Requirement |
|---|---|---|
timezone | Maximum length | 50 |
timestampFormat | Maximum length | 50 |
timestampFormat | Allowed values | ``, friendly, iso8601, date_only |
In responses
API JSON uses JSON field names (camelCase).
| Field | Type | Presence | Meaning |
|---|---|---|---|
includeCurrentTime | boolean | Optional | Append the current date and time to the system prompt as temporal context. Default: true. |
includeMessageTimestamps | boolean | Optional | Include timestamps on messages in the model context. Requires the message timestamp to be populated. Default: false. |
includeFileTimestamps | boolean | Optional | Include upload/modification timestamps when resolving FILE_ID content. When true, resolved file references include "[Uploaded: <timestamp>]" annotations. Default: false |
timezone | string | Optional | Timezone for formatting (IANA format, e.g., "America/Los_Angeles"). Default: "UTC" |
timestampFormat | string | Optional | Format pattern for timestamps. "friendly" (default): "Jan 2, 2026 at 3:04 PM MST" "iso8601": "2026-01-02T15:04:00-08:00" "date_only": "2026-01-02" |
Request validation
These rules apply when this value is supplied in a request. Request validation does not guarantee that response fields are present or satisfy the same rules.
| Applies to | Rule | Requirement |
|---|---|---|
timezone | Maximum length | 50 |
timestampFormat | Maximum length | 50 |
timestampFormat | Allowed values | ``, friendly, iso8601, date_only |
In webhook payloads
Webhook JSON uses protobuf field names (snake_case).
| Field | Type | Presence | Meaning |
|---|---|---|---|
include_current_time | boolean | Optional | Append the current date and time to the system prompt as temporal context. Default: true. |
include_message_timestamps | boolean | Optional | Include timestamps on messages in the model context. Requires the message timestamp to be populated. Default: false. |
include_file_timestamps | boolean | Optional | Include upload/modification timestamps when resolving FILE_ID content. When true, resolved file references include "[Uploaded: <timestamp>]" annotations. Default: false |
timezone | string | Optional | Timezone for formatting (IANA format, e.g., "America/Los_Angeles"). Default: "UTC" |
timestamp_format | string | Optional | Format pattern for timestamps. "friendly" (default): "Jan 2, 2026 at 3:04 PM MST" "iso8601": "2026-01-02T15:04:00-08:00" "date_only": "2026-01-02" |
Request validation
These rules apply when this value is supplied in a request. Request validation does not guarantee that response fields are present or satisfy the same rules.
| Applies to | Rule | Requirement |
|---|---|---|
timezone | Maximum length | 50 |
timestamp_format | Maximum length | 50 |
timestamp_format | Allowed values | ``, friendly, iso8601, date_only |
Where used
| Reference | Relationship |
|---|---|
| Create an agent profile | POST /api/v1/agent-profiles/create |
| Import a prompt library | POST /api/v1/agent-profiles/import |
| Update an agent profile | POST /api/v1/agent-profiles/update |
| Append a message without generating | POST /api/v1/llm/append-message |
| Create a new conversation thread | POST /api/v1/llm/create-thread |
| Send a message to a conversation | POST /api/v1/llm/send-message |
| Send a message and wait for the result | POST /api/v1/llm/send-message-sync |
| Update context management settings | POST /api/v1/llm/update-context-management-settings |
| Update default generation config | POST /api/v1/llm/update-default-generation-config |
| Update the caller's default generation config | POST /api/v1/enduser/update-generation-config |
| Get an agent profile | POST /api/v1/agent-profiles/get |
| List agent profiles | POST /api/v1/agent-profiles/list |
| Withdraw your rating on a message | POST /api/v1/llm/delete-message-rating |
| Get full conversation state | POST /api/v1/llm/conversation-state |
| Rate an assistant message | POST /api/v1/llm/rate-message |
| Submit client-side tool results and wait for the next segment | POST /api/v1/llm/submit-client-tool-results-sync |
| Get the caller's end-user profile | POST /api/v1/enduser/get |
| Generation configuration | API JSON uses JSON field names (camelCase). |
| llm.generation_started | Webhook JSON uses protobuf field names (snake_case). |
| llm.message_published | Webhook JSON uses protobuf field names (snake_case). |
| GenerationConfig | Nested in model |
| GenerationConfig | Nested in model |
| GenerationConfig | Nested in model |
Download the public reference contract.
Document: DOC-API-MODEL-time-aware-config.