The operator's browser, in beta
A real browser that looks things up, fills forms and prepares a payment.
The operator can drive a real web browser to do one task on a website: look something up behind a sign-in, compare options, fill in a form, walk through a booking, or prepare a payment that you then complete. The browser runs in the cloud, you watch it from the chat, and whenever the site needs something only you hold, Roma asks you inside the chat. Computer use is open to every account, in beta.
When the operator reaches for the browser
The browser is for a site that has to be operated, never for one that only has to be read. A status or a balance behind a sign-in, a form to fill in or submit, a booking or an order to walk through, options only an account shows, a map or a listing that only renders in a browser, a payment to prepare: those are browser tasks. Reading the public web, however much of it, is a search, and web search and research explains that side.
Before it starts, the operator makes sure it has every fact the site will ask for. It looks in your notes and in what it knows about you, and when something is missing it asks you first and waits. A site that one of your connected apps already fronts, such as your calendar or Notion, is handled through the connection rather than the browser unless you ask for the browser in your own words. The browser never starts on a site you did not name, and it never opens a search engine on its own.
What you see in the chat
The run is a card in the chat. While it works, the card reads "Using the computer" over the current step and the page it is on, with a small screenshot that refreshes as it goes. When the run ends, the card settles into a receipt: what happened, the number of actions, how long it took, the site, and the final screenshot as a thumbnail you can open full size. The operator's own words carry the outcome, such as the balance it found or the order it prepared.
The run belongs to Roma's servers, not to the window that started it. Close the tab or lock your phone and the browser keeps going. A card waiting for you shows on every device you are signed in on, and a Done pressed on your phone settles the card on your Mac.
Signing in
When a site asks for a sign-in, Roma asks you in its own card inside the chat, never in the live browser. The card shows the fields the page shows, you type your username and password, and Roma types them into the page for you. The values go straight to the page and nowhere else: the operator never sees them, nothing stores or logs them, and the box on the page is cleared the moment the site has answered. Your own password manager can fill the card, because the card is an ordinary form on roma.app. Roma ticks "Keep me signed in" when the site offers it. The card says "You signed in." only once the site itself confirmed the sign-in.
In the beta the browser takes no second verification step. When a site asks for a code, asks where to send one, waits for an approval on your phone, or accepts only a passkey, the run stops and the operator says so plainly and suggests the nearest thing you can do yourself. Nobody is asked for a code.
A sign-in the site confirmed is kept for that site, so the next run on it opens already signed in. Under Settings and Connections, Browser sign-ins lists every site Roma is signed in to, with Forget on each. The sign-in belongs to your Roma account rather than a device, so a sign-in made on the Mac is what a run from your iPhone opens with. A site can still sign you out on its own, and then Roma asks again.
Payments
A run that may prepare a payment asks first, on a card that names the task and says you will enter the card details and press Pay yourself. The browser fills in everything else, then hands you the live browser inside the chat for the card details and the final button, with Done and Cancel under it. Roma never sees your card details, and the operator never presses Pay. The approval card is one of the cards covered in approvals.
What the browser never does
A CAPTCHA is never your job. The browser clears one itself, and a CAPTCHA it cannot clear ends the run with the operator saying so. A site that blocks automated browsers ends the run the same way, with nothing else offered. The browser never types credentials on its own, never submits a payment, and treats everything it reads on a page as data rather than as instructions.
In an automation and in Settings
An automation's run gets a browser too, limited to public pages: no sign-in and no payment, so it can check a page or collect a listing on a schedule. See when an automation runs. Under Settings and Permissions, the row Use the computer lets you ask for a card before every browser run, or switch the browser off for your account entirely.
Questions people ask
Can the operator sign in to a website for me?
Yes, with your username and password, which you type into Roma's own card in the chat and Roma types into the page. A site that then asks for a second verification step, such as a code or an approval on your phone, ends the run in the beta, and the operator tells you so.
Does Roma see my password or my card details?
No. A password goes from the card to the page and is cleared afterwards, and nothing stores or logs it. Card details are typed by you in the live browser, which the operator hands to you for exactly that and the Pay button.
Why did a browser run stop?
The operator says which it was: a second verification step the beta does not take yet, a passkey-only sign-in, a site that blocked the browser or did not answer the sign-in, or a CAPTCHA it could not clear. A run that ran out of steps reports where it got to, and the operator continues once from that page when something is still open there.
Can I watch what the browser is doing?
Yes, from the card in the chat: the current step, the page it is on and a screenshot that refreshes as it works. When the run is over, the final screenshot stays on the receipt and opens full size.