Feature Request: Add multi-language support including Chinese (Simplified & Traditional)

[hiwurun]

Is your feature request related to a problem? Please describe.
Many users (especially in China and other non-English regions) are interested in this great open-source alternative to Claude Cowork. However, the current UI is English-only. We have to rely on system translation tools or third-party software, which often leads to:

• Inaccurate translations (especially for technical terms like "Skills", "Artifacts", "Host Mode", "Permissions")
• Broken UI layout
• Poor user experience on desktop (no seamless switching)

Describe the solution you'd like
Add proper internationalization (i18n) support, so users can switch languages in the app settings.
Priority languages:

• Simplified Chinese (zh-CN)
• Traditional Chinese (zh-TW)
  (English as default/base)

Nice to have in the future: Japanese, Korean, etc.

Additional context

• Project is growing fast and attracting international users.
• Good i18n would greatly improve accessibility and adoption in Asia.
• Many similar desktop tools (Obsidian, VS Code, etc.) have excellent multi-language support via community translations.

I would be happy to help with Chinese translations if the i18n framework is set up (e.g. using react-i18next or similar).

Thanks for building this awesome tool!

[benjaminshafii]

Automated message: thanks for the request. Simplified Chinese support is already landing in dev, and we plan to ship it soon; Traditional Chinese can follow once the key set stabilizes. If you’re willing to help with translations, we can share the key list.

[hiwurun]

Thanks for the quick reply!

I'm a developer and happy to help with the Simplified Chinese translations via a PR.
Please share the key list (or the relevant branch/files) when ready, and I'll prepare and submit the translations.

Looking forward to contributing!

[benjaminshafii]

Thanks for the request — I’m a bot. If you’d like to contribute, a good next step is to propose an i18n framework choice and add a minimal English string table, then we can add zh-CN/zh-TW as the first translation pack. Happy to review a PR once that scaffold is in place.

[benjaminshafii]

Thanks for the request — I am a bot. We do not have full i18n support yet. If you can share your top locales and whether you prefer community translations (e.g., JSON locale files) or a translation platform, that will help us plan the implementation.

[benjaminshafii]

Thanks — I am the OpenWork enterprise bot. Which screens should be prioritized for i18n first, and do you prefer a community translation workflow (JSON or CSV) or built-in locale files?

[OmarMcAdam]

some languages implemented by the community 🫡