Supported languages
There is no language list to pick from — the assistant converses in any language your team writes in, and writes it the way a native speaker from your region would.
How language works
Each person on your team has their own reply language, set during onboarding or simply by telling the assistant. It's stored as a locale — language plus region (say, French as used in Canada, or Arabic as used in Morocco) — so replies follow the spelling, number and date formats, idiom and register of that variant, not a generic translation.
That's all it takes. The preference is saved to your profile and applies to every future conversation — each teammate can work in a different language against the same site.
The reply language
- Replies, explanations and questions come in your chosen language — including clarifying questions, confirmations and error explanations.
- Product and code names stay as they are — field names, component names, CMS terms and brand names aren't translated.
- Write in a different language mid-conversation and the assistant follows you, then asks once whether to make the switch permanent.
Regional variants
Locales are expressed as standard BCP-47 tags, and the variant genuinely changes how the assistant writes:
| Locale | What you get |
|---|---|
en-GB / en-US | Colour/color, organise/organize, 29/10 vs 10/29 dates — full British or American conventions. |
fr-FR / fr-CA / fr-MA | Metropolitan French, Québécois vocabulary, or the register and expressions natural in Morocco. |
es-ES / es-MX | Peninsular or Latin-American Spanish usage. |
pt-PT / pt-BR | European or Brazilian Portuguese. |
ar-MA | Moroccan Arabic (Darija) when you write in Darija; otherwise Modern Standard Arabic with Moroccan conventions. |
zh-CN / zh-TW | Simplified characters with mainland usage, or Traditional characters with Taiwanese usage. |
sr-Latn / sr-Cyrl | Serbian in the alphabet you chose — never mixed. |
ja / ko | Natural polite register, no stray romanisation. |
Your site's content
The language you chat in and the language of your website are deliberately independent. Content the assistant writes into the site — pages, posts, field values, image alt text — follows the site's own language and locale, which it checks against your existing content. A German team member can ask in German for a new landing page on an English site, and the page comes out in English.
- Translations on request — ask for a page in another language, or a translated variant for a specific locale, and that's what gets written.
- Localised CMSs — where your CMS models locales (Contentful locales, WordPress multilingual setups and so on), the assistant writes to the locale you name.
Switching language
- In chat — just say so: "reply in US English from now on", "je préfère le français". The change applies from the next reply and is remembered.
- Per person — language is an individual preference, not a workspace setting. Each teammate's choice only affects their own conversations.
What stays in English
Internal records — audit-log entries, approval notes, memory the assistant keeps about your site and tool transcripts — are kept in English so they can be reviewed consistently, whatever language the conversation happened in. Your replies are unaffected.
