Skip to main content
Optexity uses a declarative model for browser automation. Define what actions to perform, and Optexity handles the how using AI-assisted element location.

Overview

Complete Example

Properties

Parameters

Three types of parameters control data flow:
See Parameters for detailed usage.

Node Types

Browser Channel

Expected Downloads

Set this to wait for file downloads to complete:
The automation waits until all expected files are downloaded before completing.

OS Emulation

Override the OS reported in the browser’s user-agent string:
Only set os_emulation when a site serves different content or layouts based on the OS. Leave it as null otherwise.

Max Retries

Control how many times the full automation reruns when an unexpected error occurs:
max_retries is the total number of attempts, not the number of extra retries. AssertionError failures are never retried regardless of this value.
See Timing & Retries for controlling per-element retry behavior (max_tries) vs. full-automation retries (max_retries).

Reuse Page If Already On URL

Every run navigates to url before the first node executes, even on a warm dedicated instance. Set reuse_page_if_already_on_url to leave the existing page untouched when the reused browser is already sitting on url:
Use this only for portals that break when their page is reloaded — some session-bound portals throw an error or invalidate the session on any refresh, so the safest thing is not to navigate at all. The URL comparison is exact on scheme, host, path, query string, and fragment — only a trailing slash on the path is ignored. A hash-routed portal on #/dashboard therefore does not match a url of #/home. Anything that doesn’t match falls back to normal navigation, so enabling the flag can never leave a run stranded.
Your first node now runs against whatever the previous task left behind — an open modal, a filled form, a scrolled list. Make it tolerant of a mid-session page, or pair it with an if-else node that resets the portal to a known state.