Set up with an AI agent

Let the coding agent you use in your repository install Linguana and connect your build. You can then choose languages, edit translations, and publish from the dashboard.

1. Gather the project details

1. Sign in to the dashboard and create a project, or ask an owner or admin to create it.
2. Copy the project ID, API URL, and browser publishable key from Integrations. Its templates name the browser values VITE_LINGUANA_API and VITE_LINGUANA_KEY; your agent may use the longer names in the docs, provided the stored values and runtime reads agree.
3. Ask an owner or admin to create a development token in Tokens. Store it in an ignored local environment file or CI secret as LINGUANA_PROJECT_TOKEN.
4. Choose a first target language in Languages, such as French (fr).

You can start with local extraction before you have an account. Leave hosted credentials unset until the local build works. The dashboard creates projects with English (en) as the source language; tell your agent if your app uses another source language so it can check the project configuration first.

2. Paste this prompt into your coding agent

Replace the bracketed values. Give the agent the secret's location, rather than including its value in the prompt.

Set up Linguana in this repository using the existing app framework.
Read the Linguana docs at [DOCS_ORIGIN]/llms.txt and the relevant pages.

Project ID: [PROJECT_ID]
API URL: [API_URL]
Browser publishable key: [PUBLISHABLE_KEY]
Source language: en
First target language: fr
Build environment: development
The project token is stored in [IGNORED_ENV_FILE_OR_CI_SECRET] as
LINGUANA_PROJECT_TOKEN. Do not print it or include it in browser code.

Inspect package.json, vite.config, the application root, and SSR setup.
Install the matching public @linguanahq runtime, @linguanahq/catalog,
and @linguanahq/vite. Use the documented adapter before the framework
plugin. Preserve existing framework, routing, and deployment plugins.
The 0.1.0 SDK ships TypeScript source; use --configLoader runner for Vite.
For SSR, follow the framework guide and share the server hydration state.

First use upload: false. Keep static user-facing text as written.
Use the documented explicit-message API for variables and rich text.
Build and inspect .linguana/manifest.json; confirm source fallback works.
Then configure upload using the project ID and development token.
Keep unprefixed secrets in build config; only browser-safe values may
use VITE_. Do not start paid translation or publish a release yet.

Report changed files, the manifest result, and remaining dashboard steps.
Explain which environment the runtime reads and how to switch it after
publishing. Do not claim a language is live because it is accepted or ready.

Use the origin of the docs you are reading for [DOCS_ORIGIN]. In a local checkout, that is normally http://localhost:3004.

3. Give the agent documentation access

The docs expose llms.txt for an index and llms-full.txt for the full text. If your agent supports remote HTTP MCP, configure the docs origin plus /mcp as its documentation server. /api/docs/mcp is also supported.

This MCP server supplies documentation context. It does not grant dashboard access, create tokens, approve spending, or publish releases. Use your agent's own connection settings; the setup prompt also works when it reads the documentation directly.

4. Confirm the handoff, then use the dashboard

Ask the agent to show where your app's visible text appears in the manifest and confirm the upload appears in Jobs. Then:

1. In Languages, enable the first target language.
2. In Jobs, choose Translate latest build and review the maximum charge before starting.
3. Use the strings editor or Review to inspect and correct the wording.
4. Before production publication, have the agent upload a production build using a separate production token. Prepare and review its target catalog, then follow Publish a language. Set the runtime to production too. A development catalog must not be assumed compatible with production delivery.

For a development preview, ask the agent to follow CI/CD after you approve the run's spending limit; the optional plugin workflow publishes only to development.

Your role controls which actions you can take. Viewers can inspect; editors, admins, and owners can edit, review, and publish.