Browser Interaction
Browser automation blocks live under Browser Interaction ▸ Browser Commands in the Toolbox.
This page explains how to start a browser session, supply “smart” parameters, control wait behaviour, and type text or passwords safely.
1 · Activating the browser
- Open the Browser tab in the right-hand sidebar.
- If a session is already running (for instance, from the agent chat), it appears here.
- If no session is running, a cloud-hosted browser instance launches automatically.
- Every Browser-category block in your flow (Navigate, Click, Type Text, etc.) targets that live session.
2 · Smart parameters (URLs, selectors & keys)
Many input fields in Browser blocks are smart parameters—they accept either an exact, literal value or a short natural-language phrase that Aidolons resolves at run-time.
| Where used | Exact input examples | Natural-language examples |
|---|---|---|
| Navigate → URL | https://news.ycombinator.com | google |
| Click → selector / target | //*[@id='login'] (XPath) button.login (CSS) | the login button |
| Press → keys | Ctrl+A Enter | control a return CTRL |
Notes on Press keys
• Case and spacing are ignored: control, CTRL, or ctrl all map to the Control key.
• Compound shortcuts (Ctrl+A, control a, ctrl-a) are recognised automatically.
• Common names such as enter / return or esc / escape are interchangeable.
Use whichever style—exact or natural language—is most convenient; the engine will interpret it correctly at execution time.
3 · Wait behaviour for Click / Press
Both Click and Press blocks expose a Wait option under Advanced:
| Value | Effect |
|---|---|
| True | Pause until the next navigation completes. |
| False | Continue immediately after the action. |
| Auto (default) | AI looks at context (form submits, link clicks, etc.) and chooses whether to wait. |
Choose True for guaranteed post-navigation stability or False for single-page apps where no reload occurs.
4 · Typing text and passwords
| Block | Privacy note |
|---|---|
| Type Text | Sends the literal keystrokes directly to the remote browser. |
| Type Password | Same behaviour—no entered value is sent to the LLM at any point. |
Even with this safeguard, it's recommended to use dedicated or low-privilege accounts when automating logins.
That practice keeps runs auditable without exposing personal credentials.