General Translation
Connect a repo —your app is translated.
Locadex connects to your codebase, internationalizes your code, and opens pull requests with translations. Auto-merge is off by default — every change waits for your review.
Push, scan, edit, translate, open PR.
The whole loop runs without you. One run of the agent, shown as its artifacts — what it found, what it decided, what it changed, and the pull request where it stops to wait for you.
locadex · run #1184 — explodedpush e4f21c9 → PR #218Scan codebase
A commit or pull request triggers the workflow, and the agent maps out what has changed. “Changed files only” is on by default — siblings outside the target directory are never touched.
Context, inferred per line
Scan is not grep. The agent reasons about your component structure and writes down what a translator would need — tone, variables, holds, and the terms that never translate.
founddecisionapp/page.tsx · L4<h1>Hello, world!</h1>wrap in <T>app/checkout.tsx · L18'Payment received'string — gt()components/Nav.tsx · L7{user.name}never translated — <Var>app/page.tsx · L16new Date()formats locally — <DateTime>components/Tagline.tsx · L2tagline copytone noted — $contextlegal/terms.mdxTerms of Serviceheld — $requiresReviewEdit code
JSX wraps in <T>, bare strings become gt() calls — in your conventions, through your linter. Local edits are preserved, so a re-run never overwrites your hand-tuned copy.
@@ −4,4 +4,6 @@ export default function Home()return (−<h1>Hello, world!</h1>−<p>Welcome back, {user.name}</p>+<T>+<h1>Hello, world!</h1>+<p>Welcome back, <Var>{user.name}</Var></p>+</T>)}
Guarded by default
An agent that edits code earns trust by stopping at the review gate. Every Locadex run ends at a pull request, not a deploy.
- Changes arrive on a prefixed
locadex/branch — never onmain - Auto-merge is off by default — opt in to merge-when-checks-pass, or keep the button yours
- Setup is a separate PR that you merge yourself first
Preserve local editsandChanged files onlyship on- Your build commands and linter run in a sandboxed VM, with org secrets injected as env vars
Open PR
Pull request created for review — the struck lines are your bare JSX, the added lines the same JSX wrapped in <T>. The merge stays yours.
locadex[bot]wants to mergelocadex/generate-codemain· 5 files changed · +38 −6Locadex never merges its own pull request. Auto-merge stays off unless you turn it on — the run ends here, at your gate.
Standing automation, not a setup script.
Three templates, each with its own trigger, re-running as your code changes. Point one at a directory, give it your commands, and it works the way your repo does.
Generate code
Wraps your source with t() and the <T> component, and opens the pull request.
Generate translations and push
Creates translations in context and pushes them to your branch.
Keep locales in sync
Keeps every locale current with the source as it changes.
Zero engineering bandwidth.
Connect a GitHub repo and your app is translated — in native speed and quality, with your review in the loop.
Metered, capped
Runs are billed at $5 per Locadex Compute Unit — files touched, lines changed, resources end to end. A usage limit is a hard cap.
Review stays yours
Every run ends at a pull request on a locadex/ branch. Auto-merge is off until you turn it on.
Standing automation
Three templates re-run as your code changes — on push, on PR, or started manually.
Your commands, sandboxed
Pre- and post-process commands and your linter run in a sandboxed VM, with your org’s secrets as env vars.