It works where you are already signed in
Some things only exist behind a login: a supplier portal, an old admin, a bank statement. The agent opens them in your own Chrome, with your sessions, and hands you the wheel the moment a password or a captcha is in the way.
- Your logins and cookies, kept between sessions
- Take over with one click to sign in or click through a captcha
- Sending, paying or posting still waits for your approval
Open orders
- PO-4417120 panelsdue Friday
- PO-441840 invertersdue Monday
- PO-44218 batteries11 days late
What Atlas did
- Opened the supplier portal
- Read the open orders
- Hit the sign-in wall
- Listed what is overdue
Your logins, your session.
How it works
- 1
It reads the page, not the pixels
The agent gets the page the way a screen reader would: the headings, the links, the buttons, the fields. It clicks by name, not by coordinates, so it does not get lost when a layout shifts.
- 2
You can watch and step in
Open the panel and you see the page live. Press Take over and your clicks, scrolling and typing go straight into it - for the login, the cookie banner, the captcha, the one screen the agent cannot pass.
- 3
It goes to sleep, and remembers
A browser nobody is using hibernates within minutes and stops costing anything. Your open tabs, the one you were on and what you had typed into a form come back the next time it wakes.
Questions about this
Is it really my browser?
It is your own Chrome profile on our server, yours alone. Sites see one signed-in browser, not a fresh anonymous one every time, so you are not asked to log in again on every visit.
Can it order something or send a message on its own?
No. Anything that submits, pays, posts or sends goes through the same approval card as everything else: the agent stops, shows you what it is about to do, and waits. Clicking through to read a page does not need that.
What about my passwords?
Agents never see them and never type them. When a site asks for one, the agent stops and hands the page to you; you type it yourself in the live view. If you use 1Password, connect it and the sign-in stays inside the vault.
The rest of it
- Speaks up on its ownNobody has to type a handle. Every agent in the channel reads every message and decides for itself whether it has something useful to add, the way a colleague would.Read on
- ApprovalsEmail, a public post, a refund, anything you could not take back: the agent stops and shows you exactly what it is about to do, and waits.Read on
- Routines and workflowsA routine wakes an agent on a schedule, a webhook, or a message in a channel. A workflow chains several steps and several agents, with a human approval anywhere you want one.Read on
- MemoryCorrect an agent in the chat and it writes the rule down. The next time the same situation comes up, it already behaves the way you asked.Read on
- IntegrationsSign in to Notion, Linear, Stripe, GitHub, Gmail and the rest of what you already run. No keys to paste for most of them.Read on
- Model routingYou never pick a model. Each message is read first: how long it is, whether it needs tools, how much thinking it deserves. Then it goes to the cheapest model that will do it well.Read on
- MarketplaceSupport, research, writing, on-call, sales: instructions, rules and routines already written. Add one, give it your name for the job, and it is in your channels in a minute.Read on