AI-Assisted Editing
The AI works directly in the Commands view. Describe in plain language what should happen, and the AI adds, changes or describes actions right in the tree you are working in. You can also write the whole scenario as text and let the run build each part on the live screen.
Nothing is written behind your back: every AI proposal is first shown in the Commands tree, and the scenario changes only when you click Apply.
/img/editor/ai-editing/overview.pngCapture: the Commands view with the AI menu open next to Add, and AI descriptions shown dimmed under the action names. Why it must be retaken: the AI text tab shown in the old screenshot no longer exists.
The separate AI text tab is gone, together with Fetch descriptions, the per-action β» Sync button and the tab's settings (Auto mode, Context and the others). Everything the AI does is now in the AI menu. Descriptions saved with your scenarios in earlier versions are kept and shown under the actions.
Before you startβ
The AI writes actions for a screen, so it needs a connected robot that has one β Desktop, RDP or Web. Until a robot is connected, the AI menu says Connect a robot to use the AI and its entries are unavailable. A Passive robot has no screen, so the AI does not generate actions there either.
While a run is in progress, Add with AIβ¦ and Edit selection with AIβ¦ are unavailable β the AI must not rewrite actions the robot is executing.
The AI menuβ
The AI menu sits next to Add in the Commands header. Its first three entries are also in the right-click menu of the Commands tree.
| Entry | What it does |
|---|---|
| Add with AI⦠| Adds new actions after the selected one. See Adding actions. |
| Edit selection with AI⦠| Changes, rearranges or removes the selected actions. Needs a selection. |
| Describe with AI | Writes a short plain-language description of the selected actions β or, with nothing selected, of every action that has none yet. |
| Scenario template | Opens the text pane above the tree in which you write the scenario as text. See Scenario template. |
| Show AI descriptions | Shows the descriptions under the action names. On by default. |
| Detailed descriptions | Shows the step-by-step technical description instead of the one-line summary. Available only while Show AI descriptions is on. |
Adding actionsβ
- In the Commands tree, select the action after which the new ones should go.
- Choose AI β Add with AIβ¦ (or right-click and choose the same).
- In the Add with AI dialog, describe what should happen β for example Click 'Save' and wait until the confirmation appears.
- Click Send, or press Ctrl+Enter. Enter only starts a new line, so you can write a longer, multi-line instruction.
- The dialog shows Processing⦠while the AI works. Cancel closes it and drops the request.
- The proposal appears in the tree β see Reviewing a proposal.
Where the new actions land depends on the selection:
| Selected | New actions go |
|---|---|
| An action | Right after it. With several selected, after the last one. |
| A Section | At the end of the section. |
| An empty block or a Condition branch | Inside it. |
| Nothing | At the insertion cursor; without one, at the end of the scenario. |
One instruction can produce several actions β the AI decides how many steps your description needs. If the AI's reply would change nothing, the dialog stays open and shows why, so you can rephrase.
Changing selected actionsβ
- Select one or more actions in the Commands tree.
- Choose AI β Edit selection with AIβ¦.
- The dialog title says how many actions are selected. If the actions were written by the AI, the field already holds the instruction they came from, so you can adjust it instead of retyping it.
- Describe the change β Change the typed text to 'hello world', Wait 5 seconds longer, Remove these steps β and click Send (Ctrl+Enter).
Reviewing a proposalβ
/img/editor/ai-editing/add-action2.pngCapture: the Commands tree showing an AI proposal β a new action and a changed action highlighted β with the proposal bar above the tree (Edit prompt, Apply, Discard). Why it must be retaken: proposals are no longer shown in the AI text tab.
The tree shows the scenario as it would look with the proposal applied. New, changed and removed actions are highlighted; removed actions stay visible, marked, so you can see what would go away. A line under a changed action shows what it was before (Before: β¦), and a new action shows what it does.
The bar above the tree summarises the proposal β for example AI proposal: +2 new Β· ~1 changed β and repeats your instruction. Hover over the summary to see the full list of changes.
| Button | Effect |
|---|---|
| Apply | Writes the proposal into the scenario. |
| Discard | Leaves the scenario as it was. |
| Edit prompt | Reopens the dialog with your instruction filled in, so you can adjust it and get a new proposal. |
Actions with a missing targetβ
Sometimes the AI cannot find the element an action should work with β a Click or Get without its target, for example. Such an action is added disabled, and after Apply a warning names the action and the missing field. Pick the element by hand and enable the action again.
If an action with an empty target is run anyway, it fails immediately with a clear message, instead of failing later with an unclear error.
When the AI writes a message such as "Processed $count invoices", $count is stored as a
real variable reference, so it is substituted at run time. A reference resolves even when the
variable is created elsewhere in the same reply, and the preview shows what Apply will
actually store.
If the AI produces an expression that cannot be evaluated, the warning after Apply names the field you need to fix by hand.
AI descriptionsβ
An AI description is a short sentence shown dimmed under an action's name β "Press Ctrl+S to save the file." β so you can read the scenario as prose without opening one form after another.
- Describe with AI describes the selected actions, even those that already have a description. With nothing selected, it describes every action that has none yet.
- Actions the AI writes get their descriptions automatically.
- When you edit an action, its description is hidden until you describe the action again β the tree never shows a description of something the action no longer does.
- Descriptions are stored in the project file, so they load instantly and the AI is called only when you ask for it.
Show AI descriptions turns the descriptions on and off; Detailed descriptions swaps the one-line summary for the step-by-step technical description.
Languageβ
The AI answers in the language you write in. An English instruction gets English actions and descriptions even in an Editor set to Czech. Descriptions that are written again keep their language, and changing the interface language does not trigger new descriptions.
Scenario templateβ
A scenario template lets you write the whole process as text β or paste it, for example straight from a Google Doc or a Word document β and let the run build the actions for each part on the live screen.
- Choose AI β Scenario template. The Scenario template pane opens above the Commands tree.
- Type or paste the process and split it into parts (see below).
- Each part becomes a Section in the tree, with the part's name as the Section name and its text as the section's Description.
- Run the scenario. When the run reaches a section, the AI writes its actions.
The template is saved with the scenario. The pane's close button only hides it; AI β Scenario template shows it again.
Splitting the text into sectionsβ
| You write | Result |
|---|---|
A line section: name (or the Czech sekce: name) | Starts a new section called name. |
| A heading (Heading 1β3) in text pasted from Google Docs or Word | Becomes a sekce: name line automatically. |
A horizontal rule β a line such as --- | Ends the section; the next line becomes the name of the next one. |
| Lines before the first section | Form one section without a name. |
(only in test environment) after a section name | The section is created as Enabled (Test), so it does not run in production. |
Everything under a section name is handed to the AI as one instruction β the lines are not split, so a condition or a loop can span several of them.
Warningsβ
The pane checks the text as you type and lists what looks wrong under it:
- a section name with no steps under it (the section is skipped),
- a section name used more than once,
- a section longer than the AI service accepts (2,048 characters) β split it,
- placeholders left to fill in, such as
<shared folder>, - names that are neither variables nor Vault keys.
Names are checked when they look like variable names β words joined with an underscore, such
as invoice_number. A line name = value in the template declares a variable the run
creates, so it does not count as missing.
When you start a run while such names are missing, the Missing variables dialog lists them and lets you cancel to add them first, or run anyway.
Keeping the template and the tree in stepβ
- Editing the template updates the sections in the tree. A section whose text did not change keeps the actions already built for it; a section whose text changed is built again on the next run.
- A section removed from the template is removed from the tree. Actions and sections you added by hand stay where they are.
- Editing a section's Section name or Description in the tree updates the template text.
How a run builds a sectionβ
When the run reaches a section that has no actions yet, or whose Description changed since its actions were written, the AI writes the actions on the spot. It uses what is on the screen and the values of the variables at that moment. The run bar says The AI is writing 'β¦'β¦, and while a template scenario runs it also counts the built sections β for example Running Β· 2/5 sections.
The written actions are put into the tree, run straight away and kept for the next run, so the AI is called again only when the section's description changes. A section whose actions you built by hand is never rewritten.
If the AI added a step it could not complete (see Actions with a missing target), the run pauses on the section. Fix the step and click Continue. File β Export as Python writes a section that has not been built yet as comments with its description.
For pausing, continuing and skipping steps during a run, see UI Overview.
Conditions keep exactly two branchesβ
A Condition always has its True and False branch and nothing else. When the AI misplaces a step that would become a third branch, that step is put after the Condition instead of inside it.
Scenarios corrupted by an older version β the ones that refused to open with "Condition action must have exactly 2 children" β repair themselves when opened in 0.24.0 or later.
Loops nest normallyβ
Loops have no such branch limit. When your request calls for repetition β "for every row in the tableβ¦", "for each e-mail with an attachmentβ¦" β the AI creates a loop block, most commonly Repeat for each item in iterating over a list variable, and places the repeated steps inside it as its children. Repeat until and Repeat x times work the same way, and loops can nest β a loop over e-mails can contain a loop over each e-mail's attachments. See Loop actions for what each loop type does.