openclaw - 💡(How to fix) Fix [Feature]: CLI setup wizard has no i18n — all prompts hardcoded English across 11 files

Summary

The CLI setup wizard (src/wizard/, src/commands/, src/flows/) has no localization support — all user-facing strings are hardcoded in English.

Problem to solve

Every prompt in the setup/onboarding wizard is hardcoded English. For example, in src/wizard/setup.finalize.ts:

const toEnable = await prompter.multiselect({
  message: "Enable hooks?",
  options: [
    { value: "__skip__", label: "Skip for now" },
    ...
  ],
});

And in src/wizard/setup.gateway-config.ts:

message: "Gateway port",
message: "Gateway auth",
message: "Gateway token (blank to generate)",

And in src/commands/onboard-custom.ts:

message: "API Base URL",
placeholder: "https://api.example.com/v1",

None of these strings go through any translation function. There is no t() helper, no locale map, no i18n module for the wizard at all.

Proposed solution

Step 1: Create the i18n module

Add src/wizard/i18n/ with:

• types.ts — type definition for the locale map
• index.ts — a t(key: string) lookup function
• locales/zh-CN.ts — Simplified Chinese translations (~138 wizard strings)
• locales/zh-TW.ts — Traditional Chinese translations (~135 wizard strings)

Step 2: Wrap strings in 11 files

Each file needs:

1. Add import { t } from "../wizard/i18n/index.js";
2. Wrap hardcoded strings with t()

After the change, the code above should look like:

import { t } from "../wizard/i18n/index.js";

const toEnable = await prompter.multiselect({
  message: t("Enable hooks?"),
  options: [
    { value: "__skip__", label: t("Skip for now") },
    ...
  ],
});

Files that need changes:

Alternatives considered

Adding locale keys to the existing Control UI locale files (ui/src/i18n/locales/) was considered, but the wizard code lives outside the UI package and has its own import paths — a standalone i18n module is cleaner and avoids cross-package dependencies.

Impact

• Affected: Non-English-speaking users running openclaw setup or openclaw onboard
• Severity: Medium — does not block setup but forces non-English users to read English prompts throughout a potentially long wizard flow
• Frequency: Every CLI setup/onboarding session
• Consequence: Non-English users get an English-only experience during the entire setup process