v1.0.1 — 🌐 Fourteen languages, actually
🌐 Fourteen languages, actually
This office ships worldwide, and 1.0.0 quietly assumed otherwise in three
places. Nothing here changes behaviour — it changes what the product says, and
to whom.
The Tools page read English in 12 of the 14 languages
The site's language files cover page chrome. The tool descriptions live in
the catalog, which only ever carried English and Thai — so a reader in Japanese
or Arabic got a fully translated page wrapped around English cards.
All 79 catalog strings are now translated into every supported language, in
per-language overlay files fetched on demand and keyed by the English source,
with English as the fallback.
"Falls back to English" is not the same as "supported".
Three settings had no stable name outside Thai
Every field in the chat window leads with an ALL-CAPS English term — 🔌 MCP
SERVERS, ⚡ SYSTEM TOOLS, 🔑 API KEYS — with the local-language gloss after it.
That is not decoration. The window is Thai-source and a DOM pass
machine-translates it at runtime, so the English term is the part that
survives unchanged: it is the name an English office actually shows, and the
only name the documentation can cite.
The settings added in 1.0.0 were Thai-only. They are now:
| 📦 RUN LOCATION | where an agent's work runs — this machine, a container, another box |
| 🔎 SEMANTIC RECALL | search memory by meaning, not only by words |
| 👻 GHOST ISOLATION | give each parallel ghost its own git worktree |
The English guide cited Thai labels
Doubly wrong: a reader of an English page is running an English office and would
never see them. Those pages cite the English names now, and the example of a
word-match failure that ran in Thai runs in English on the English-facing pages.
Tests, so this holds without vigilance
CI now fails if a language loses its overlay file, if any English string is
untranslated in any language, if a file keeps a string the catalog has dropped,
or if a "translation" is just the English copied through — the failure that
looks like success, because the key is present, the card renders, and the
reader still gets English.
Full detail: CHANGELOG.md