Custom translations are saved under wp-content/languages/loco/plugins/ for plugin strings and wp-content/languages/loco/themes/ for theme strings. That keeps edits separate from the plugin or theme's own language directory, so upgrades do not overwrite custom translations. SleekAI's Wizard reads PO and MO files from those locations, so the bot has the exact strings the translator is editing in the Loco admin.

Yes. The system prompt encodes plural form expressions for common locales, including languages with one, two, three, and many forms. When the translator asks about a plural in fr_FR, ru_RU, or ar, the bot quotes the right number of msgstr rows and the conditions for each. That avoids the common mistake of writing all plural variants into msgstr[0] and leaving the other rows empty.

Yes. The Wizard parses the active PO file and exposes a similar-string lookup that finds msgid entries with shared keywords or shared developer comments. The bot can quote those past translations so the translator can keep terminology consistent across the file, useful for plugins where wishlist, cart, and order strings repeat across dozens of surfaces.

Yes. PO files preserve translator-targeted comments that developers added in source via #. comments. Those clarify where a string renders or how it should be tone-matched. SleekAI parses those comments from the PO file and includes them in the chat-request context, so the bot can ground a translation suggestion in the developer's own note rather than guessing from the msgid alone.

No. Display conditions are typically set to the translator role and to the Loco Translate admin URL pattern. Subscribers, contributors, and authors do not see the bot at all, and even editors only see it when they are actively in the Loco admin. That keeps the assistant scoped to the workflow where its context is useful and absent everywhere else on the site.

Yours. SleekAI is bring-your-own-key, so message costs are billed directly by your provider with no SleekWP markup. Use OpenAI, Anthropic, Google, or OpenRouter, and pick a fast model for routine plural lookups and a stronger one for long passages or culturally sensitive tone work under the same chatbot without changing the integration.

Yes. The Wizard scopes the bot to the active text domain and locale at chat-request time, so a translator working on a WooCommerce string sees WooCommerce-specific context, and a translator working on a theme string sees theme context. Switching text domain in the Loco admin switches the bot's context on the next message without any additional configuration on the translator's part.

Not directly. Loco Translate edits PO and MO files, while WPML and Polylang manage translated post and string content via their own tables. SleekAI for Loco focuses on the PO and MO workflow. If your site also runs WPML or Polylang, you can run a separate SleekAI chatbot scoped to those plugins' admin screens with their own field mappings, coexisting under the same SleekAI install.