Developer Tools · Built-in

CLI

Setup

Get CLI running

Three steps, no migration. Point it at your project and the first keys land in the dashboard.

InstallAdd the package or the config block. Nothing else in your build changes.
Connect your projectUse the org/project identifier from your dashboard. Keys and languages come from there, not from a local file you have to keep in sync.
ShipPublish once and every locale is a static file on the edge. Copy changes go live without a new deploy.

What it looks like in your code

terminal

# Compare local keys with the platform, then create the missing ones
npx @better-i18n/cli sync --push --yes

# Fail a build when i18n health drops below the threshold
npx @better-i18n/cli doctor --ci --report

Install integration

Surface

What CLI gives you

The exact commands, tools and paths you get. Names are what you type, not marketing labels.

better-i18n scan

Walk your source files and report every user-facing string that is not wrapped in t().

better-i18n sync --push

Compare local keys against the platform and create the missing ones.

better-i18n check:missing · check:unused

List keys used in code but missing remotely, and keys published but no longer referenced.

better-i18n doctor --ci

Score i18n health and fail the build below your threshold.

better-i18n keys list · create · delete

List, create and delete keys from a script or a pipe, without opening the dashboard.

better-i18n publish

Push approved translations to the CDN from your terminal.

Where it fits

How CLI works inside Better

Detect

Pull source strings from your codebase or connect your CLI repository. Keys arrive in Better with structure and context intact.

Review

Run AI translation, assign human reviewers, and gate approval before any change reaches production. Everything auditable in one place.

Ship

Publish to the CDN edge or push translations back to CLI. Copy changes go live without triggering a new app deploy.

Developer-first workflow

Localization lives close to your code — reviewable in pull requests, version-controlled, and part of your existing CI and deploy pipeline.

Less operational drift

Centralize translation updates, review sign-off, and delivery in one workflow instead of spreading work across separate tools and scripts.

Controlled rollout

Decouple translation publishing from code releases. Ship copy changes on your schedule without waiting for the next deploy window.

Questions

Before you connect it

Connect CLI today

Free to start. Add the integration, publish once, and see the copy change without a release.

Install integration Read the guide

CLI