Hey, thanks for the detailed report and the screenshot. I can see the garbled Thai text in the chat output.
This is a known issue with Composer 1.5/2 models. They don’t handle non-ASCII Unicode correctly (Thai, Korean, Vietnamese, etc.). We got similar reports today from users in other languages:
- Encoding issues in Auto Mode (Korean text broken)
- Agent's responses get unicode errors (unreadable Vietnamese)
The team is aware of the issue. We don’t have an exact ETA yet, but your report helps with prioritization.
As a workaround, try switching to a different model (like Claude or GPT) instead of Composer 1.5/2 when you work with Thai text. In Auto, it happens less often since routing doesn’t always pick a Composer model.
If you can, please send the Request ID (top right of the chat > Copy Request ID) from one of the broken messages. That’ll help with extra tracing.