Skip to main content
New release Β· v8.4.0

RTILA X 8.4.0 is here

Every feature reviewed and refactored, plus a long list of fixes. Here is what you get:

  • AI that works without your own key AI Self-Correction and AI Completion now run on shared RTILA AI, in desktop, scheduled, remote and bot runs.

  • Cloud and Remote mode run your projects Projects and trigger chains now execute in Cloud and Remote mode. Stopped runs keep their checkpoint and can be resumed.

  • Proxies with a login, in any Chromium browser Authenticated proxies now work everywhere, including Google Chrome, and side requests follow the run’s proxy.

  • Redesigned Visual Builder The side panel opens by itself, fits any width and gives empty projects a clear first step.

Free forever plan Β· No account needed Β· Already using RTILA X? Check the β€œBehaviour changes” section in the notes before updating.

Roll Back When a Change Goes Wrong

RTILA X stores project revisions so you can restore an earlier version of any workflow.

The Risk of Experimentation

Automation building is iterative. You adjust selectors, rearrange commands, and try different timing strategies. Most changes improve the workflow, but some introduce subtle breakage that only appears under production conditions. Without version history, reverting a bad change means rebuilding lost steps or guessing what the previous state looked like.

Version history removes that risk. RTILA X saves revisions as the project changes, and you can restore an earlier version when necessary. This creates a safety net that encourages bolder experimentation and faster iteration.

What Gets Tracked

Revisions include the project’s command structure, settings, variables, and related configuration. The exact scope depends on the project type, but the goal is always to restore a usable state. If a selector change broke extraction or a scheduling tweak caused a missed run, you can go back to the last working revision.

Version history also helps with client work. When a client reports a regression, you can compare recent versions to identify what changed before the issue appeared. This makes support diagnosis much faster.

Reviewing and Restoring

RTILA X provides access to saved revisions from the project interface. You can review the version list, inspect a previous state, and restore it when needed. Restoring a version does not necessarily delete later versions; the newer history remains available in case you need it again.

The process is designed to be low-friction. You do not need to manage separate backup files or naming conventions. The application handles the revision trail in the background.

Works Well with Export Workflows

If you compile standalone bots for clients, version history gives you a clean source record for each delivered product version. You can identify which source revision produced a particular bot and restore that revision if you ever need to rebuild an old client version.

This connection between source revisions and exported products is valuable for support and licensing. Instead of relying on memory, you can trace exactly what a client received.

Frequently Asked Questions

Does version history work automatically?
Yes. RTILA X records changes as you edit projects, allowing you to restore earlier states.
Can I compare two versions?
You can review the command structure and settings of saved versions, depending on the current interface.
How far back can I roll back?
The available history depends on local project storage, but RTILA X keeps a meaningful revision trail for active projects.

Ready to Get Started?