Current Datetime

Current Datetime injects the current date and time into each request before it is forwarded to the LLM. This gives the model reliable temporal context for queries that depend on knowing the current date or time — for example: "What happened today?", "How many business days are left this month?", or "What should I schedule for tomorrow?"

Without this module, LLMs have no knowledge of the current date beyond their training cutoff, often producing incorrect or vague temporal answers.

Stage

Injected Format

The module prepends the following block to the first user message in the request:

Current datetime: {datetime}
Timezone: {timezone}

If no user message exists in the request, the block is prepended to the first message of any role.

Example

Original first user message:

How many days until the end of the quarter?

After injection (timezone: Asia/Jakarta, format: ISO 8601):

Current datetime: 2026-06-25T09:30:00+07:00
Timezone: Asia/Jakarta

How many days until the end of the quarter?

Configuration

Timezone

The IANA timezone identifier used to resolve the current datetime. Defaults to UTC.

All standard IANA timezone identifiers are supported. If an unknown or invalid timezone is provided, the module automatically falls back to UTC.

Common options:

Datetime Format

The output format for the injected datetime string.

Example Use Cases

• Time-sensitive Q&A bots: Chatbots that answer questions like "What's today?" or "When does this promotion end?" need reliable temporal context.
• Scheduling assistants: Agents that help users book meetings, set reminders, or reason about deadlines.
• Daily digest generation: Pipelines that generate summaries anchored to the current date.
• Business logic validation: LLMs evaluating time-based rules (e.g., "Is this invoice still within the payment window?").