openclaw - 💡(How to fix) Fix [Feature]: Add i18n support to CLI setup wizard (onboarding, gateway config, channel setup)

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…

The CLI setup wizard (onboarding, channel setup, gateway config, plugin config, etc.) has no i18n support — all user-facing prompts, labels, hints, and options are hardcoded English strings.

Root Cause

The CLI setup wizard (onboarding, channel setup, gateway config, plugin config, etc.) has no i18n support — all user-facing prompts, labels, hints, and options are hardcoded English strings.

RAW_BUFFERClick to expand / collapse

Summary

The CLI setup wizard (onboarding, channel setup, gateway config, plugin config, etc.) has no i18n support — all user-facing prompts, labels, hints, and options are hardcoded English strings.

Problem to solve

The wizard files under src/wizard/, src/commands/, and src/flows/ display English-only text regardless of the user's locale. Non-English speakers doing openclaw setup or openclaw onboard see untranslated prompts like "Gateway port", "Enable hooks?", "Select channel" etc.

There is no t() helper or locale map wired into the wizard system at all.

Proposed solution

Create a src/wizard/i18n/ module with:

  • types.ts — type definition for the locale map
  • index.ts — a t() helper function that looks up translated strings
  • locales/zh-CN.ts — Simplified Chinese locale map
  • locales/zh-TW.ts — Traditional Chinese locale map

Then add import { t } and wrap hardcoded strings with t() in these files (files with changes needed):

  • src/commands/onboard-custom.ts — ~10 strings
  • src/commands/onboard-hooks.ts — ~2 strings
  • src/commands/onboard-remote.ts — ~12 strings
  • src/commands/onboard-skills.ts — ~5 strings
  • src/flows/channel-setup.ts — ~6 strings
  • src/wizard/setup.finalize.ts — ~5 strings
  • src/wizard/setup.gateway-config.ts — ~13 strings
  • src/wizard/setup.migration-import.ts — ~6 strings
  • src/wizard/setup.official-plugins.ts — ~2 strings
  • src/wizard/setup.plugin-config.ts — ~4 strings
  • src/wizard/setup.ts — ~8 strings

Alternatives considered

Adding locale entries to existing locale files (ui/src/i18n/locales/) was considered, but the wizard code lives outside the UI package and has its own import paths, so a standalone i18n module is cleaner.

Impact

  • Affected: Non-English-speaking users running CLI setup/onboarding
  • Severity: Medium — does not block setup but creates poor UX for non-English users
  • Frequency: Every CLI setup/onboarding session
  • Consequence: Chinese/other locale users see English-only prompts during the entire wizard flow

Evidence/examples

Confirmed by reading the current source — none of the listed files have an import { t } statement or any wrapped strings.

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…

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 - 💡(How to fix) Fix [Feature]: Add i18n support to CLI setup wizard (onboarding, gateway config, channel setup)