- Issue created by @marcus_johansson
- 🇩🇪Germany jan kellermann
As I understood it, the AI-Translate module is supposed to deliver a provider for “translate_text” that works with LLMs and chat.
My impression is that AI-Translate works past “translate_text”. I cannot select the set Deepl provider at any point.
Was this the goal? What is the sense of “translate_text” then? How can I use ai_provider_deepl with AI-Translation module?
- 🇧🇬Bulgaria alexrayu
Confirmed. With the recent changes from #3480861, The whole translate-text branch of providers fell off. DeepL is no longer accessible. The code now enforces the use of "chat" provider type.
- 🇬🇧United Kingdom scott_euser
I'm not sure the plan here myself, but maybe a separate issue should be raised in ai_provider_deepl. It seems like converting it to chat would lose the source/target language though so I don't think this issue should be closed. Maybe AI Translate instead needs to check for providers that provide both chat and/or translate_text, and if translate_text is found in a provider, use that, otherwise fall back to chat.
- 🇧🇬Bulgaria valthebald Sofia
This was handled by 📌 Discuss: Unify translate operations over ai Active , so I dare mark this closed
- Status changed to Closed: duplicate
29 days ago 7:23pm 5 July 2025 - 🇺🇸United States Kristen Pol Santa Cruz, CA, USA
We are doing some issue management housekeeping and adding/removing components.
We are removing the "Other Submodules" component and want people to categorize issues with the best module/submodule component.
Moving this issue to "AI Translate".
See 📌 Update AI module project components Active for more details.