Choose a Robot kind

Robot kind selects the execution target. Review it in effective settings before authoring a new scenario. Availability also depends on your authorized workspace and capacity.

Kind	Best fit	Important difference
Browser	Interactive web applications, page extraction, scripts and tabs.	A rendered page and supported Browser locators/input.
HTML	Source-based navigation, link following and extraction.	No page-script execution or Browser typing. Visual Toolbox authoring does not change ordinary source execution.
Console	Bash commands and text/structured processing.	Terminal output/input, no graphical display or DOM.
Desktop Linux	Visible Linux applications and physical interaction.	Coordinate-based input and a fixed 1280 × 900 desktop; no Browser DOM selector tools.

Desktop Windows is not an available target described by this guide.

A small Console test

Create a Console Job with one Exec action whose literal Bash source is:

printf 'Hello from the example Job\n'

Apply, then Play and inspect terminal output. Exec source is literal Bash, not an Eyerobot text template: shell ${...} syntax keeps its shell meaning.

Success requires a zero exit status; a nonzero command exit fails the action. Set working variables using supported scenario actions rather than assuming an Exec command’s stdout automatically becomes one.

Toolbox offers interactive terminal input under the current owner’s rights. Its persistent shell can retain shell state between inputs, while separate Exec actions are not implicitly the same interactive shell. Terminal output is a bounded live view, not proof of a complete saved transcript.

A Desktop test

1. Select Desktop Linux and open its Toolbox.
2. Use the display to identify the intended application/control.
3. Choose a coordinate-capable action and use its point picker or numeric axes.
4. Apply the edit and test the action.
5. Use supported Type or visible-screen capture as needed.

Desktop Type inserts at the active caret; it does not automatically select and replace every character like a located Browser Type. Scroll follows the application, so requested wheel units are not a promise of an exact pixel displacement.

Desktop browsers remain ordinary desktop applications. Opening one does not grant Browser DOM extraction, page scripts or Browser profiles to the Desktop Job. Changes to the temporary desktop do not establish reusable installed applications across future Sessions.

Switching an existing Job

Check inherited settings before changing kind. Native targets cannot use a Browser start URL, Browser profiles, page resources or DOM-based conditions/extraction. Correct incompatible source explicitly; do not silently remove it just to make validation pass.

Choose a test scope with safe inputs. A successful import or launch acknowledgement is not proof that all steps can execute on a different target.