Everything your team needs to start translating your app strings with Forthwith.

A typical Forthwith rollout has four steps: choose the billing model that fits your translation volume, add a payment method for the organization, invite teammates with the right roles, and run the CLI against your project.

Forthwith supports pay-as-you-go and subscription billing. The Billing page shows your current plan, usage in the active billing period, a default payment method, recent invoices, and whether cancellation is pending.

Invitations are managed from the Organization page. Invite a teammate by email, choose one or more roles, and send the invitation. Pending invitations stay visible until they are accepted, expire after 7 days, or are deleted.

Forthwith supports three organization roles, and a member can hold more than one at the same time. Roles control billing access, workspace administration, and day-to-day project work.

The primary owner has a small set of responsibilities that ordinary owners do not: transferring primary ownership, closing the organization, and handling situations where the current owner needs to leave the workspace.

The CLI is the main integration point for repositories. It discovers strings, shows the expected translation work, and writes localized files back into your project.

Open the Terminal and enter commands below:

brew install Forthwith-LLC/forthwith/forthwith

Choose the installer that matches your machine to get the exact command for your environment.

Supported frameworks currently include Android, iOS, React, React Native, Flutter, Phoenix, and go-i18n.

Update the CLI with the same package manager or install path you used during installation.

brew update
brew upgrade forthwith

Use the matching update path so package manager metadata and installed binaries stay aligned.

If you need to remove the CLI, choose the same platform and package manager or script path you used during installation.

brew uninstall forthwith
brew untap Forthwith-LLC/forthwith

Use the matching uninstall path so package manager metadata and shell-installed files are removed correctly.

forthwith login
forthwith init
forthwith translate
forthwith status
forthwith whoami

That sequence gets you authenticated, creates a project config, runs a translation pass, and lets you confirm coverage and account context.

• Use the forthwith login command to authenticate the default profile from the CLI in your browser. To use a specific profile name, add the --profile flag. Recommended
• To use token-based login, first generate an API token at API access , then use the ( --use-token or --token ) flag to specify the token.
• FORTHWITH_AUTH_TOKEN overrides stored credentials for commands that need authentication, and should really only be used for CI/CD.
• List profiles with forthwith profile list , and set the profile you want to use with forthwith profile use .
• forthwith logout revokes token(s) server-side and removes local credentials.
• forthwith logout --all revokes all saved profile tokens, then removes all local credentials.

Create config with forthwith init , then edit it with forthwith config .

version: 1
framework: android
source_language: en
target_languages:
  - es
  - fr
source_paths:
  - app/src/main/res/values/strings.xml
do_not_translate:
  - Forthwith
tone: neutral
politeness: neutral
domain: general
audience: general

Editor selection order for forthwith config is VISUAL , then EDITOR , then the platform fallback ( vim , vi , or notepad.exe on Windows).

• forthwith translate processes new, changed, and missing target translations by default.
• Plural output follows the target framework, not just the source file's shape. For CLDR-native formats such as iOS .stringsdict , Forthwith may expand English one/other into target categories such as Spanish or Italian one/many/other . For Phoenix/gettext targets, it writes only the forms the msgstr[N] slots can persist, such as one/other for Spanish or Italian.
• --all forces a full re-translation.
• --target accepts one language or a comma-separated list from target_languages .
• --file limits the run to one configured source path.
• --dry-run previews work without writing files.
• --yes skips confirmation prompts, and --force skips the git safety prompt.
• Exit codes are 0 for success, 1 for error, and 2 for cancellation.

• forthwith status summarizes per-language translation coverage and supports --json output.
• forthwith whoami shows the authenticated email, organization, and plan info, with optional --json output.
• forthwith completion <shell> generates shell completions for bash , zsh , fish , and powershell

export FORTHWITH_AUTH_TOKEN=<token>
forthwith translate --yes --force

A common CI flow is to run translation with a token, then open a pull request only when localized files changed.