Skip to content
ReRune

Localization CLI for releases that cannot wait on spreadsheets.

The ReRune CLI helps developers create project config, pull approved dashboard translations into the app, and push local translation updates back to ReRune.
Start localizingSee workflow
ReRune projects list showing real localization projects in a workspace
ReRune dashboard showing localization workspace activity and project statusReRune dashboard showing localization workspace activity and project statusReRune dashboard showing localization workspace activity and project status
ReRune OTA demo mobile app landing screen with live localization status

Common challenge

Developers need localization to move through repeatable terminal commands instead of manual file downloads and uploads.

Best fit

Teams that already script builds, tests, and releases and want translation sync to follow the same operational pattern.

How ReRune helps

ReRune combines CLI automation with a shared workspace so command-line sync still has product context, team review, and language progress behind it.

Workflow

From app copy to release-ready localization.

ReRune connects translation management to the delivery path developers already use: dashboard work, AI assistance, CLI/API sync, and OTA updates where a supported SDK is installed.

Authenticate once

Generate API keys in the dashboard and use them in local scripts, CI/CD jobs, release tasks, or integration services.

Automate sync

Run ReRune once to create project config, then use rerune --pull and rerune --push as part of the engineering workflow instead of waiting on manual file handoffs.

Validate before release

Keep placeholders, structured values, missing languages, and review status visible before translated copy reaches production.

Release with options

Ship translations as files, API-driven sync, or OTA updates depending on the platform and how the product is deployed.

Setup WizardAI Coding Agent

One command. A wizard sets the stage, your AI agent ships it.

Run the onboarding command from the root of your Git repository. The wizard inspects the app and confirms the plan with you, with no AI involved and nothing changed yet. Then it opens the coding agent you already use with a complete migration workflow.

Run inside your Git repository

curl -fsSL https://rerune.io/onboard.sh | sh

View current scriptView v1.2.11Changelog

The script runs locally. ReRune does not receive your source code or list of installed agents.

Coding agent integrations

11 integrations: 4 available now, 7 planned.

  • Claude CodeReady
  • CodexReady
  • OpenCodeReady
  • PiReady
  • GitHub Copilot CLIPlanned
  • GoosePlanned
  • Qwen CodePlanned
  • Cursor AgentPlanned
  • Kiro CLIPlanned
  • Cline CLIPlanned
  • Factory DroidPlanned

Coverage

App-first does not mean mobile-only.

Start where localization creates release friction, then keep web, mobile, and cross-platform products in one shared workspace as your surface area grows.

Developer delivery

Sync through the CLI. Publish through OTA SDKs.

Use the ReRune CLI locally or in CI/CD to manage project translations, then deliver approved runtime updates through the SDK built for your app.

SDK directory

Use the current public SDK for each product surface.

Public ReRune SDKs for Flutter, Android, iOS, Kotlin Multiplatform, React, React Native, and Angular support runtime variant selection with Main and bundled fallback.

rerune on pub.devReRune Android on Maven CentralReRune iOS on Swift Package IndexReRune Kotlin Multiplatform on Maven Central@rerune/react on npm@rerune/react-native on npm@rerune/angular on npmngx-translate example appTransloco example app
Flutter        rerune ^1.9.1
Android        rerune-android-compose:1.8.0
               rerune-android-views:1.8.0
iOS            ReRune 1.7.0
KMP            rerune-kmp-compose:1.0.0
React          @rerune/react@1.9.0
React Native   @rerune/react-native@1.9.0
Angular        @rerune/angular@1.9.0

Companion CLI: Install the ReRune CLI

Use the ReRune CLI to sync, validate, and manage translations right from your terminal. Run syncs in CI/CD or locally whenever you need to push a new language.

  • Downloadable builds for macOS, Linux, and Windows
  • Uses the API keys you generate in the dashboard
  • Fits scripted CI/CD workflows through CLI and API access

Need help? Invite your teammates directly from the CLI or jump back into the web dashboard.

Homebrew (macOS/Linux):

brew install BasalBit/tap/rerune

Already installed? Update anytime with brew upgrade BasalBit/tap/rerune.

Direct download:

Choose the architecture that matches your machine.

Download macOS (amd64)Download macOS (arm64)
After install, run rerune at the root of the project to start using the CLI.

Need archived binaries or older versions? Browse the release catalog.

Install or update with one command

Installs the latest reviewed ReRune CLI for your user account. No sudo or administrator privileges required.

curl -fsSL https://rerune.io/install.sh | sh

Questions

Questions teams ask before choosing a localization platform.

Contact the ReRune team

Share an idea, report a problem, or ask for help with ReRune.

Can ReRune CLI run in CI/CD?

Yes. The CLI is designed for scripted workflows, so teams can use it locally or from CI/CD jobs where API credentials and project context are available.

Does CLI sync replace the dashboard?

No. The dashboard remains the shared place for teams to manage keys, languages, glossaries, context, and review status. The CLI moves approved localization work through developer workflows.

Can one workspace cover web, mobile, and cross-platform apps?

Yes. ReRune is structured around projects, languages, keys, glossaries, metadata, CLI/API sync, and SDK delivery paths so teams can manage several product surfaces from one localization workspace.

Explore next

Keep exploring the localization workflow.

Go deeper into the developer, platform, and delivery workflows connected to this page.

Localization API for teams that automate product text.

Automate ReRune with an API key: the CLI in CI, the hosted MCP server for coding agents, and server-side scripts. Apps use a read-only OTA Publish ID.

Continuous localization for teams that ship every week.

Use ReRune for continuous localization with CLI/API sync, AI-assisted translation, review context, and release-ready updates for web and app teams.

Developer localization platform for product teams that ship fast.

Keep localization in your engineering workflow with ReRune: CLI sync for releases, API keys for automation, and SDKs for runtime text updates in your apps.

One workspace

Start with one product workflow and expand from there.

Create projects, manage keys, use AI assistance with context, sync through CLI/API, and publish approved runtime updates when your app uses a supported ReRune SDK.
Start localizingPricing