---
title: Roadmap
description: What's next for Langnostic, from project glossaries and local AI tools to a desktop translation workspace.
---

Here's what we're planning for Langnostic, in our current order of priority.
We'll update this page as the plans evolve.

## 1. Simpler project configuration

Configure your AI provider, model, locales, translation files, and plugins in a
plain configuration file. Set up common integrations without writing JavaScript
or TypeScript, while keeping advanced configuration available when you need it.

## 2. Project context and glossary

Give translations the background they need: what your product does, who it's for,
and how it should sound. Add instructions for your whole project or specific
parts of it.

Define preferred translations for important terms and keep brand names unchanged.
See which translations need revisiting when your glossary or instructions change.

## 3. Translate with local AI tools

Use your installed Claude Code, Codex, or Gemini CLI to translate through its
supported sign-in. Choose a local CLI or a direct API provider while keeping the
same project instructions, glossary, and translation files.

## 4. Standalone CLI

Install Langnostic directly on macOS, Linux, or Windows and translate without
setting up Node.js, npm, or JavaScript dependencies in your project. Continue using
the npm package if it already fits your workflow.

## 5. Desktop translation workspace

Open a project, select entries to translate, and compare proposed translations
with the original text. Review and edit results, manage your glossary, and update
project instructions in a desktop app.

Use the same project files in the desktop app and CLI, so you can review changes
visually and keep automated translation in your scripts and CI.

## 6. More frameworks and localization formats

Translate the localization files your framework already uses. Start with Rails
I18n, then expand to Django/Gettext and Swift/Apple string catalogs, with support
for their placeholders, plural forms, and translation context.

## 7. Installable plugins

Add support for more file formats and workflows by installing official or
community plugins. Build and publish your own integrations with documented plugin
development tools, and choose compatible versions for your project.

## Reliability across every workflow

Across these features, our priorities are consistent terminology, valid
localization files, predictable incremental updates, and preserving your edits.