Skip to main content
You never operate your assistant’s computer for it — you just ask for outcomes, and it decides when the work needs a screen. Here’s what that looks like in practice.

​
Browsing the web

The browser is the workhorse. Your assistant can open sites, sign in, navigate, fill forms, read pages, and download files — everything a person does in a browser tab:
  • “Book the usual meeting room on the facilities portal for Thursday.”
  • “Download last month’s statement from the supplier site.”
  • “Check what our product page looks like and tell me if the pricing table is out of date.”
It can run several browser sessions at once — a visible one for work you might want to watch, and background ones for quick lookups that don’t need an audience. It reads pages visually as well as structurally, so even awkward, JavaScript-heavy interfaces are workable. When a site throws up a CAPTCHA, the platform can solve the common kind automatically rather than stalling.

​
Using applications

Beyond the browser, the desktop itself is fair game: native applications, the file manager, the terminal. If a job needs software, your assistant can download, install, and use it — spreadsheet tools, document editors, whatever the task calls for. You don’t need to provision anything.

​
Working with files

The assistant’s machine has a persistent working folder that ties the whole platform together:
  • Attachments arrive there. Any file you send — in Console chat, by email, over WhatsApp — lands in its Attachments folder, ready to be opened and worked on.
  • Downloads and outputs live there. Files it pulls from the web, documents it produces, intermediate work — all on its machine, and it can send you any of them back over any channel.
  • Nothing evaporates. The workspace persists across sessions — the spreadsheet it built for you last week is still there when you ask for an update. More on this in The machine.

​
When does it use the computer vs. everything else?

You don’t have to think about it — your assistant routes work sensibly. As a rule of thumb:
  • Connected integrations and the workspace come first when they cover the job — they’re faster and more reliable than clicking through screens.
  • The computer takes over when there’s no integration for the tool, the work is inherently visual, or files and software are involved.
  • The two combine freely: pull data from the CRM, work it over in a spreadsheet on the desktop, email you the result.
Computer work also runs inside scheduled tasks — a weekly task can log into a portal, download the new report, and send you the highlights, screen and all, with nobody watching.