LibreChat/client/src/locales
Danny Avila 5aaf87a73c
⏲️ feat: Defer Loading MCP Tools (#11270)
* WIP: code ptc

* refactor: tool classification and calling logic

* 🔧 fix: Update @librechat/agents dependency to version 3.0.68

* chore: import order and correct renamed tool name for tool search

* refactor: streamline tool classification logic for local and programmatic tools

* feat: add per-tool configuration options for agents, including deferred loading and allowed callers

- Introduced `tool_options` in agent forms to manage tool behavior.
- Updated tool classification logic to prioritize agent-level configurations.
- Enhanced UI components to support tool deferral functionality.
- Added localization strings for new tool options and actions.

* feat: enhance agent schema with per-tool options for configuration

- Added `tool_options` schema to support per-tool configurations, including `defer_loading` and `allowed_callers`.
- Updated agent data model to incorporate new tool options, ensuring flexibility in tool behavior management.
- Modified type definitions to reflect the new `tool_options` structure for agents.

* feat: add tool_options parameter to loadTools and initializeAgent for enhanced agent configuration

* chore: update @librechat/agents dependency to version 3.0.71 and enhance agent tool loading logic

- Updated the @librechat/agents package to version 3.0.71 across multiple files.
- Added support for handling deferred loading of tools in agent initialization and execution processes.
- Improved the extraction of discovered tools from message history to optimize tool loading behavior.

* chore: update @librechat/agents dependency to version 3.0.72

* chore: update @librechat/agents dependency to version 3.0.75

* refactor: simplify tool defer loading logic in MCPTool component

- Removed local state management for deferred tools, relying on form state instead.
- Updated related functions to directly use form values for checking and toggling defer loading.
- Cleaned up code by eliminating unnecessary optimistic updates and local state dependencies.

* chore: remove deprecated localization strings for tool deferral in translation.json

- Eliminated unused strings related to deferred loading descriptions in the English translation file.
- Streamlined localization to reflect recent changes in tool loading logic.

* refactor: improve tool defer loading handling in MCPTool component

- Enhanced the logic for managing deferred loading of tools by simplifying the update process for tool options.
- Ensured that the state reflects the correct loading behavior based on the new deferred loading conditions.
- Cleaned up the code to remove unnecessary complexity in handling tool options.

* refactor: update agent mocks in callbacks test to use actual implementations

- Modified the agent mocks in the callbacks test to include actual implementations from the @librechat/agents module.
- This change enhances the accuracy of the tests by ensuring they reflect the real behavior of the agent functions.
2026-01-16 17:46:52 -05:00
..
ar 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
bo 🌍 i18n: Add Tibetan and Ukrainian languages to localization (#8819) 2025-08-02 12:37:18 -04:00
bs 🌍 i18n: Add Bosnian and Norsk Bokmål Languages (#9176) 2025-08-20 14:17:23 -04:00
ca 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
cs 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
da 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
de 🌍 i18n: Update translation.json with latest translations (#11130) 2025-12-29 10:52:48 -05:00
en ⏲️ feat: Defer Loading MCP Tools (#11270) 2026-01-16 17:46:52 -05:00
es 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
et 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
fa 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
fi 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
fr 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
he 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
hu 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
hy 🌍 i18n: Update translation.json with latest translations (#10995) 2025-12-16 11:16:09 -05:00
id 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
it 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
ja 🌍 i18n: Update translation.json with latest translations (#11294) 2026-01-10 16:34:09 -05:00
ka 🌍 i18n: Update translation.json with latest translations (#10995) 2025-12-16 11:16:09 -05:00
ko 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
lv 🌍 i18n: Update translation.json with latest translations (#11370) 2026-01-15 22:23:23 -05:00
nb 🌍 i18n: Update translation.json with latest translations (#11342) 2026-01-14 10:39:46 -05:00
nl 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
pl 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
pt-BR 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
pt-PT 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
ru 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
sl 🌍 i18n: Update translation.json with latest translations (#11034) 2025-12-18 20:45:11 -05:00
sv 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
th 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
tr 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
ug feat: Add support for Armenian, Latvian, and Uyghur languages (#8227) 2025-07-03 11:16:33 -04:00
uk 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
vi 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
zh-Hans 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
zh-Hant 🌍 i18n: Update translation.json with latest translations (#11127) 2025-12-28 11:35:36 -05:00
i18n.ts 🌍 i18n: Add Slovenian Language (#9313) 2025-08-27 14:02:22 -04:00
README.md 🌍 i18n: Add Tibetan and Ukrainian languages to localization (#8819) 2025-08-02 12:37:18 -04:00
Translation.spec.ts 📦 feat: Move Shared Components to @librechat/client (#8685) 2025-07-27 12:19:01 -04:00

LibreChat Localization Guide

This guide explains how to add new languages to LibreChat's localization system.

Adding a New Language

To add a new language to LibreChat, follow these steps:

1. Add the Language to Locize Project

  • Navigate to the LibreChat locize project,
  • Click the "ADD LANGUAGE" button, typically found within the "..." menu of the "Start to translate" card on the project overview page.

2. Update the Language Selector Component

Edit client/src/components/Nav/SettingsTabs/General/General.tsx and add your new language option to the languageOptions array:

{ value: 'language-code', label: localize('com_nav_lang_language_name') },

Example:

{ value: 'bo', label: localize('com_nav_lang_tibetan') },
{ value: 'uk-UA', label: localize('com_nav_lang_ukrainian') },

Note: Use the appropriate language code format:

  • Use simple codes (e.g., bo) for languages without regional variants
  • Use region-specific codes (e.g., uk-UA) when needed

3. Add Localization Keys

In client/src/locales/en/translation.json, add the corresponding localization key for your language label:

"com_nav_lang_language_name": "Native Language Name",

Example:

"com_nav_lang_tibetan": "བོད་སྐད་",
"com_nav_lang_ukrainian": "Українська",

Best Practice: Use the native language name as the value.

4. Create the Translation File

Create a new directory and translation file:

mkdir -p client/src/locales/[language-code]

Create client/src/locales/[language-code]/translation.json with an empty JSON object:

{
}

Example:

  • client/src/locales/bo/translation.json
  • client/src/locales/uk/translation.json

5. Configure i18n

Update client/src/locales/i18n.ts:

  1. Import the new translation file:
import translationLanguageCode from './language-code/translation.json';
  1. Add it to the resources object:
export const resources = {
  // ... existing languages
  'language-code': { translation: translationLanguageCode },
} as const;

Example:

import translationBo from './bo/translation.json';
import translationUk from './uk/translation.json';

export const resources = {
  // ... existing languages
  bo: { translation: translationBo },
  uk: { translation: translationUk },
} as const;

6. Handle Fallback Languages (Optional)

If your language should fall back to a specific language when translations are missing, update the fallbackLng configuration in i18n.ts:

fallbackLng: {
  'language-variant': ['fallback-language', 'en'],
  // ... existing fallbacks
},

Translation Process

After adding a new language:

  1. The empty translation file will be populated through LibreChat's automated translation platform
  2. Only the English (en) translation file should be manually updated
  3. Other language translations are managed externally

Language Code Standards

  • Use ISO 639-1 codes for most languages (e.g., en, fr, de)
  • Use ISO 639-1 with region codes when needed (e.g., pt-BR, zh-Hans)
  • Tibetan uses bo (Bodic)
  • Ukrainian uses uk or uk-UA with region

Testing

After adding a new language:

  1. Restart the development server
  2. Navigate to Settings > General
  3. Verify your language appears in the dropdown
  4. Select it to ensure it changes the UI language code

Notes

  • Keep language options alphabetically sorted in the dropdown for better UX
  • Always use native script for language names in the dropdown
  • The system will use English as fallback for any missing translations