github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-11 00:04:08 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

feat: Add {{CURRENT_DATETIME}} variable support in Tool Prompts #4811

New Issue
Closed
opened 2025-11-11 16:03:37 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-11 16:03:37 -06:00
Owner
Copy Link

Originally created by @loong95 on GitHub (Apr 11, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

Hello Open WebUI team,

I'm currently working on implementing time-sensitive tools (like weather queries) and noticed a limitation in the tool calling system. While {{CURRENT_DATETIME}} works well in system prompts, this functionality isn't available in tool-specific prompts.

Current Challenge:
When implementing a tool like:

def get_weather(__user__: dict, date: str) -> str:
    # Returns weather for specified date

I want to handle queries like "What was yesterday's weather?" by referencing the current date in the tool prompt. However, since tool prompts don't support the {{CURRENT_DATETIME}} variable, I'm unable to:

  • Calculate relative dates (yesterday/tomorrow)

  • Provide time-aware responses

  • Maintain consistency with system prompt timestamps

This creates a disconnect between what the LLM understands (via system prompt) and what tools can access.

Desired Solution you'd like

Could we extend {{CURRENT_DATETIME}} support to tool calling prompts? This would enable proper time-awareness throughout the entire processing pipeline.

Alternatives Considered

No response

Additional Context

No response

Originally created by @loong95 on GitHub (Apr 11, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description Hello Open WebUI team, I'm currently working on implementing time-sensitive tools (like weather queries) and noticed a limitation in the tool calling system. While `{{CURRENT_DATETIME}}` works well in system prompts, this functionality isn't available in tool-specific prompts. Current Challenge: When implementing a tool like: ```python def get_weather(__user__: dict, date: str) -> str: # Returns weather for specified date ``` I want to handle queries like "What was yesterday's weather?" by referencing the current date in the tool prompt. However, since tool prompts don't support the `{{CURRENT_DATETIME}}` variable, I'm unable to: * Calculate relative dates (yesterday/tomorrow) * Provide time-aware responses * Maintain consistency with system prompt timestamps This creates a disconnect between what the LLM understands (via system prompt) and what tools can access. ### Desired Solution you'd like Could we extend `{{CURRENT_DATETIME}}` support to tool calling prompts? This would enable proper time-awareness throughout the entire processing pipeline. ### Alternatives Considered _No response_ ### Additional Context _No response_
GiteaMirror commented 2025-11-11 16:03:38 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Apr 11, 2025):

You should use the python built-in functions.

@tjbck commented on GitHub (Apr 11, 2025): You should use the python built-in functions.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#4811
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?