We just shipped the Inbox.

The Inbox is one place for localization work that needs a human.

The new Lingo.dev is here, and it is live for every organization.

Lingo.dev is completely redesigned around the way you work, so everything now has a clear place, across five areas:

• Home  your starting point: a quick read on recent activity.

• Infrastructure  where you build your localization engines: the models, glossaries, rulesets, and brand voices you configure once and reuse everywhere.

• Studio  where localization connects to the tools you already use: the GitHub App, a Zendesk Help Center, a Payload CMS, plus the CLI and the API.

• Queue  one inbox for everything that needs a person: human review, localization engine suggestions, and triage, in a single list you filter and save as views.

• Observability  where you see whether the output is good, even in languages you cannot read: reports, AI reviewers, and a log of every review beside the translation it scored.

This is the foundation for everything we build next, and the new home for your localization work.

You can now retranslate specific pieces of your content, down to a single key.

The Lingo.dev CLI command lingo push retranslates only the source text you edited. But some changes happen in your localization engine, not your files: you switch the model, add glossary terms, or edit your rules. Your source stays identical, so lingo push finds nothing to redo. Now you can retranslate the exact pieces you want, from a single key to a whole language.

Run lingo push messages/en.json --key auth.login and Lingo.dev retranslates only the keys you list. A key is its path in the file, so you can pick one value, a whole subtree, or several keys at once. Everything else stays the same. If you are not sure which keys to list, your AI coding assistant can read the file and write the command for you.

If a change affects more than a few strings, retranslate whole files. Run lingo push src/en/**/*.json --force and Lingo.dev retranslates every string in the files you list. And if one language needs redoing, run lingo purge --locale fr to delete the French files, then lingo push --backfill-missing to translate them again. Your other languages stay the same.

You can now translate your Payload CMS content from Lingo.dev.

The Payload CMS integration connects your Payload instance to a localization engine you host on Lingo.dev. Choose the collections and globals to cover, and Lingo.dev translates their localized fields into your target languages, then writes each translation back to Payload under that locale. Rich text translates as a Lexical tree, so formatting, links, uploads, and block structure survive the round trip and only the text inside is replaced.

Setup is one plugin. Install lingo.dev/payloadcms, add it to your Payload config, and redeploy. Scope, locales, and engine live in the dashboard, so you can change them without touching your config again.

You can now translate your Zendesk Help Center from Lingo.dev.

The Zendesk Help Center integration connects your Help Center to a localization engine you host on Lingo.dev. Choose the categories, sections, and articles to cover, and Lingo.dev translates their titles, descriptions, and bodies into your target languages, then writes each translation back to Zendesk. Article bodies translate as HTML, so links, formatting, and embedded media survive the round trip.

There are two ways to keep your Help Center translations up to date. The first, Sync, translates only the articles you have added or edited since the last run. The second, Retranslate, rebuilds every article in scope from scratch, which is what you want after changing the localization engine's glossary, brand voice, or rules and needing your existing translations regenerated against the new configuration.

Human review can run on only the translations that need it.

Human review is a stage in the localization pipeline: a translation pauses so a person checks it before it ships. Until now, turning it on sent every string to a reviewer. Now it is selective. Set a quality threshold on the engine, and only translations that score below it are routed to a human. Everything at or above the threshold ships automatically. Reviewers spend their time on the translations most likely to need a fix, review cost drops, and high-confidence output no longer waits in a queue.

Full changelog: lingo.dev/changelog

Seed a whole glossary from the MCP server, across every locale at once.

Adding glossary terms through the MCP server no longer goes one term at a time. Ask your AI assistant to add a whole set of terms in a single step, spanning as many locales as you need, and it seeds the glossary in one pass. Building out a large termbase used to be slow, adding each term on its own call. Now it lands in one go, and the terms start steering translations right away.

Also shipped

• Docusaurus output paths in the CLI. Translated pages now land in the folder layout Docusaurus expects, so the localized site renders without moving files by hand.

• Fuller YAML frontmatter translation. Nested and list frontmatter fields, like SEO or FAQ metadata, are now translated too, not just simple top-level ones.

Localization Engine Suggestions now come from the corrections human reviewers make, not only from low AI-review scores.

When a reviewer edits a translation whether in-house or through an external provider the localization engine compares the change against what it first produced. When the same fix recurs across jobs, or a correction clearly sets a term, it proposes the glossary, instruction, or brand-voice edit behind it. Apply writes the change into the engine, and the next translation runs with the fix in place.

Suggestions can now be approved or dismissed in bulk select a set and act on all of them at once, instead of one card at a time.

Full changelog: lingo.dev/changelog

Glossaries, rulesets, and brand voices now live at the organization level and attach to any engine.

Build a glossary, a ruleset of linguistic rules, or a brand voice once, then attach it to any engine that needs it. Edit a shared asset and every engine it's attached to picks up the change. A new engine no longer starts from an empty configuration: attach what you already have and it inherits it.

Also this week:

• Take over a translation waiting on external review. When a job is parked on an external professional reviewer, an authorized member of your own team can open the pending review in the dashboard and submit the decision, so the job continues instead of waiting on the external round trip.

• A runnable example repo for every framework. Each is a real project with .lingo/config.json and translations committed clone it, run lingo link, and push: iOS, Android, Flutter, React + Vite, Next.js, Rails, Laravel, Markdown, Markdoc, OpenAPI, and TypeScript modules.