Auto-translate missing strings

LangSync has three flavours of AI translation, used in different contexts:

• Batch auto-translate – fill every missing cell across one or more languages in a namespace.
• Single-cell recommendation – get the AI's suggestion for one translation, review, then save.
• Manual translation – stream a translation for arbitrary text not tied to a term.

Batch auto-translate

1. Open the namespace and click Terms.
2. Click Translate missing (top of the list).
3. (Optional) Pick a subset of languages – by default, all attached target languages.
4. Confirm.

The job runs in the background. Refresh the page to see progress. Filled cells appear with an "AI" badge until you edit them.

The same flow runs automatically at the end of a sync job if you don't opt out – perfect for CI.

Single-cell AI recommendation

When you don't want to commit a full batch but want a starting point for one cell:

1. Click the empty cell in the terms grid.
2. Click AI recommend.
3. Optionally choose a custom prompt for tone/register, and override the source language if you want to translate from a non-default.
4. The AI's suggestion appears in the cell. Edit if needed and save.

Manual translation

The Manual translation page is for strings that aren't terms – for example, a one-off marketing tagline you're drafting in the dashboard before committing to a copywriter.

1. Pick a source and target language.
2. Type or paste source text. The translation streams in as you type (debounced).
3. Toggle Use glossary if you want the org glossary applied.
4. Optionally pick a custom prompt.
5. Copy the result.

Manual translations are not stored in any namespace.

What gets billed

• A term × language pair is billed once it has a non-empty translation stored. Empty translations are free.
• AI calls themselves are part of the platform's bundled compute – they don't have a separate per-call charge – but rate limits apply (see Limits).
• Manual translation calls don't store anything, so they don't add to storage billing – but they still count against the rate limit.

What's next

• Use a glossary – improve translation consistency before running big batches.
• Sync jobs – CI-driven push that auto-translates as part of the pipeline.