Repository navigation
Bug: Telegram Bot Messages Are Displayed in Ukrainian #135
Description
Regression: Telegram Bot Welcome Message Is Always Displayed in Ukrainian
Summary
The Telegram bot onboarding message is displayed in Ukrainian, regardless of the language configured in Claude Code Studio.
Current Behavior
When starting a conversation with the Telegram bot, the following message is displayed:
👋 Claude Code Studio
Для підключення введіть 6-символьний код з панелі налаштувань вашого Studio.
💡 Код має вигляд: XXX·XXX
Expected Behavior
The bot should either:
- Use the language configured in Claude Code Studio.
- Use the Telegram user's selected language when available.
- Fall back to English if no translation is available.
For example, with English selected:
👋 Claude Code Studio
To connect, enter the 6-character code from your Studio settings panel.
💡 Example code: XXX·XXX
Additional Observation
This appears to be part of a broader localization regression where English users sometimes receive Ukrainian text in various parts of the application.
Suggested Improvements
- Respect the CCS language setting.
- Add a bot language configuration option.
- Use English as the default fallback language.
- Audit Telegram bot translations and locale detection logic.
Impact
- Confusing onboarding experience.
- Inconsistent localization.
- Difficult for users who do not understand Ukrainian.
Priority
Medium
Activity
telegram: follow the Studio language instead of defaulting to Ukraini…
Lexus2016 commentedon Nov 10, 2026
Fixed in #138, now on
main.The root cause was a default mismatch: the app's own language fallback is English
(
GET /api/langanswersc.lang || 'en'), while the bot carried a separate'uk'fallback inits constructor and in both places
server.jscreates it. A fresh install therefore ran anEnglish UI with a Ukrainian bot. The bot now takes the same default, and a key missing from a
dictionary falls back to English rather than Ukrainian.
One deliberate addition beyond the report: the pairing screen — the message you quoted — now
answers in the language your Telegram client reports (when it is one of the five we ship),
because there is no Studio setting to read before a device is paired. After pairing, the Studio
language governs everything, so changing Settings → language changes the bot too, live.
Thanks for the clear write-up, including the expected text — it made the fix unambiguous.