[Bug] macOS tray menu displays untranslated localization keys

Client Type

Desktop App (Electron)

Operating System

macOS

Deployment Platform

Self hosting Docker

Version

2.2.13

Browser

Other

What happened?

The LobeHub Desktop macOS tray menu displays internal localization keys instead of readable menu labels.

The following menu items are shown as:

• tray.quickChat
• tray.newChat
• tray.settings

The issue is visible in the Russian interface. Other menu items, such as Открыть LobeHub and Выйти, are displayed correctly.

The application and tray actions otherwise work normally.

How to reproduce it?

1. Install and launch LobeHub Desktop version 2.2.13 on macOS.
2. Connect the Desktop application to a self-hosted LobeHub instance.
3. Set the application language to Russian.
4. Click the LobeHub icon in the macOS menu bar.
5. Observe the tray menu items.

The menu displays the internal keys tray.quickChat, tray.newChat, and tray.settings instead of localized labels.

What it should be?

The tray menu should display human-readable localized labels.

For the Russian interface, the items could be displayed as:

• Быстрый чат
• Новый чат
• Настройки

If Russian translations are not available, the corresponding English labels should be displayed instead:

• Quick Chat
• New Chat
• Settings

Internal localization keys should not be shown to users.

Additional Information

Environment

• LobeHub Desktop: 2.2.13
• Operating system: macOS
• Client type: Desktop
• Deployment: self-hosted LobeHub instance running with Docker Compose
• Interface language: Russian

Additional details

The screenshot shows the macOS tray menu. The following labels are displayed directly as internal localization keys:

tray.quickChat
tray.newChat
tray.settings

Other items, such as Открыть LobeHub and Выйти, are displayed correctly.

The issue affects the tray menu localization. Internal i18n keys are shown to the user instead of readable localized labels.

The application and tray actions otherwise work normally.

A screenshot is attached to this issue.

️ Willing to Submit a PR?

No, but I am happy to help test the fix

✅ Validations

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a LobeChat issue and not a third-party library or provider issue.
• Check that this is a concrete bug. For Q&A, please use GitHub Discussions or join our Discord Server.