globalize.now is now a published plugin in ChatGPT. globalize.now is AI-powered localization infrastructure for React, Next.js and Vue apps, and the plugin lets you manage your globalize.now projects from a ChatGPT chat or from Codex. You can ask which languages each project ships in and add new target languages without opening a dashboard.

What is the globalize.now ChatGPT plugin?

It is the globalize.now listing in OpenAI's plugin directory, published by globalize.now SIA under Developer Tools. ChatGPT and Codex share that directory, so one listing covers both. A plugin can bundle apps, skills and templates. Ours bundles one app: the globalize.now connection to your projects.

The plugin works on the layer we own. globalize.now produces the keys and the locale files. It is not an i18n runtime library like next-intl or i18next, and it is not a translator workflow tool. The plugin gives ChatGPT a way to read and change your globalize.now projects, nothing more.

How do I install it?

Open Plugins in the ChatGPT sidebar, search for globalize, and open the listing. Connect your globalize.now account from there. If you do not have one yet, connect your repository first: that is the step where your codebase gets converted and your project gets created. The get-started guide walks through it.

Once the plugin is connected, ChatGPT can use it whenever a request is about your localization projects. You can also call it directly by typing @globalize.now in the composer, which is what the starter prompts on the listing do.

What can I ask it?

Here are two requests we ran in ChatGPT on 14 November 2026, on our own account.

"Show my globalize.now projects and their target languages." ChatGPT called the plugin and answered with a summary and a table: the number of projects, the target language configurations across them, the unique target locales, and one row per project listing each language by name and locale code. On our account that came back as 5 projects, 28 target language configurations and 14 unique locales, with our website project at 10 languages.

"Add German and Japanese to my storefront project." ChatGPT matched "storefront" to our demo project, Brewline Storefront, added German (de) and Japanese (ja) as target languages, and confirmed both in a table. We checked the project in globalize.now afterwards: both languages were there next to the existing French.

Adding a language configures it. It does not start a translation job by itself, and ChatGPT said so in its reply: no job had started, so no translation credits were used.

Why manage localization from a chat at all?

Because the question "which languages does this app ship in, and what is missing?" usually comes up in the middle of other work. If you are already in ChatGPT or Codex planning a launch in a new market, the answer is one message away instead of a tab switch and a settings page.

It also makes the state of your localization readable for people who never open the app. A founder planning a Japanese launch can ask ChatGPT whether Japanese is configured for the product, and get the real answer from the project, not a guess from the model.

The same holds in Codex. If you build with an agent, the agent can check and change the project's languages as part of the task it is already running.

What does the plugin not do?

It does not convert your code. Turning hardcoded strings into i18n keys happens once, in the globalize.now app or through the agent skills, when you connect the repository. The listing says it plainly: the plugin handles everything after that.

It does not move your translations into ChatGPT. Translations live in your repository as locale files, and your app keeps loading them through whatever i18n library you already use. There is no runtime widget and nothing new in your bundle.

It does not replace a translation engine or your i18n runtime. Those layers stay where they are. globalize.now sits between your code and them, producing and maintaining the keys and the locale files.

How does this fit with the rest of globalize.now?

The flow is the same one you would run in the app:

  1. Connect your repository. globalize.now converts the codebase once and creates the catalog.
  2. Pick your target languages. You can now do this from ChatGPT too.
  3. Translate new strings. When new strings land in the catalog, translation jobs translate the new units, and the finished translations come back to your GitHub repository.

The plugin adds a second front end to step 2 and to checking the state of your projects. The developers page covers the full flow, and the vibe coder guide covers the same path for people building with AI tools who would rather not touch config files. If you work in Claude, the connector in Claude's directory gives you the same projects from there.

Which apps does it work with?

The listing names React, Next.js and Vue apps, which matches what globalize.now converts today. If your app was built with Lovable, Cursor, Claude Code or Codex itself, the path is the same: connect the repository, let globalize.now convert it, then manage languages from wherever you work. The Lovable path has its own page in our Lovable integration.

Try it

Search for globalize in ChatGPT's Plugins, connect your account, and ask which languages your app ships in. If you have not connected a repository yet, start in the app.

globalize.now turns hardcoded app copy into translation-ready locale files and keeps them updated as you ship.

Try globalize.now free