Interface languages
The console has one interface-language preference for each authenticated controller user. The same React components use it in the terminal, browser and desktop application. Open Settings → Interface language to select English, Russian, German, French, Spanish, Italian, Portuguese, Polish, Czech, Ukrainian, Dutch, Swedish, Japanese or Simplified Chinese.
All 14 languages cover the registered built-in interface messages. Navigation, forms, inventories, access controls, session operations, tooling releases and operation feedback use the same explicit display keys in TUI, web and Tauri. Translations receive semantic review, including a separate pass over security warnings. Language settings report the actual translated and total catalog entries; tests require complete registered coverage for every locale. English fallback remains available for a missing future message and never counts as a translation. Project names, accounts, repositories, model IDs, commands, agent output and upstream diagnostic prose stay in their original form. Changing language does not restart an agent or replace an open conversation.
Public website
The homepage and comparison page use the same 14 language IDs. English is at
https://devctrl.dev/; other versions use paths such as /ru/, /ja/ and
/zh-CN/, with their comparisons at /ru/compare/, etc. Choose a language in
the site header. The current section or comparison feature stays selected.
These are static pages with localized metadata and hreflang alternates;
reading them does not require a controller or account. Website language lives
in the URL and does not modify the controller-user preference.
The terminal player's controls, chapter labels and explanations are translated. The original CLI recording is unchanged. The interactive browser demo seeds its private sample preference from the page language and reuses the console's registered translation catalogs. Product names, code, commands, source links, comparison evidence statuses and technical identifiers are preserved. See landing translation maintenance.
Preference API and MCP
Authenticated clients can read GET /v1/preferences/language. The response is {"language":"en","revision":0} before the first save. Reading never writes a default. Update with PUT /v1/preferences/language and {"language":"de","revision":0}; the response contains the next revision. A stale revision returns 409: reload before trying again. Unknown locales, additional fields and invalid revisions return 400. The current authenticated user owns the preference; requests cannot choose another owner.
Both operations appear in the existing operator operation catalog and can be used through its MCP adapter. Preferences use the controller's normal durable user storage, authentication and audit trail. They are not included in public session-share pages.
Shared forms and operation feedback
Management forms, MCP approvals, access inventory, server users, folder grants, network settings, provider setup, Control Room, Decisions API and Overnight use explicit labels. A localized label never changes a confirmation word, checkbox payload, scope ID, method name, permission or risk category. Inventory rows keep their raw state separately from the translated caption, preserving status colors and allowing searches by either form. Unknown custom fields remain literal.
Local feedback is stored as a message key and parameters, so a visible progress or validation notice can change language without repeating an operation. Failure styling uses a separate semantic flag. External errors are not translated merely because their text resembles a built-in message or carries a similarly named property. Paths, endpoints, model IDs and user values interpolate literally; they are never HTML or executable templates.
Release groups, importance labels, recommendations and update-history controls share the interface preference. Upstream release-note prose remains original. Translated text cannot change whether a release is critical, whether a model exists or whether an update was applied.
The native Tauri connection window also uses the shared connection catalogs. These are source changes: an already installed desktop or mobile binary needs a new build to receive them. Language work does not rebuild, install or launch native applications automatically.
Maintaining translations
packages/i18n/src/catalogs/en.json is the public English catalog. Stable ui.<hash> keys identify explicit source messages. Semantic messages for the language picker are in core-catalogs.ts. Each other locale has a separate JSON catalog. packages/i18n/generate.mjs validates exact known keys and named placeholders, preserved URLs, allowed writing systems and the absence of terminal controls, then generates a browser-safe TypeScript catalog. Invalid draft entries are rejected; they are never counted as translated. translationCoverage counts actual catalog entries, not English fallback.
Only explicit t(key, parameters), <Message> references and <Localized messages={{prop: key}}> properties are translated. Rich parameters remain React nodes and are never interpreted as HTML. Native nativeLabel overrides require their own explicit reference. Resource names and arbitrary runtime text never pass through a text-matching translator. ANSI/OSC control sequences and pure URLs are excluded from source extraction.
Goal lifecycle and budget labels, native model provenance, detach and connection diagnostics, project-view controls and internal progress-refresh feedback also use explicit semantic session messages. Goal objectives, model IDs, observed token counts, agent answers and server error details remain unchanged. A translated lifecycle label never creates a completion percentage or changes the observed native state. Authorization colors use a separate semantic state; a translated sign-in label cannot change a healthy account into a warning. The detached Ink attach-progress frame receives the same selected language without another HTTP request, while native terminal output passes through unchanged.
Settings menu titles, descriptions, audit and streaming policy fields, operation feedback and empty-state labels use explicit display keys. Counts use the selected locale's number formatter. Internal section IDs, API routes, JSON field names, numeric option values and collector query parameters remain unchanged; raw server errors are displayed verbatim.
The web shell translates its main header controls, sign-in labels and introduction, connection statuses and download progress through the separate @devctl/i18n/shell catalog. Its small pre-auth bundle does not include the full UI catalogs or add a request before the application download. A validated, non-secret language hint on this device supplies the initial display language; the authenticated controller preference overrides it when loaded. Only a successfully loaded or saved preference updates that hint. Form values, access keys, native errors and backend responses remain unchanged.
The separate connection catalog covers long sign-in help, saved-console management, host invitations and the shared desktop SSH onboarding source. Rich help preserves actual code elements for commands; parameters are inserted as text or existing DOM nodes, never HTML. Server names, addresses, SSH fingerprints and passwords stay unchanged. The native setup protocol carries explicit notice keys alongside its original English diagnostics, so new clients can translate known progress and validation messages without interpreting arbitrary SSH or server output. Browser fixtures exercise the shared onboarding source with mock native calls; this does not imply that an older installed native application has received the new translations. The separate exchange catalog covers the browser file navigator, sort and filter controls, keyboard hints, upload progress, known file types and repository/service/provider pickers. It preserves filenames, paths, IDs, upload bytes, exact API values and upstream errors. Dynamic session, context, resource pressure, quota, freshness, synchronization and context-tool stages have reviewed semantic translations. The separate @devctl/i18n/browser catalog covers notification registration and permissions, browser installation help, private-link input validation, terminal connection notices, clipboard and session file-drop feedback, and anonymous public-session headers and controls. Public viewers read only the validated device hint and never request authenticated language preferences. Known activity and goal state codes are localized; session names, objectives, native model evidence and terminal bytes remain unchanged. Only locally constructed typed notices are translated; upstream errors cannot opt in by supplying a matching property or English message. Browser fixtures cover Russian and Japanese at desktop and mobile widths, including metadata updates without private API requests. Unknown server and native diagnostics remain verbatim, with no matching or replacement of their English text.
Session-sharing lifetimes, access roles, expiry dates, control warnings and local operation results use explicit interaction messages. Link IDs, tokens, roles sent to the API and lifetime values are unchanged. Voice input and settings localize their own recording stages, service choices and local microphone notices; recognized speech remains an editable raw draft. Local notice descriptors stay reactive when the language changes, while external/native diagnostics remain verbatim. Browser audio validation uses typed local errors rather than guessing from English words. No audio is sent merely by changing language or opening settings.
docker/i18n-audit.mjs inventories source messages without changing files. docker/i18n-apply.mjs applies explicit JSX references to the frozen catalog. Review generated edits and run renderer tests before committing them. The inventory covers static JSX messages and selected labeled properties. Dynamic status mappings and helper-produced messages have separate explicit catalogs and renderer tests. Catalog completeness does not translate arbitrary agent output, external commands or third-party startup shells.
The optional docker/i18n-translate.mjs utility can draft bounded public-catalog batches through an already configured loopback Ollama endpoint. It neither downloads models nor sends source files, credentials or user data. Draft generation is currently stopped after quality review found incorrect terminology and mixed writing systems. Further locale work uses explicit human or agent review rather than unattended machine batches. Product names, commands, paths, hotkeys and interpolation tokens must be preserved; automated validation does not establish semantic correctness.