Build it for me
Switch it on and it reads the repositories you work in, then suggests small improvements — each with a reason, a plan and a size. Press Go and a chat builds it and opens the pull request.
New: Universal sign-in — it signs in anywhere you can
An assistant that actually does things.
Hand it the errand you keep putting off, or the bug you never get to. It works on a computer of its own — browsing, signing in, writing code — and tells you when it's done.
Sign in with GitHub, Google, a passkey or a password. Pay only for what you use.
Cut the Actions bill
Working
Universal sign-in New
It signs in anywhere you can.
Most agents stop at the login page. Yours signs in the way you do — with your passwords and passkeys, the codes texted and emailed to you, and your Google account — everything a sign-in asks for, on any website, without the AI ever holding the real thing.
- Passwords and passkeysFrom your own Bitwarden vault
- Email codes and sign-in linksGmail, iCloud, Outlook or any IMAP inbox
- Texted codesThe Android app, or a Mac for your iPhone
- Your Google accountSigned in once, in a browser of its own
- Your Apple accountComing soon
Universal sign-in
Hands your agent stand-ins.
Swaps the real values in on the way out.
Swaps the real values in on the way out.
Any site you can sign in to
- your bank
- the airline
- the electricity company
- your tax portal
- the dentist's booking page
- GitHub and Google Cloud
- that site with no API
Signing in to your bank
- Stand-ins, never secretsThe AI types a random stand-in of the same length; the real password is swapped in on its way to the website. It never appears in a chat or reaches the model provider.
- Your device says yesYour logins, mail and texts are sealed to your own phone and browser. A chat can use them only after one of them allows it.
- One chat, one keyGive a chat the one login it needs — not your whole vault — and take it back mid-task if you change your mind.
For the boring stuff
Ask once. Come back to it done.
Each request gets a real browser on a computer in the cloud. It signs in with your saved logins, reads the code that was texted or emailed to you, and works through the steps — while you do something else. Watch it any time, or take over for a CAPTCHA.
- Several things at once. Start a few requests and it keeps each one going, then tells you as each is finished.
- Talk to it. Say what you need from your phone, or from the car with the driving view.
- It checks back. When something needs you — a choice, an approval — it asks, then carries on.
- ›Move my domain's DNS to Cloudflare and check that email still arrives
- ›Find every donation receipt in my email from last year and total them for my taxes
- ›Reorder last week's groceries, but swap the oat milk for almond
- ›Compare flights to Lisbon for the second week of May and book the cheapest morning one once I say yes
- ›Download this month's statements from my bank and put them in one folder
- ›Cancel the subscriptions I haven't used since the summer
For your side projects
Describe the change. Merge the pull request.
Every chat has its own Linux sandbox with your repositories cloned in. It runs your tests, opens a pull request on GitHub or Forgejo, and you review and merge it without leaving the chat.
- Claude Code or pi does the work, with the model you choose.
- Bring your own. Use your Claude subscription or your own API keys, or pay as you go here.
- It fixes its own CI. When a check fails on its pull request, it is told, and tries again.
- Build tools for it. Turn any repository into an API your chats can call, and share it in the marketplace.
Fix a flaky test
Done
The reconnect test fails one run in ten on CI. Fix it properly — no sleeps.
AGENT
The test checked for close code
1012 before the server had sent it. It now waits for the close frame. 200 runs, 0 failures.you/your-app #212Open
Wait for the close frame in the reconnect test
fix/reconnect-race → mainFor the big asks
Some jobs need a team, not one chat.
Say "build it with a JIT harness" and the agent writes a small program for your request that runs the work through other chats: some in parallel, some feeding into the next, some going back and forth until the work is good enough. You read the program before it runs, or tell it not to bother.
- Thinkers and builders. One chat works out the design, or the legal side, while another builds it.
- A builder, a reviewer and a judge. One does the work, one says what to fix, and one scores it against your checklist. They go round until the score is high enough.
- Many hands. A long list of separate chores, done at the same time.
- It can wait days. Nothing runs while a chat is working, so a slow step costs nothing. When it is all done, your chat tells you what came of it.
Café name brainstorm
Waiting on chats
- #1Brainstorm five playful names for a café on a bike path
- #2Brainstorm five French-inspired names
- #3Brainstorm five minimalist names
- #4JudgeShortlist the best three of these fifteen
- #5CriticDo you agree with the judge's pick? Say why
Also in the box
It finds work, shows its work, and lends you its tools.
Three things that start where an ordinary chat stops.
Dashboards
Ask for a page and a chat writes one, live at its own address the moment it is done: charts that read your connected APIs, kept private to you, run in a locked-down frame.
A portable API
The APIs your chats call — yours or the marketplace's — work from any script or app too. Make a client secret, limit it to the APIs it needs, and rotate or revoke it whenever you like.
You decide what it can touch
Each chat gets exactly the access it needs.
A new chat starts from a profile you set up. Grant it one site's logins, your mailbox read-only, or a single repository — and take it back mid-task if you change your mind.
Per-chat permissions
Logins, mail, texts, repositories and tools are granted chat by chat, read-only or full, and checked on every call.
Its own computer
Every chat runs in an isolated sandbox, away from your devices. Turn its internet off and it can still reach its model and nothing else.
Watch it, or take over
Every chat's browser is live. Watch it work, and take the controls for a CAPTCHA or a sign-in only you can finish.
Profiles
Save a set of permissions — "errands", "this repo only" — and start any new chat from it in one tap.
Lend it your laptop
Run chats on your own machine instead of ours, or send its web traffic out from your home connection.
Your data, your call
Download everything, or delete your account and all of it, from Settings at any time.
Pricing
Pay for the time it works.
You are charged for the minutes a chat's computer is running. When a chat goes quiet, its computer is shut down.
Credits
Pay as you go
Top up when you like and spend as you go. Every purchase comes with a receipt.
Pro
$10 a month
Usage included every month, for when you use it most days. Credits only once it runs out.
- Public links to chats and tools
Team
$20 a seat a month
Pro for everybody, with the usage pooled. From 2 seats.
- Share private tools with the team
- Share chats with the team's admins
- One data policy for everybody
Enterprise
$45 a seat a month
Everything in Team, with more usage per seat. From 10 seats.
- Admins can read every member's chats, and members are told
Bring your own keys on any plan: use your Claude subscription or your own API keys for the model, so model costs go straight to your provider.
Refer a friend: when they sign up through your link and first pay $10, they get $10 in credits and you get $20.
What have you been putting off?
Make an account and ask it. It can read the codes texted to you, too, so it can sign in where a site sends one — through the Android app, or for an iPhone, a Mac signed in to your Messages.