Translations belong in your repo. Not in a browser tab
Keep your i18n JSON files in lockstep with LangSync. Push what you edit, fill the rest with AI, write the result back. One command per repo.
Your i18n files stay the source of truth
Most tools force you out of your editor: copy a string, switch tabs, paste, translate, copy back. The CLI turns that around. Your JSON files stay where your team and tools already work: git, your editor, code review.
- Edit in your editor, sync with one command
- Stable key ordering, atomic writes, clean diffs
- Each dev syncs their own edits without overwriting anyone's
One init. Same setup for every dev
A short wizard writes .langsync.json at your project root: organization, namespace, directory, source language. Commit it. Teammates clone the repo and run the CLI with the same organization and namespaces, no coordination needed.
- Project pinned to org and namespace in JSON
- Multi-org devs never hit the wrong project
- CI runs the same commands as your laptop
You write Czech. The AI translates from Czech
Most tools assume English first. The CLI doesn't. Set your source language to whatever you think in, and the AI translates from that file into every other language, including the team default.
- Source-of-truth file is your choice, per project
- Human translations in other languages stay intact
- Each dev can pick their own source independently
The eight commands you'll use most
nrc login
Browser sign-in. The session lives in your OS keyring, one per profile.
nrc langsync init
Five-step wizard that writes .langsync.json. Organization, namespace, directory, source language, seed mode.
nrc langsync sync
Push every local language file, fill gaps with AI, write the result back. The everyday command.
nrc langsync pull
Read-only refresh: writes what the team translated in the web app to your local files.
nrc langsync mark add
Add one term without opening the dashboard. Optional auto-translate.
nrc langsync namespace create
A new namespace from the terminal: name, default language, optional context.
nrc org create
Bring up a new Norcube organization without leaving the CLI.
nrc upgrade
Self-update to the latest release. No package manager needed.
Built to be boring in production
The CLI is a thin client. The real work happens server-side as a durable, resumable job.
Server-side jobs, not client orchestration
Sync runs on our servers, not your laptop. If a backend restarts, the next worker picks up where the last one stopped.
Cost gate on AI translation
A resumed job never re-translates a cell that's already filled, so a restart doesn't cost you twice.
Honest progress UI
Multi-namespace parallel sync with a live dashboard. When something fails, the Issues block tells you which mark in which language and what to do about it.
Install. Sync. Ship
One curl command on macOS and Linux, or a zip download on Windows. The install script adds itself to your PATH and creates the nrc short alias. Time to first sync: under a minute.
- macOS · Linux · Windows
- Single binary
- OS keyring auth
- Self-updating