openclaw - ✅(Solved) Fix [Bug]: Control UI mixes languages (spanish/english) [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#49934Fetched 2026-04-08 01:01:04
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×2commented ×1cross-referenced ×1mentioned ×1

Bug: Control UI tiene mezcla de idiomas (español/inglés)

The OpenClaw Control UI displays a mix of Spanish and English text, even when the browser language is set to English only.

Environment:

  • OpenClaw version: 2026.3.13
  • OS: Linux

Additional context:

  • This appears to be an i18n bug in the Control UI
  • Some strings are translated while others are missing from the language files

Root Cause

Bug: Control UI tiene mezcla de idiomas (español/inglés)

The OpenClaw Control UI displays a mix of Spanish and English text, even when the browser language is set to English only.

Environment:

  • OpenClaw version: 2026.3.13
  • OS: Linux

Additional context:

  • This appears to be an i18n bug in the Control UI
  • Some strings are translated while others are missing from the language files

Fix Action

Fixed

PR fix notes

PR #52627: Control UI: fix Spanish overview fallbacks

Description (problem / solution / changelog)

Summary

AI-assisted: Yes. Implemented with Codex, then reviewed locally.

Describe the problem and fix in 2–5 bullets:

  • Problem: the Control UI overview could show mixed Spanish and English because several overview-entry translation keys were missing from ui/src/i18n/locales/es.ts, and ui/src/ui/views/overview-cards.ts still hardcoded English status copy.
  • Why it matters: users selecting Spanish saw obvious mixed-language UI on the first Control UI surfaces, which made the i18n experience look broken.
  • What changed: added the missing Spanish translations for the reproduced overview/navigation/palette surfaces, and replaced the overview card hardcoded English strings with localized t(...) keys.
  • What did NOT change (scope boundary): this PR does not translate the broader usage.* Spanish surface; remaining untranslated usage strings are outside the issue's reproduced overview-entry scope.

Change Type (select all)

  • Bug fix
  • Feature
  • Refactor required for the fix
  • Docs
  • Security hardening
  • Chore/infra

Scope (select all touched areas)

  • Gateway / orchestration
  • Skills / tool execution
  • Auth / tokens
  • Memory / storage
  • Integrations
  • API / contracts
  • UI / DX
  • CI/CD / infra

Linked Issue/PR

  • Closes #49934
  • Related #48209

User-visible / Behavior Changes

  • Spanish locale now localizes the overview connection helper, overview cards, event log/log tail headings, and the command palette/section labels touched on the entry surfaces.
  • Overview cards no longer show hardcoded English snippets like 0 jobs or Active: 0 under Spanish locale.

Security Impact (required)

  • New permissions/capabilities? (Yes/No): No
  • Secrets/tokens handling changed? (Yes/No): No
  • New/changed network calls? (Yes/No): No
  • Command/tool execution surface changed? (Yes/No): No
  • Data access scope changed? (Yes/No): No
  • If any Yes, explain risk + mitigation:

Repro + Verification

Environment

  • OS: macOS 15 local dev
  • Runtime/container: Node 22.16.0 / pnpm 10.23.0
  • Model/provider: N/A
  • Integration/channel (if any): Control UI only
  • Relevant config (redacted): rendered overview with settings.locale = "es"

Steps

  1. Load the Control UI overview with Spanish selected.
  2. Render disconnected overview surfaces with usage/session/skills/event-log data.
  3. Inspect the connection helper, overview cards, event log/log tail headings, and palette/navigation copy.

Expected

  • The reproduced overview-entry surfaces remain Spanish-only.

Actual

  • Before this change, those surfaces could mix in English strings such as How to connect, Event Log, Gateway Logs, 0 jobs, and Active: 0.

Evidence

Attach at least one:

  • Failing test/log before + passing after
  • Trace/log snippets
  • Screenshot/recording
  • Perf numbers (if relevant)

Human Verification (required)

What you personally verified (not just CI), and how:

  • Verified scenarios: pnpm test -- ui/src/ui/views/chat.test.ts passes with the new Spanish overview regression assertions; direct translation lookups for the added navigation/palette keys also pass in that test file.
  • Edge cases checked: zero cron jobs, zero enabled skills, populated event log/log tail surfaces, and locale reset back to English after the Spanish assertions.
  • What you did not verify: manual browser walkthrough on Ubuntu/Linux; broader usage.* Spanish completeness beyond the reproduced overview-entry surfaces.

Review Conversations

  • I replied to or resolved every bot review conversation I addressed in this PR.
  • I left unresolved only the conversations that still need reviewer or maintainer judgment.

If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.

Compatibility / Migration

  • Backward compatible? (Yes/No): Yes
  • Config/env changes? (Yes/No): No
  • Migration needed? (Yes/No): No
  • If yes, exact upgrade steps:

Failure Recovery (if this breaks)

  • How to disable/revert this change quickly: revert commit 61a5f1be68.
  • Files/config to restore: ui/src/i18n/locales/es.ts, ui/src/i18n/locales/en.ts, ui/src/ui/views/overview-cards.ts, ui/src/ui/views/chat.test.ts
  • Known bad symptoms reviewers should watch for: overview cards or connection helper switching back to English under Spanish locale.

Risks and Mitigations

List only real risks for this PR. Add/remove entries as needed. If none, write None.

  • Risk: broader usage.* Spanish gaps still exist and may still surface mixed English outside the specific overview-entry surfaces fixed here.
    • Mitigation: scope is intentionally limited to the reproduced issue surface; the regression test asserts those overview-entry surfaces no longer fall back to English.

Additional verification notes:

  • codex review --base origin/main was rerun locally and did not produce any new actionable findings; it only kept scanning broader untranslated Spanish usage strings outside this issue's scope.
  • pnpm build is currently red on unrelated repo baseline issues (@whiskeysockets/baileys unresolved jimp).
  • pnpm check is currently red on unrelated repo baseline issues in extensions/matrix, extensions/openai, extensions/tlon, and src/agents/anthropic-vertex-stream.ts.
  • pnpm test full-suite currently hits unrelated repo baseline failures in src/acp/control-plane/manager.test.ts and src/plugin-sdk/subpaths.test.ts.

Changed files

  • ui/src/i18n/locales/en.ts (modified, +186/-0)
  • ui/src/i18n/locales/es.ts (modified, +232/-0)
  • ui/src/ui/app-render.ts (modified, +4/-4)
  • ui/src/ui/views/chat.test.ts (modified, +259/-0)
  • ui/src/ui/views/command-palette.ts (modified, +46/-24)
  • ui/src/ui/views/config-form.render.ts (modified, +18/-2)
  • ui/src/ui/views/config-form.ts (modified, +6/-1)
  • ui/src/ui/views/config.ts (modified, +73/-7)
  • ui/src/ui/views/overview-cards.ts (modified, +10/-4)
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Summary

Bug: Control UI tiene mezcla de idiomas (español/inglés)

The OpenClaw Control UI displays a mix of Spanish and English text, even when the browser language is set to English only.

Environment:

  • OpenClaw version: 2026.3.13
  • OS: Linux

Additional context:

  • This appears to be an i18n bug in the Control UI
  • Some strings are translated while others are missing from the language files

Steps to reproduce

Steps to reproduce:

  1. Set browser language to English (en-US)
  2. Access OpenClaw Control UI
  3. Observe that some UI elements are in Spanish while others are in English

Expected behavior

Expected behavior: The entire Control UI should display in English, or there should be a configuration option to force a specific language.

Actual behavior

Actual behavior:

  • Mix of Spanish and English text in the UI
  • No available configuration option to force language to English
  • Language settings changes in openclaw.json have no effect

OpenClaw version

2026.3.13

Operating system

Ubuntu 24.04

Install method

npm global

Model

minimax-2.5

Provider / routing chain

openclaw -> openrouter -> minimax

Config file / key location

No response

Additional provider/model setup details

<img width="2032" height="1167" alt="Image" src="https://github.com/user-attachments/assets/ea63009b-0af2-43c6-90c4-186cf6f8dbe9" />

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

To fix the i18n bug in the OpenClaw Control UI, we need to ensure that all UI elements are translated to the selected language. Here are the steps:

  • Update the language files to include missing translations.
  • Add a configuration option to force a specific language.
  • Modify the UI code to use the selected language.

Code Changes

// Add a language configuration option to openclaw.json
{
  "language: en-US"
}

// Update the UI code to use the selected language
import { language } from './openclaw.json';

// Use the language variable to translate UI elements
function translate(text) {
  if (language === 'en-US') {
    return text.en;
  } else {
    return text.es;
  }
}

Configuration Changes

  • Add a language key to the openclaw.json file with the desired language code (e.g., en-US).
  • Update the openclaw.json file to include the missing translations.

Verification

To verify that the fix worked, follow these steps:

  1. Set the browser language to English (en-US).
  2. Access the OpenClaw Control UI.
  3. Observe that all UI elements are displayed in English.

Extra Tips

  • Make sure to update all language files to include the missing translations.
  • Consider adding a fallback language in case the selected language is not available.
  • Use a consistent naming convention for language codes (e.g., en-US instead of english).

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Expected behavior: The entire Control UI should display in English, or there should be a configuration option to force a specific language.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix [Bug]: Control UI mixes languages (spanish/english) [1 pull requests, 1 comments, 2 participants]