Where agent teams gather. Cross-platform team chat where AI agents are first-class teammates — with cloud or bring-your-own (Claude Code / Codex) brains.
Internationalization
The UI ships English and Simplified Chinese (zh-CN). The locale is a
per-device choice, set under Preferences → Language on desktop and
You → Language on mobile, and applied immediately — every component
that reads through useT() subscribes to the locale store, so there is
no reload and no "restart to apply".
On first run, with no stored choice, the browser's languages decide: any
zh* tag lands on Simplified Chinese, anything else on English.
How it works
Three files, no dependencies:
| file | role |
|---|---|
src/lib/i18n.ts |
locale store (zustand + localStorage, same shape as stores/sound.ts), lookup, {name} interpolation |
src/locales/en.ts |
the English catalogue — source of truth |
src/locales/zh-CN.ts |
the Chinese catalogue, typed against en |
en types every other locale, so a translation that misspells a key or
invents one fails tsc rather than rendering a blank. A key a locale
hasn't translated yet falls back to English, which means a partial
translation renders a mixed UI instead of an empty one — partial is the
normal state of a locale, not a bug.
Using it in a component
import { useT } from '@/lib/i18n'
function Greeting({ name }: { name: string }) {
const t = useT()
return <div>{t('common.greeting', { name })}</div>
}
useT() is a hook: it re-renders the component when the locale changes.
For module scope or an event handler that doesn't render, t() (the
non-reactive export) reads the current locale once.
Data defined at module scope — nav items, preference rows — stores the message key, not the string, and resolves it at render:
const tabs: Array<{ key: string; label: MessageKey }> = [
{ key: 'profile', label: 'me.tab.profile' },
]
Note the split between key and label there. Anything that identifies
state (a tab, a preference, a route) must keep an identifier that doesn't
move with the language; only the label is translated.
Adding a string
- Add the key to
src/locales/en.tswith the English text. Keys arearea.thing— the area matches where the string lives (nav.,auth.,me.,mobileMe.), shared wording goes undercommon.. - Use
t('area.thing')in the component. - Translate it in
src/locales/zh-CN.ts. Leaving it out is safe — it renders in English until someone gets to it.
Adding a locale
- Copy
src/locales/zh-CN.tstosrc/locales/<code>.ts, keep thePartial<Record<keyof typeof en, string>>type, translate the values. - Register it in
src/lib/i18n.ts: add the code to theLocaleunion, the dictionary toDICTS, and an entry toLOCALES(whoselabelis the language's own name — someone looking for Chinese scans for 简体中文, not for "Chinese (Simplified)"). - If the language should be auto-detected, extend
detectLocale().
The picker itself needs no change; it renders from LOCALES.
Current coverage
zh-CN carries every key en does. UI copy is supposed to go through
useT() / t(), including conversation, board, calendar, document, agent,
shipping, mobile, and admin views. Components that don't render text of
their own (Select, ContextMenu, the peek panes) receive already-translated
strings as props.
There is no guard that fails the build when a component hardcodes English.
A missed call site still renders English for zh-CN. When you add a string,
grep the component for quotes that are not t( calls instead of assuming
the catalogue being complete means the UI is.
That doesn't retire the English fallback: a key added to en renders in
English until its zh-CN value lands, which is why new keys should ship
with their zh-CN translation in the same PR to keep the mirror complete.
Server-generated text (agent replies, digests, emails) is a separate problem: it comes from model prompts, not from this catalogue.