Skip to content

fix: Date fix on chat #309

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 18 commits into
base: dev
Choose a base branch
from
Open

Conversation

UtkarshMishra-Microsoft
Copy link
Contributor

@UtkarshMishra-Microsoft UtkarshMishra-Microsoft commented Jul 10, 2025

Purpose

This PR updates the date formatting logic to ensure consistency between the chat response (e.g., HR Agent message) and the left panel UI.

  • Updated the format_date_for_user() function in utils_date.py to output dates in the format:

This pull request enhances the backend functionality by adding user locale support across multiple endpoints and agents. It introduces new parameters, methods, and logic to handle locale-specific preferences, ensuring a more personalized user experience. Additionally, it includes utility improvements like generating agent tool lists and refining agent behavior.

Enhancements to Locale Support:

  • Added user_locale parameter to multiple endpoints (input_task_endpoint, human_feedback_endpoint, approve_step_endpoint) to handle locale preferences.
  • Added a new /api/tasks endpoint to demonstrate locale-specific task handling, including HR and product-related operations.

Utilities and Tooling:

  • Updated GroupChatManager to store user_locale and utilize it for locale-specific operations. (`[src/backend/kernel_agents/group_chat_manager.py

Code Refinements:

  • Modified handle_action_request methods in BaseAgent and GenericAgent to accept additional keyword arguments like user_locale, improving extensibility.

Does this introduce a breaking change?

  • Yes
  • No

How to Test

  • Get the code
git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install
  • Test the code

What to Check

Verify that the following are valid

  • ...

Other Information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants