CLI Configuration

There is no config file. Everything is a flag or an environment variable, which keeps the CLI reproducible in CI.

Environment variables

Variable	Used when	Description
`ANTHROPIC_API_KEY`	default provider	Your Anthropic key
`OPENAI_API_KEY`	`-p openai`	Your OpenAI key

The idiomatic way to lock in options for a project is an npm script:

{
  "scripts": {
    "i18n": "shipi18n translate locales/en.json -t es,fr,de,ja --incremental"
  }
}

Now npm run i18n means the same thing on every machine and in CI, and the options are reviewed like any other change.

{
  "scripts": {
    "i18n": "shipi18n translate locales/en.json -t es,fr --incremental",
    "build": "npm run i18n && vite build"
  }
}

For CI, the GitHub Action is usually a better fit — it can commit the result or open a pull request for review.