General TranslationOverview
In gtx-cli 2.4.0, we've added a new way to save your local translation edits directly from the CLI. This means you can now make translation changes locally, persist them, and keep everything in sync with your project without touching the dashboard.
The save-local Command
Historically, the only way to make translation edits was through the dashboard editor. That worked, but it often broke flow, especially if you were mid-development and just wanted to tweak a translation inline.
The new save-local command lets you commit local translation edits back to your General Translation project. You stay in your workspace, and your changes stay in sync.
npx gtx-cli save-local
Running this command uploads any modified translation files, merges your local changes into the project, and ensures that the next translate run reflects your edits.
Translate (Now With Local Awareness)
Until now, translate would always assume the remote version of a translation was the source of truth. If you made local changes and ran translate again, those edits would be overwritten. That's no longer the case.
npx gtx-cli translate
The CLI automatically checks for local edits and saves them in the background — the same way save-local does — before re-downloading translations. This guarantees that your local versions are preserved and that re-translations always persist your edits.
What Happens When Sources Change
You might wonder: what if I edit the source file after making local translation edits? In earlier versions, that would have triggered a full retranslation that wiped your custom changes.
In 2.4.0, the CLI is smarter. Even when a source update causes a retranslation, your previous local edits persist. They are incorporated into the new translation automatically.