AGENT_REACH_LANG=en still shows Chinese output in agent-reach doctor
Agent-Reach v1.5.0 ignores AGENT_REACH_LANG=en:
agent-reach doctorrenders entirely in Chinese on Windows 11 and macOS, anddoctor --jsonreturns Chinese values too. Why is the locale setting not honored, and is there a fix?Originally asked on GitHub: https://github.com/Panniantong/Agent-Reach/issues/553
3 answers
Status: still open as of 2026-10-08; no released fix yet.
Root cause (found by a commenter in the thread):
AGENT_REACH_LANGis read in exactly one place —_skill_resource_name()inside_install_skill(cli.py:475–487) — where its only effect is choosingSKILL_en.mdoverSKILL.md. Nothing on the runtime path consults it, and there is no shared locale helper, sodoctor.pyandchannels/*.pyemit hardcoded strings regardless of the variable.doctor --jsonis affected the same way.Workaround that worked in the thread: build and run PR #595 locally. The commenter who tested it reports it resolves the issue completely — headings, channel names, backends and diagnostics all render in English, Chinese remains the default, and the JSON contract is unchanged. The branch is 1 ahead / 5 behind
main, and the five upstream commits are README and sponsor edits with no code changes, so it should still apply cleanly.Related PRs: #490 (translates 28 files, closed unmerged), #560 (same doctor fix, closed unmerged), #599 (ships English
references/files, open). Note that an English-locale install currently lands seven Chinese reference files next to an EnglishSKILL.md, anddocs/README_en.mdshows English doctor output that the current code cannot produce.General advice: if you cannot build from the PR, watch #595 for merge status — the thread contains no other released workaround.
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Reporter set AGENT_REACH_LANG=en (the recommended setting) and ran
agent-reach doctor; all output was still rendered in Chinese, including the channel status table.Source: https://github.com/Panniantong/Agent-Reach/issues/553 (opens external site)
Did this work for you?What @bhaveshpatelapple tried on GitHub (Worked)
Commenter traced the env var usage in cli.py, then built and ran PR #595 locally; doctor output rendered fully in English while keeping Chinese as the default and preserving the JSON contract.
Source: https://github.com/Panniantong/Agent-Reach/issues/553#issuecomment-5496597225 (opens external site)
Did this work for you?
Related questions
- How to get LinkedIn and Instagram contacts in Agent-Reach when their APIs are deprecated?
- bird CLI 'fetch failed' on Twitter search in Agent-Reach: proxy not used by Node fetch
- agent-reach Instagram cookies fail: redirected to login / 'Something went wrong'?
- OpenClaw keeps failing to install Agent-Reach skill (exec/communication errors) — correct install flow?
- Long Twitter tweets truncated at "Show more" in Agent-Reach MCP — how to get full text?