Context: Using Hennos via Telegram.
Issue: Hennos sometimes switches back to Portuguese even when the user initiates and maintains the conversation in English. This happens "at random" from the user's perspective, and breaks the language consistency of the chat.
Observed behavior:
- User starts a conversation in English and keeps writing in English.
- Hennos initially replies in English, but later answers or parts of answers come back in Portuguese without the user changing languages.
- This has occurred multiple times for the user, enough that they noticed a pattern and reported it as a bug.
Expected behavior:
- Hennos should continue replying in the language the user is currently using, unless the user explicitly requests a different language or code-switching.
- If there is any automatic language detection, it should not override the user’s clear, ongoing use of English.
Possible causes (guess):
- Over-aggressive language auto-detection based on older messages.
- System/developer instructions suggesting a preferred language and occasionally overriding user context.
- Model sometimes following earlier Portuguese messages or profile info instead of the latest user message language.
Suggested fixes:
- Enforce a simple rule: "Respond in the language of the latest user message by default".
- If multiple languages are mixed, prioritize the majority language of the last message, or ask the user which language they prefer.
- Optionally add a per-user language preference setting that, once set, is sticky unless user changes it.
User impact:
- Confusing UX, especially for bilingual users who intentionally choose English.
- Makes longer, emotionally sensitive or technical conversations harder to follow when the language flips unexpectedly.
Context: Using Hennos via Telegram.
Issue: Hennos sometimes switches back to Portuguese even when the user initiates and maintains the conversation in English. This happens "at random" from the user's perspective, and breaks the language consistency of the chat.
Observed behavior:
Expected behavior:
Possible causes (guess):
Suggested fixes:
User impact: