Let your coding agent do the work.

Claude Code and similar coding agents can change everything a project needs. Every command runs from the shell, no editor window required.

Available with the Pro license

The command interface and the Pro toolkit are part of the Pro license: commands, check reports, screenshots, undo, F12, the test suite and working rules for coding agents, unlocked with a Pro license key. Pro also gives you the right to change and develop the engine itself, on our foundation, for your own games. Your agent may rebuild the engine however you want.

The engine itself uses no AI and is not tied to any AI. Without Pro, you use the engine by hand and receive updates from us.

Buy Pro

  • Every action is a command
  • Each answer carries a check report
  • Each answer carries a screenshot
  • Every change can be undone
  • F12 in every editor sends the current view to your agent

You do not need an agent to use Terra Engine. Every editor works by hand. The command interface is for people who want to script or automate.

terminal
# describe the change as a command list
$ cat mine.json
{ "version": 1,
  "befehle": [
    { "bereich": "dungeon", "befehl": "neuer_dungeon",
      "werte": { "name": "Old Mine",
                 "planet": "demo-planet",
                 "vorlage": "mine" } },
    { "bereich": "dungeon", "befehl": "neue_etage",
      "werte": { "name": "Level 1" } },
    { "bereich": "dungeon", "befehl": "speichere" } ],
  "bildschirmfoto": "shots/old-mine.png" }

# run it, no editor window needed
$ tools/werkstatt_befehle/befehle.sh mine.json
{ "ok": true, "exit": 0,
  "befehle": [ { "befehl": "neuer_dungeon", "ok": true },
              { "befehl": "neue_etage", "ok": true },
              { "befehl": "speichere", "ok": true } ],
  "pruefung": { "dungeon": {
      "fehler": [],
      "hinweise": ["floor Level 1 has no rooms yet"] } },
  "dateien": [ "content/dungeons/old_mine.json" ],
  "bildschirmfoto": "shots/old-mine.png" }

# changed your mind? go back to the state before the run
$ tools/werkstatt_befehle/befehle.sh rueckgaengig
{ "ok": true, "befehle": [ { "befehl": "rueckgaengig",
    "ok": true, "ergebnis": "1 Dateien zurückgesetzt." } ] }

How it works

  1. Describe the change as a JSON command list: area, command, values.
  2. Run it with one shell command. No editor window is needed.
  3. Read the answer: ok, a check report, a screenshot and the files that changed.
  4. Changed your mind? One command goes back to the state before the run.

What it covers

Every public method of an area's work layer becomes a command automatically. Registered areas: dungeon, quest, planet, sound (library, assignment, voices), languages, systems, abilities, main quest, chapter book, segments, notes and progression. A help command lists all commands.

Exit codes

0all commands good
1a bad command
2the check reports errors

F12 sends what you see

In every editor area, F12 sends the current view and state to your agent, so you can point at something and say fix this.

Your coding agent can work on the same Quest Helper plan file.

Example

A command file with new dungeon, new floor and save builds a small mine and writes a plan image. The terminal below shows a run with its result and the undo.

Start building your pixel RPG.

BuyTry free