Its own browser

Each Autobot has its own browser. A side panel shows it live while it works, so you see every page it opens instead of a list of tool calls.

• It opens its own browser. Every Autobot has a real browser of its own. It never starts one until it needs a page.
• You watch it live. The Browser tab shows each page as it works. Click the preview to see it at full width.
• You step in if needed. Take over for a sign-in or a captcha, then hand it back.
• Save what it did. Record the session as a workflow to run again.

Click Take over to drive the Autobot’s browser yourself for a sign-in, a captcha or a tricky step, then Hand back and it carries on from that page.

• Click Take over. The live view becomes yours: click, type, press keys and scroll.
• Finish the tricky step. A sign-in, a captcha, or the step it kept getting wrong. Native dropdowns show their options right in the view.
• Click Hand back. The Autobot is told to carry on from the page exactly as you left it.
• Or just Stop. End the browser session without handing back.

Record everything that happens in the Autobot’s browser, your clicks or its own steps, and save it by name as a workflow you can run again.

• Start recording. Choose Record a workflow. Recording can open the browser on a start address.
• Do it, or ask for it. Click and type in the browser yourself, or ask the Autobot in chat; both become steps.
• Name it and stop. Give it a name, like “Login test”. Saving it adds it to Workflows.
• Run it again. Run any saved workflow from the list, by you or by an Autobot on a schedule.

Replays find a step’s element by meaning when a page has changed and mark the step healed, the signal that a site drifted since the recording.

• Run a workflow. Every step shows its result as it replays.
• A page has changed. If a step’s element is not where it was, it is found by meaning, “the Create project button”, instead of failing.
• The step is marked healed. You see exactly which steps needed healing.
• Treat healed as a signal. For a test, healed means the site drifted since the recording.

Name a recording, stop it, and the Autobot writes an Autodocs how-to document with screenshots of every step, listed under Docs your Autobots wrote.

• Record the task once. Do it in the Autobot’s browser, or ask the Autobot to.
• Stop with a name. “Stop recording and write a how-to doc with this name.”
• It writes the doc. An Autodocs how-to with every step and its screenshot.
• Find it later. Listed under “Docs your Autobots wrote about what they did.”