[Feature Request] Support use openai compatible api translate bio #183

New Issue

MrUnknownDE · 2026-04-05T16:16:33+02:00

MrUnknownDE commented

2026-04-05 16:16:33 +02:00

Originally created by @mdogwoop on 12/6/2025

Explain in detail what your suggested feature would be used for.
This feature would allow users to translate user bios using OpenAI-compatible LLM APIs. It expands the current functionality beyond the Google Translate API, enabling the use of various model providers (both cloud-based and local) for more accurate, context-aware, and customizable translations.

Describe how it would look if it requires a UI.

Menu Update: Rename the Google Translate API option under Settings > Advanced to Bio Translate API.
Configuration Interface: Upon clicking "Set API Key", introduce a Provider selector with two options:
- Google Translate: Retains the existing interface/functionality.
- LLM / OpenAI Compatible: Displays the following new fields:
  - API Endpoint: (e.g., base URL)
  - API Key
  - Model Name: (e.g., gpt-4o, llama3)
  - Prompt: An input box pre-filled with a default system prompt, which users can edit.
- Test Button: Add a button to verify the connection and model response.

Explain why people would want to use it.
Leveraging LLMs for translation offers several advantages over traditional engines like Google Translate:

Quality & Context: LLMs perform significantly better with low-resource languages and internet slang/memes.
Personalization: Users can modify the prompt to achieve specific translation tones or styles.
Compatibility: Support for OpenAI-compatible APIs covers the majority of model providers.
Cost & Privacy: Many providers (e.g., Google Gemini, SiliconFlow) offer generous free tiers. Additionally, users can opt for local deployment using tools like Ollama to ensure complete data privacy.

*Originally created by @mdogwoop on 12/6/2025* **Explain in detail what your suggested feature would be used for.** This feature would allow users to translate user bios using OpenAI-compatible LLM APIs. It expands the current functionality beyond the Google Translate API, enabling the use of various model providers (both cloud-based and local) for more accurate, context-aware, and customizable translations. **Describe how it would look if it requires a UI.** 1. **Menu Update:** Rename the `Google Translate API` option under **Settings > Advanced** to `Bio Translate API`. 2. **Configuration Interface:** Upon clicking "Set API Key", introduce a **Provider** selector with two options: * **Google Translate:** Retains the existing interface/functionality. * **LLM / OpenAI Compatible:** Displays the following new fields: * **API Endpoint:** (e.g., base URL) * **API Key** * **Model Name:** (e.g., `gpt-4o`, `llama3`) * **Prompt:** An input box pre-filled with a default system prompt, which users can edit. * **Test Button:** Add a button to verify the connection and model response. **Explain why people would want to use it.** Leveraging LLMs for translation offers several advantages over traditional engines like Google Translate: * **Quality & Context:** LLMs perform significantly better with low-resource languages and internet slang/memes. * **Personalization:** Users can modify the prompt to achieve specific translation tones or styles. * **Compatibility:** Support for OpenAI-compatible APIs covers the majority of model providers. * **Cost & Privacy:** Many providers (e.g., Google Gemini, SiliconFlow) offer generous free tiers. Additionally, users can opt for local deployment using tools like Ollama to ensure complete data privacy.

MrUnknownDE closed this issue

2026-04-05 16:16:33 +02:00

MrUnknownDE added the Feature Feature Feature Feature Feature Niche Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Niche Niche Niche Niche Niche Niche labels 2026-04-05 16:16:33 +02:00

Sign in to join this conversation.

No Label Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Niche Niche Niche Niche Niche Niche Niche

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/VRCX#183