Changelog
What shipped, week by week.
- W36 – Retranslate specific pieces, down to a single keyRetranslate specific pieces of your content, down to a single key, without redoing everything else. Name the keys with lingo push --key, redo whole files with --force, or redo one language with purge and --backfill-missing. Do the same from a pull request with /lingo translate, and let your AI coding assistant write the key selection.September 6, 2026
- W35 – Translate your Payload CMS contentConnect a Payload CMS to a localization engine you host on Lingo.dev, pick the collections and globals to cover, and Lingo.dev translates their localized fields into your target locales, with the results written back to Payload under each locale. Every run goes through your localization engine's full pipeline, including internal and external human review. Sync sends only what changed.August 30, 2026
- W34 – Translate your Zendesk Help CenterConnect a Zendesk Help Center to a localization engine you host on Lingo.dev and translate its categories, sections, and articles into every target language, with the results written back to Zendesk as per-locale versions. Every run goes through your localization engine's full pipeline, including internal and external human review. Sync sends only what changed.August 23, 2026
- W33 – Route only low-scoring translations to human reviewHuman review becomes selective. Set a quality threshold and only translations that score below it are routed to a reviewer, while everything at or above it ships automatically. Reviewers focus on what needs a fix and review cost drops.August 16, 2026
- W32 – Add glossary terms in bulk from the MCP serverSeed a glossary from your AI assistant through the MCP server in one step, across as many locales as you need. What used to take a long stream of one-term-at-a-time calls now happens in a single, much faster pass. Plus smaller improvements: Docusaurus output paths in the CLI, and fuller YAML frontmatter translation.August 9, 2026
- W31 – Glossaries, rulesets, and brand voices move to the organization levelGlossaries, rulesets, and brand voices are now organization assets you attach to any engine, so you configure them once and reuse them instead of rebuilding per engine. An internal team member can take over a translation waiting on external review. The CLI writes framework-correct output paths for Rails, Android, Xcode, and Flutter, with a runnable example repo per framework.August 2, 2026
- W30 – Engine Suggestions learn from human editsEngine Suggestions now also come from the corrections human reviewers make, not just low AI-review scores: a fix that recurs across jobs becomes a proposed glossary, instruction, or brand-voice edit. Suggestions can now be approved or dismissed in bulk.July 26, 2026
- W29 – AI review false positives down 59.7%AI reviews cut false positives by 59.7%. The GitHub App localizes Xcode String Catalogs (.xcstrings). Request logs show the source file path for lingo push runs.July 19, 2026
- W28 – Estimate translation cost upfront: `lingo push --estimate``lingo push --estimate` reports what translating will cost before any translation runs. The CLI uploads the source bytes so the server plans the exact delta against what's already localized, prints the estimate, and exits without spending credits.July 12, 2026
- W27 – Async CLI file formats: TypeScript, YAML, PO, Flutter, Android, XcodeThe async CLI adds file-format support for TypeScript locale modules, YAML, Gettext PO, Flutter ARB, Android strings, and Xcode .strings, String Catalogs (.xcstrings), and .stringsdict. Translatable text runs through your engine's full pipeline; keys, IDs, metadata, and placeholders stay put.July 5, 2026
- W26 – New Lingo.dev CLI: `lingo push` runs your engine's full localization pipelineIntroducing the new Lingo.dev CLI. Every `lingo push` runs your localization engine's full configured pipeline server-side – pre-edit, core localization with your glossary and brand voice, human review, AI review, rephrase, and back-translation – the same pipeline the Async Localization API runs from code.June 28, 2026
- W25 – Localization Engine Suggestions: low AI-review scores propose the glossary, instruction, or brand-voice editLocalization Engine Suggestions proposes a glossary, instruction, or brand-voice edit whenever AI reviews on a translation come back low. Apply writes the change into the localization engine, and the next translation runs with the fix in place.June 21, 2026
- W24 – Rephrase: a new stage in the localization pipeline for natural-sounding copyRephrase is a new optional stage in the async localization pipeline. After the core localization step, an AI agent rewrites the output to read like native, idiomatic copy in the target locale – while keeping placeholders, variables, tags, and formatting exactly as-is.June 14, 2026
- W23 – Human-in-the-loop for in-house AI translation reviewHuman-in-the-loop review is now a pipeline stage your own team can run – in-house translators and language experts review, edit, and approve AI translations directly in the Lingo.dev dashboard, instead of an external translation provider.June 7, 2026
- W22 – The Lingo.dev GitHub App: continuous localization, straight from gitThe Lingo.dev GitHub App runs continuous localization on any repository, straight from git — install it, commit a config, and every push runs through your engine's async localization pipeline. AI Reviewers now run on every plan, with unlimited usage.May 31, 2026
- W21 – Audit logsAudit logs land in the dashboard. Glob patterns in i18n.json. Organization invites through the MCP server. Last-used timestamps on API keys.May 24, 2026
- W20 – API keys split: personal keys, or service keys with their own roleAPI keys split into Personal (inherit your role) and Service (own role, own engine scope). Sync localize returns model and cost per call. Engines gain an enable/disable toggle.May 17, 2026
- W19 – RBAC lands: roles, per-engine access, ownership transferRBAC ships – roles, per-user engine access, ownership transfer. Claude Desktop logs into the MCP server via browser OAuth. Async API gains lockedKeys; logs show retrieved context per request.May 10, 2026
- W18 – Credit balance auto top-upAuto top-up replenishes credits when your balance dips below a threshold. New Reports charts for instruction adherence and terminology coverage. Credit balance alerts and ISO 5060 classification in triage land alongside.May 3, 2026
- W17 – Pipeline: pre-edit, human review, AI review, back-translation as optional stagesThe localization pipeline wraps the core translate step with optional stages – pre-edit, human review, AI review, back-translation. Toggle them per engine or override per job.April 26, 2026
- W16 – Inspect every localization job, per language, end to endLocalization Jobs UI ships end-to-end – inspect job groups, per-language progress, payload, and webhooks.April 19, 2026
- W15 – Engine provisioning API: a fresh engine, auto-configuredThe provisioning API takes a fresh engine plus a few URLs or content samples and auto-configures brand voice, glossary, and instructions. Multi-step manual setup becomes one call.April 12, 2026
- W14 – Built-in glossary and instructions reviewsTwo built-in AI Reviewers check every glossary term and every instruction on every translation. Turn them on with a toggle instead of configuring a custom reviewer per criterion.April 5, 2026
- W13 – Triage Jira tickets with an agent that knows your glossaryJira triage workflow uses an agent that suggests glossary items, instructions, and model config tweaks. AI reviewers gain access to engine context. Translation logs gain review filters.March 29, 2026
- W12 – One POST, every locale: the async localization API shipsAsync localization API delivers any number of target locales via webhook. Glossary terms now bulk-import from CSV. Jira and GitHub integrations move to OAuth.March 22, 2026
- W11 – v1.0 is live: configure a localization engine once, call it from anywhereLingo.dev v1.0 introduces localization engines – stateful translation APIs configured once with models, brand voice, glossaries, and instructions, then called from code, MCP, or CI/CD.March 15, 2026