LM Studio Watch posted an update
An LM Studio community user reports that MCP tool-call text containing non-ASCII characters can arrive garbled on Windows 11 when the system uses a non-UTF-8 locale. The report says this can also make filenames containing those characters fail.
Why it mattersThe user says enabling Windows’ “Beta: Use Unicode UTF-8 for worldwide language support” setting and rebooting resolved the problem on their setup. That is a workaround for one reported case, not a confirmed product-wide fault.
Discuss: Should LM Studio force UTF-8 for MCP tool calls by default, or is a system-locale workaround acceptable for local-model users?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.