openclaw - 💡(How to fix) Fix [Feature]: Russian language support for QCLAW_FORCE_RESPONSE_LANGUAGE [1 comments, 2 participants]

Summary

Add Russian (ru) language support to the QCLAW_FORCE_RESPONSE_LANGUAGE setting in the OpenClaw Control UI, allowing agents to respond in Russian.

Problem to solve

Users who prefer Russian have no way to switch the agent's response language through the Control UI settings. The QCLAW_FORCE_RESPONSE_LANGUAGE tag only supports English — there is no Russian (ru) option in the language dropdown. Users must patch the compiled app binary to get Russian responses, which is unsafe and not supported.

Proposed solution

Add ru: "Русский" to the language map in the Control UI renderer. The relevant code is in the renderer bundle (e.g. out/renderer/assets/c-DYOCP9_1.js), where the language map currently reads:

Ar = {zh:"Simplified Chinese", en:"English", ja:"Japanese", ko:"Korean", es:"Spanish", fr:"French"}

Alternatives considered

The fix requires:

1. Adding ru: "Русский" to the language map
2. Emitting "language":"ru" when Russian is selected in the UI language dropdown
3. Adding Russian translations for UI strings (if required by the rendering layer)

This is a small, isolated change with no impact on existing functionality.

Impact

• Affected users/systems/channels: All OpenClaw users who prefer Russian as their agent language
• Severity: Annoying — does not block work but forces English-only interaction or unsafe patching
• Frequency: Always for affected users
• Consequence: Users either accept English-only responses or risk app breakage by patching binary files

Evidence/examples

Current language map in out/renderer/assets/c-DYOCP9_1.js:

Ar = {zh:"Simplified Chinese", en:"English", ja:"Japanese", ko:"Korean", es:"Spanish", fr:"French"}

The QCLAW_FORCE_RESPONSE_LANGUAGE tag emitted by the Control UI:

¥¥[QCLAW_FORCE_RESPONSE_LANGUAGE] You MUST respond ONLY in English. ¥¥

If ru were added, it would emit:

¥¥[QCLAW_FORCE_RESPONSE_LANGUAGE] You MUST respond ONLY in Russian. ¥¥

Additional information

• OS: Windows (confirmed)
• The change is purely additive — no existing languages or functionality are affected
• No API changes required — only the UI language selector and the emitted tag value
• This issue was discovered while trying to use OpenClaw with Russian-speaking users; it is a real and recurring pain point