跳转至

Task Route Mechanism

A task route is generated from a real task run. It records useful navigation and operation evidence so the same task can run more deterministically next time.

Task route generation

Why routes are useful

Without a route, every run depends more heavily on the model observing the screen and deciding the next step. This is flexible, but slower and less stable.

With a saved route, AutoLXB can first replay known page navigation and stable actions. The vision model is then used for dynamic parts that still need judgment.

How a route is generated

During visual execution, AutoLXB records:

  • Screenshots and model observations.
  • Model actions and expected results.
  • XML / accessibility nodes when available.
  • Text, content description, resource id, class, bounds, parent features, and related UI attributes.

When the model clicks, inputs, or swipes, Core combines the visual action with the current UI structure. After the run, you can review these recorded actions and save useful ones as the task route.

Targeting strategy

For tap steps, AutoLXB tries several strategies from more stable to less stable:

  1. Locator targeting: use text, content description, resource id, class, parent relation, and similar structural features.
  2. Container probing: validate the clickable container near the original tap point.
  3. Local coordinate fallback: keep a local tap point or fallback point when the UI cannot be described reliably.
  4. Semantic adaptation: portable export converts coordinate-backed taps into semantic descriptions; after import on another device, the first replay asks the vision model to adapt those semantic steps into local executable steps.

Local reuse and cross-device import

On the same device, saved routes are optimized for local repeatability.

Across devices, coordinates may not transfer perfectly because screen size, font scale, app version, and login state may differ. For imported tasks, AutoLXB tries to adapt semantic steps on the new device and then writes the adapted local result back to that device's route asset.

When a route fails

A route may fail if:

  • The app UI changed.
  • A popup or ad blocks the page.
  • The target account state is different.
  • A coordinate-backed step cannot be adapted on the new device.

When this happens, AutoLXB can fall back to visual execution. Use Trace to see which route step failed and why.