Skip to content

Docs

How agent setup works

The document chain an AI coding agent follows to set up Rodarion, what each part owns, and what the agent will and will not do.

View as markdown · for agents and copy-paste

Rodarion is built so that a coding agent can do the whole setup. You paste one prompt; the agent reads a short chain of markdown documents and does the rest.

The chain

StepDocumentOwns
1The prompt on /startPoints the agent to the entry document
2https://www.rodarion.com/llms/start.mdThe goal, order of work, rules and the hand-off to you
3https://app.rodarion.com/llms/trial.mdCreating a trial without credentials, installing and configuring the CLI
4AGENTS.md, written by rodarion initAnalysing your repo, choosing the export profile, importing, verifying

Each document covers only its part, so they never contradict each other. The site index for agents is /llms.txt, following the llms.txt convention.

What the agent does

  1. Reads your language files and decides the source and target languages.
  2. Creates a trial with one API call. No account, e-mail or card.
  3. Installs the CLI and writes rodarion.json, AGENTS.md and a gitignored .env.
  4. Detects the file format and layout and sets up an export profile.
  5. Imports your keys and existing translations, then downloads them again and checks the git diff to prove the round trip is lossless.
  6. Asks you for your e-mail address, name and company, and claims the trial so it becomes your free account.
  7. Gives you a login link and a summary of what changed.

What the agent does not do

  • It does not commit. Every change is a working-tree diff for you to review.
  • It does not store your token in a tracked file.
  • It does not overwrite approved translations.
  • It does not need your e-mail address until the very end, and the trial is deleted automatically if you never give it.

Already have an account?

Create an API token in the app and use the second prompt on /start. The agent skips the trial and goes straight to the import.