# What the Terminal does with a script

> Compile, describe, run, report, versions, deploy.

Source: https://algobarsx.com/docs/terminal-tools/

| The Terminal | What it does |
| --- | --- |
| Compiles as you work | Names, types, units, price levels against distances, R, where things may go, and imports are all checked before anything runs. |
| Description | The script in plain English, generated from the compiled code. |
| Convert to AlgoBarsX | Type what you want in plain English. When the editor holds a description and not code, this button appears and writes the script. |
| Run | A strategy is backtested, reported and charted. An indicator is run and charted. An alert is checked against its own settings. Before a backtest you confirm the market, bars, bar type, how far back to test (1 week to 1 year), the lot size and the starting balance. |
| Replay | Plays a finished backtest back. Trades appear as they open and settle as they close, and the balance moves with them. If the account ran out, the replay stops where the test stopped. |
| Report | How it went, what it cost, how the trades behaved, then breakdowns by rule, exit, confirmation, side, tag and month. |
| Versions | Every run is kept with the code that produced it. Restore any earlier build. |
| Reference and autocomplete | Every built-in is documented in the editor and offered as you type, from the same registry this page is built from. |
| Import, save and seal | Bring in a script from another language or an .abx file, and save your own as an open or sealed file. |
| Deploy | Run a strategy on a demo or live account, or switch an alert on. You choose the market, the bar size, the trade size and the balance to trade, so one script can run on more than one market. Editing a live script explains what the change would do before it is made. |
| Strategies list | Strategies written in AlgoBarsX appear with your other strategies, where each one can be deployed, opened or deleted. |
| Import from a file | The import menu takes files as well as pasted code: `.pine`, `.mq4`, `.mq5`, `.cs`, `.els`, `.py` and plain text. |

The engine promises five things: no look-ahead, the same answer every time, indicators that always update, higher bar sizes that only appear once their candle has closed, and no hidden costs in the numbers. The language's own test suite has 678 tests, and all of them must pass on every build.