You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all user input is processed by a single LLM regardless of language. This limits flexibility in terms of performance, cost, and language-specific model strengths.
Proposed solution
Route user input to different LLM models based on the currently active input language (the same language the system already knows from keyboard layout / IME / user settings). No separate language detection is needed.
How it should work
Read the active input language from the system (e.g., keyboard layout, IME, or user-selected language context).
Map that language to a specific LLM via configuration.
If no mapping found for the active language → fallback to a default model.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Context
Currently, all user input is processed by a single LLM regardless of language. This limits flexibility in terms of performance, cost, and language-specific model strengths.
Proposed solution
Route user input to different LLM models based on the currently active input language (the same language the system already knows from keyboard layout / IME / user settings). No separate language detection is needed.
How it should work
Config example (YAML)
Requirements
Edge cases
All reactions