Private beta, free

An always‑on browser for always‑on agents.

Hotkey is a cloud browser that stays signed in to your sites, for developers who run AI agents. Claude Code cloud sessions and other MCP agents use it from anywhere, so they keep working with your laptop closed. When one needs a 2FA code or your OK, your phone buzzes.

Request access

No mail app? Write to hello@hotkey.so

How it works

1
Add Hotkey to your agent

Make a token in the console and add one MCP server. The agent gets browser tools, such as navigate, read_page, find and request_human, that reach only your browsers. Each agent gets its own token, and you can revoke it in the console.
```
claude mcp add --transport http \
  hotkey https://console.hotkey.so/mcp \
  --header "Authorization: Bearer <token>"
```
Sign in to your sites once

Open the browser from the console and sign in to the dashboards, inboxes and admin pages your agents need. The logins stay, as they do in your own browser.
Answer from your phone

When an agent meets a login, a 2FA code, a captcha or a payment, it asks you. Your phone gets a push, you do that step in the real page, and the agent carries on in the same tab.

All your browsers, and everything waiting on you

The console shows what each agent is doing. Open any browser to watch it live, and answer every request from one list, at your desk or on your phone.

One browser per identity. Work, personal and each client get their own browser with their own logins. Agents pick the one they need.
Quick to wake. After 30 quiet seconds a browser pauses, and the next call wakes it in about 40 ms. After 8 idle hours it shuts down with its logins kept, and the next call starts it again in about a second.

The Hotkey console's Browsers page. Work shows its invoices page and asks to pay invoice INV-2041; Acme client asks for a 2FA code. — The console, with sample browsers.

The console's Needs you list on a phone: Acme client asks for a 2FA code, Work asks to pay invoice INV-2041. — The console, with sample browsers.

It asks before it sends or pays

Before the agent clicks a button or link, Hotkey reads its label. Labels that start with Send, Pay, Buy, Delete, Publish, Confirm, Submit, Transfer, Subscribe and similar verbs stay locked until you approve on your phone. One approval unlocks that tab for the next 10 minutes, then the lock is back.

You see what the page says. The approval shows the amount and payee read from the page itself, and flags it when they don't match what the agent asked for.
You type the passwords. The agent never receives your passwords: you enter them in the page yourself, and ones you save in the browser are encrypted on disk.
No other account can reach your browsers. Each account's browsers run as their own system user, with their own files and memory limits, and can't reach our internal network.
Labels aren't everything. A button with only an icon, or a form sent with the Enter key, isn't caught by the lock. The agent is also told to ask before anything that sends, pays or deletes.

An approval on a phone: Work wants to pay invoice INV-2041, $4,200.00, to Brightwater Co. The page's own total matches. Deny and Approve buttons. — An approval on a phone, with sample data.

Questions

What does it cost?

Nothing during the private beta. We'll publish prices before the beta ends and tell beta users first. You can delete your account at any time.

Which agents work with it?

Any agent that can add an MCP server over HTTP. We build and test with Claude Code, including Claude Code cloud sessions, which can't reach your laptop's browser.

How does my phone get the requests?

Through the free ntfy app for iPhone and Android: you subscribe to your own topic, shown in the console. Alerts go through the public ntfy.sh service and carry the browser's name and the agent's reason, so treat the topic name like a password. The push opens the request, where you approve, deny or do the step in the page. You can also answer from the console in any browser.

What if I don't answer?

The agent waits and can keep working on other things. A request lapses after 30 minutes, and the agent sees that it wasn't done.

How is it different from Browserbase or Claude in Chrome?

Browserbase and similar services give developers fresh browsers for scripts, billed by the hour. Claude in Chrome drives the Chrome on your laptop, so the laptop has to stay on. Hotkey is one browser per identity that keeps your logins, is shared by all your agents, and hands you the steps only a person can do.

Where do the browsers run, and who can see them?

On our servers at Hetzner in Germany. Traffic to the console passes through Cloudflare, a US company. Each browser is Chromium, the open-source base of Chrome, with its own profile. Saved passwords and passkeys are encrypted on disk. We run the server and have admin access to it, and we only open a browser to help when you ask, to fix a fault or to stop abuse. The privacy page lists what we store.

Will sites block a browser in a data center?

During the beta your browser connects from a data center in Germany. Some sites ask you to confirm a sign-in from a new place, or show a captcha, the first time. You do that from your phone like any other request. A fixed home-like address in your own country is planned.

What if a server fails?

During the beta each browser lives on one server, and backups to a second place aren't on yet. If that server were lost, you would sign in to your sites again. We'll say here when backups are on.

What happens when the beta ends?

We'll tell you before it ends. You can delete your browsers and your account at any time, before or after.

Can I delete everything?

Yes. Deleting a browser erases its logins, saved passwords and history. Deleting your account does that for every browser. There's no undo.

Join the private beta

A small group gets in by invite. Tell us what you want your agents to do, and we'll email you a link. The link creates your account, and you sign in with a passkey, not a password.