WebPilot
An AI that works the web for you.
WebPilot gives your AI a real browser. A pilot is a browser set up for one job: the sites it may visit, what it may do there and how to use them. You give it a task in its chat and watch it work, or drag it onto an AI agent and the agent browses with it.
Everyone you share the workspace with as a team member sees the pilots you choose to share, and can run them. Only you change them.
Make a pilot
Open WebPilot
Go to the WebPilot page. With nothing there yet you see one box with the way to start.
Press New pilot
Press New pilot. The pilot setup window opens.
Name it and say where it may go
Write a name, then the sites it may visit, one per line. Leave the sites empty to allow any public website. A page given in full is where the pilot starts.
Choose what it may do
Pick one of the three levels: read pages only, fill and press asking first, or act without asking. No level ever types a card number.
Add notes, then create it
Write how to use the site if it helps, and press Create. The pilot opens.
Common jobs
- Give a pilot a task. Open it and write in the prompt box at the foot. The answer goes on in the assistant's panel at the right edge, where the pilot browses, and the pilot's page turns into its live browser. Under the box, three asks made from its first site are one press away.
- Watch or stop a flight. A run that is working or waiting on you stands on the pilot's page as a card. Watch opens its chat, Stop closes its browser. When a run stops to ask you something, it is answered on the live browser or in the chat: a yes or no, your own words, or sign in details that go to the run's browser only and are never stored.
- Change a pilot. Press Setup in its header, or use the three dots on its card. Saving a change does not interrupt a flight in the air; the next message uses the new setup.
- Give an agent a browser. Drag a pilot's card onto an AI agent. The agent then has it as a tool. Every agent that uses a pilot shares its setup.
- Run a pilot on a schedule. Open the pilot's Workflows window. A workflow that runs the pilot starts it by itself and tells you when the answer changes.
- Let the pilot browse from your own server. In setup, switch on Browse from this workspace's server, so sites see that server's address. It needs a server of the workspace that is running.
- Delete a pilot. Use the three dots on its card or in its header. A delete asks first, and takes the pilot's runs and pictures with it.
What the page tells you
A line at the top says how many pilots you have and how many are waiting for you, working or failed. At its end, quiet, it says what the plan has left: pilots used, and browser time used this month.
Each pilot is a card with a print of the page it last browsed, its last run's state, its name and when it last ran. A pilot waiting on you comes first. A card that flies shows its route, one dot a step. Past twelve pilots the cards become a grid with search, filters on state, what it may do and owner, sortable columns, and ticks to delete many at once.
If WebPilot is switched off, your pilots are kept and agents that have one browse on the Free plan's hours. The page says so, with a way to switch it on. When every pilot your plan includes is in use, or the month's browser hours are used, it says that too. Open the plans window from the card icon in the header.
Inside a pilot, the top says who it is: where it may go, how far it may go, this month's browser time and its next scheduled run. Under it stands only what is active. Past runs are not listed on the page; each one lives in its own chat.