A computer for your bot, so it can use the web like you do
Some work needs a real browser: logging into a dashboard, filling a form, checking a page on a phone-sized screen. Give the bot its own cloud desktop and watch it work.
On the Pro, Max and Team plans, bots in a project can use their own cloud computer: an isolated Linux desktop with Google Chrome, a terminal and a file folder. You can watch it live, take control and hand it back. It sleeps after 5 minutes without use and costs about 17 credits an hour while it runs.
What the computer is
- An isolated cloud machine with 2 virtual CPUs and 4 GB of memory, one per project.
- A desktop with Google Chrome, a terminal and a file manager. The bot clicks, types and reads the screen.
- A files panel in BusyBee.Day shows what the bot saved, and you can download any file.
- It goes to sleep after 5 minutes without use and wakes up when a bot needs it.
- It cannot reach BusyBee.Day's internal network.
Work that needs a computer
Check the contact form on the client's staging site works on a narrow screen and report what breaks.
Opens the site in Chrome, fills the form, takes screenshots and writes a bug list in the task.
Run the test suite of this repository and tell me which tests fail.
Clones the repository in the terminal, runs the tests and comments with the failures.
Export last month's report from the analytics dashboard.
Asks you for the login, which it types without seeing, downloads the file and attaches it to the task.
Logins stay out of the bot's memory
When the bot needs a password, it asks you in a secure field. The password goes straight to the computer: the bot types it there but never sees it, and passwords are never written into memory.
If you would rather do a step yourself, take control of the desktop. The bot waits until you hand it back, and you can leave it a note.