Skip to content
AlumiaDocs

Search docs

Find pages, headings, and concepts. Press ⌘K or Ctrl+K to toggle.

Localization

Interface language across 25 locales (including right-to-left Arabic) and a separate agent response language.

Open in ChatGPTOpen in Claude

Alumia separates two language settings so you can read the app in one language while an agent answers in another.

SettingWhat it controls
App languageThe interface locale — menus, buttons, settings, and chrome. One of 25 supported locales.
Agent response languageThe language agents use for normal replies, summaries, and generated prose.

Both live on the Settings → Profile page and are read/written through GET / PATCH /api/v1/settings/language.

App language

The interface ships in 25 locales: English, Arabic, German, French, Spanish, Italian, Polish, Portuguese, Swedish, Danish, Finnish, Romanian, Czech, Greek, Hungarian, Bulgarian, Lithuanian, Latvian, Estonian, Slovak, Slovenian, Croatian, Maltese, Irish, and Dutch.

  • English is the base catalog. Every other locale is a translation layered on top of English, so any string a locale hasn't translated yet falls back to English rather than showing a blank.
  • Arabic is right-to-left. When the app locale is Arabic, the document renders RTL (<html dir="rtl">) and the layout mirrors. Technical text — code, identifiers, URLs — stays left-to-right.
  • Resolution order. Alumia picks your locale from the alumia_locale cookie, then your saved profile locale, then the browser Accept-Language header, and finally English. Changing the picker updates the cookie (kept for a year) and your profile.

Unsupported language tags resolve to the closest supported locale, or English if there's no match.

Agent response language

The agent response language is independent of the interface. Set it when you want an agent to reply in a language other than the one you read the app in — for example, browse Alumia in English but have an agent draft in French.

  • It accepts any valid language tag, not just the 25 app locales.
  • If you leave it unset, agents follow your interface/profile language.
  • Right-to-left languages (Arabic, Persian, Hebrew, Urdu) are detected so generated prose renders in the correct direction.
  • An agent can switch its own response language mid-conversation when you explicitly ask it to; it won't change languages on its own.

API

# Read current language settings
curl -H "Authorization: Bearer $ALUMIA_API_KEY" \
  https://app.alumia.com/api/v1/settings/language

# Switch the interface to Arabic and have agents answer in French
curl -X PATCH -H "Authorization: Bearer $ALUMIA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"locale":"ar","agentCommunicationLocale":"fr"}' \
  https://app.alumia.com/api/v1/settings/language

PATCH accepts locale, agentCommunicationLocale, or both — at least one is required. See User and organization for the full response shape.