[Q&A] Auto detect language when typing?

[FrenchdToastify]

Question

I was wondering if there is an option to autodect which language I am currently typing in so that the keyboard suggests and autocoreccts based on the language without having to manually switch.

Example: I have 2 languages installed. Sometimes I write in English, and sometimes not... The Google keyboard detects what language I'm typing, probably by the first or 2 words I type. And then it sticks with that language.

Version

v3.9.1

[AZADAYAZ]

This is possible using artificial intelligence + prompt
Even translation is possible

[FrenchdToastify]

Would you mind explaining how to set it up?

[AZADAYAZ]

After adding the API key of the artificial intelligence you use from the AI Integration section, you can assign any command to one of the buttons in the Custom AI keys section. This provides you with the desired convenience, including correcting spelling errors, translating into another language, or getting direct information from the artificial intelligence at that moment.

[yudin-s]

From what is documented today, I would treat this as not currently supported as a Gboard-style automatic language switch.

LeanType has multilingual typing and multiple dictionaries/layouts, but the active suggestion/autocorrect path is still tied to the selected input language/subtype. The AI features in the standard build can proofread or translate text, but that is different from automatically changing the live correction dictionary after the first word or two. It also would not fit the offline/offline-lite builds, where network AI features are intentionally unavailable.

So the current practical workflow is still to switch languages manually, or use the direct IME/language switching features if you want faster switching. A real implementation would probably need a separate feature: detect the language from the current composing text, switch the active dictionary/subtype, and be careful not to break mixed-language typing or privacy/offline behavior.

If this is the behavior you need, I would open it as a feature request rather than looking for a hidden setting in v3.9.1.

If this answers the question, please mark it as the answer so other multilingual users can find the current limitation.