|
Documentation
Book a DemoPlatform
PlatformMCPCLIAPIWorkflows
GuidesChangelog

Releases

What's new in Lingo.dev

New features, improvements, and fixes – shipped weekly.

2026

20 releases
  • Jul 26Week 30 · 2026

    W30 – Engine Suggestions learn from human edits

    Engine 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.

  • Jul 19Week 29 · 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.

  • Jul 12Week 28 · 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.

  • Jul 5Week 27 · 2026

    W27 – Async CLI file formats: TypeScript, YAML, PO, Flutter, Android, Xcode

    The 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.

  • Jun 28Week 26 · 2026

    W26 – New Lingo.dev CLI: `lingo push` runs your engine's full localization pipeline

    Introducing 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.

  • Jun 21Week 25 · 2026

    W25 – Localization Engine Suggestions: low AI-review scores propose the glossary, instruction, or brand-voice edit

    Localization 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.

  • Jun 14Week 24 · 2026

    W24 – Rephrase: a new stage in the localization pipeline for natural-sounding copy

    Rephrase 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.

  • Jun 7Week 23 · 2026

    W23 – Human-in-the-loop for in-house AI translation review

    Human-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.

  • May 31Week 22 · 2026

    W22 – The Lingo.dev GitHub App: continuous localization, straight from git

    The 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 24Week 21 · 2026

    W21 – Audit logs

    Audit logs land in the dashboard. Glob patterns in i18n.json. Organization invites through the MCP server. Last-used timestamps on API keys.

  • May 17Week 20 · 2026

    W20 – API keys split: personal keys, or service keys with their own role

    API 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 10Week 19 · 2026

    W19 – RBAC lands: roles, per-engine access, ownership transfer

    RBAC 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 3Week 18 · 2026

    W18 – Credit balance auto top-up

    Auto 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.

  • Apr 26Week 17 · 2026

    W17 – Pipeline: pre-edit, human review, AI review, back-translation as optional stages

    The 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.

  • Apr 19Week 16 · 2026

    W16 – Inspect every localization job, per language, end to end

    Localization Jobs UI ships end-to-end – inspect job groups, per-language progress, payload, and webhooks.

  • Apr 12Week 15 · 2026

    W15 – Engine provisioning API: a fresh engine, auto-configured

    The 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.

  • Apr 5Week 14 · 2026

    W14 – Built-in glossary and instructions reviews

    Two 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.

  • Mar 29Week 13 · 2026

    W13 – Triage Jira tickets with an agent that knows your glossary

    Jira 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.

  • Mar 22Week 12 · 2026

    W12 – One POST, every locale: the async localization API ships

    Async localization API delivers any number of target locales via webhook. Glossary terms now bulk-import from CSV. Jira and GitHub integrations move to OAuth.

  • Mar 15Week 11 · 2026

    W11 – v1.0 is live: configure a localization engine once, call it from anywhere

    Lingo.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.