Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix Feature Request: i18n / Multi-Language Support for System Messages [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
NousResearch/hermes-agent#16546•Fetched 2026-04-28 06:52:39
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
NickLJingNickLJing
Participants
alt-glitchalt-glitchNickLJingNickLJing
Timeline (top)
labeled ×3commented ×1

Error Message

Currently, all system-level messages generated by Hermes Agent are hardcoded in English — interrupt notices (⚡ Interrupting current task...), tool approval prompts (⚠️ Dangerous command requires approval...), background process notifications, error messages, etc. For non-English-speaking users (e.g., Chinese), this creates an inconsistent experience: the agent responds fluently in Chinese, but system messages drop into English mid-conversation.

  • Error and timeout messages

Code Example

# Now:
"⚡ Interrupting current task (2 min elapsed, iteration 2/90). I will respond to your message shortly."

# Expected (zh_CN):
"⚡ 正在中断当前任务（已运行 2 分钟，第 2/90 轮）。稍后回复你的消息。"
RAW_BUFFERClick to expand / collapse

Feature Request: i18n / Multi-Language Support for System Messages

Problem

Currently, all system-level messages generated by Hermes Agent are hardcoded in English — interrupt notices (⚡ Interrupting current task...), tool approval prompts (⚠️ Dangerous command requires approval...), background process notifications, error messages, etc. For non-English-speaking users (e.g., Chinese), this creates an inconsistent experience: the agent responds fluently in Chinese, but system messages drop into English mid-conversation.

Proposed Solution

Add i18n support for system messages:

  1. Extract all user-facing system strings into locale files (e.g., locales/zh_CN.yaml, locales/ja.yaml)
  2. Auto-detect locale from the user's OS language ($LANG) or config.yaml setting
  3. Fallback to English when a locale is unavailable
  4. Phase 1 scope: gateway system messages, interrupt notices, tool approval prompts, cron delivery headers

Affected Components

  • Gateway interrupt/pause/resume messages
  • Tool approval / dangerous command confirmation prompts
  • Cron job delivery formatting
  • Error and timeout messages
  • Memory save confirmation messages

Example

# Now:
"⚡ Interrupting current task (2 min elapsed, iteration 2/90). I will respond to your message shortly."

# Expected (zh_CN):
"⚡ 正在中断当前任务（已运行 2 分钟，第 2/90 轮）。稍后回复你的消息。"

Additional Context

  • User base includes multiple non-English platforms (Weixin/WeChat, DingTalk, Feishu, QQ Bot)
  • The agent already correctly switches to the user's preferred language for conversation responses
  • System prompt could include locale preference for full-system i18n

extent analysis

TL;DR

Implementing i18n support for system messages by extracting strings into locale files and auto-detecting the user's locale is the most likely fix.

Guidance

  • Extract all user-facing system strings into locale files (e.g., locales/zh_CN.yaml, locales/ja.yaml) to support multiple languages.
  • Auto-detect the user's locale from the OS language ($LANG) or config.yaml setting to ensure the correct language is used.
  • Implement a fallback to English when a locale is unavailable to prevent errors.
  • Start with the Phase 1 scope, which includes gateway system messages, interrupt notices, tool approval prompts, and cron delivery headers.

Example

# locales/zh_CN.yaml
interrupt_notice: "⚡ 正在中断当前任务（已运行 {elapsed_time}，第 {iteration}/{total} 轮）。稍后回复你的消息。"

Notes

This solution assumes that the agent's conversation responses are already correctly switching to the user's preferred language. Additional work may be required to fully integrate i18n support for all system messages.

Recommendation

Apply the proposed solution to add i18n support for system messages, as it will improve the user experience for non-English-speaking users and provide a more consistent interaction with the agent.

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…
#optimization#mixed precision#training loop#device allocation#model download

Still need to ship something?

×6

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

Back to top recommendations

TRENDING