Can Claude log in to websites? Three ways that work
I build Dejo, one of the three options below. I've tried to describe the other two from their own docs, with links, so you can check.
Yes, Claude can work on websites you're signed in to. But you should be the one who signs in, and the browser should keep the session so you only do it once. There are three common ways to set that up for Claude Code, and they differ mostly in whose browser Claude is using.
Why "just give it the password" is a bad idea
Anything you type in the chat becomes part of the conversation the model reads. A password pasted there is a password sitting in a transcript. Many sign-ins also ask for a one-time code or a tap on your phone, which an agent can't answer anyway.
So the pattern that works is: you sign in once, in a real browser window, and the tool keeps the session. Here's how each option does that.
Option 1: Claude in Chrome (your own browser)
Claude in Chrome is Anthropic's browser extension. Start Claude Code with claude --chrome, and Claude works in tabs of your everyday Chrome. From the docs: it "shares your browser's login state, so it can access any site you're already signed into," and "when Claude encounters a login page or CAPTCHA, it pauses and asks you to handle it manually."
That's the least setup of the three, since you're probably signed in to most things already. A few things to know from the same page: it needs a direct Anthropic plan (Pro, Max, Team or Enterprise), it works in Chrome and Edge, it runs in a visible window, and it's not supported in WSL. You control which sites it may use from the extension's settings.
Option 2: Playwright MCP (its own profile, kept on disk)
Playwright MCP runs its own browser. By default its profile persists between sessions: "login state, cookies, and local storage are preserved." You sign in once in its window, and later sessions start signed in.
It has two other modes worth knowing. --isolated starts every session fresh and writes nothing to disk, which suits tests. And its browser extension connects to your running Chrome or Edge, "reusing your logged-in sessions," which the docs suggest for SSO and two-factor sign-ins.
One limit to plan around: a profile can only be used by one browser at a time, so two sessions sharing a project folder will clash.
Option 3: Dejo (a sign-in window, then checked)
Dejo also keeps its own browser profile, in ~/.dejo. When a site wants a sign-in, your agent calls dejo_login and a real browser window opens on that site. You sign in however the site asks (password, Google, a code on your phone), tell the agent you're done, and it calls dejo_login_done.
The part I care about most: before closing the window, Dejo checks it. If the page still looks like a sign-in page, nothing is saved and the agent is told you haven't finished. A sign-in that didn't happen is never recorded as one.
For sites with a plain password form you want filled on every run, the password lives in an environment variable such as DEJO_SECRET_BILLING_ACME_COM_PASSWORD or in ~/.dejo/secrets.json. The saved route only records that a password goes there. The full setup is in the sign-in docs.
Side by side
| Claude in Chrome | Playwright MCP | Dejo | |
|---|---|---|---|
| whose browser | your everyday Chrome | its own (or yours, via the extension) | its own |
| you sign in | already signed in, or when it pauses | once, in its window | once, in a window it opens |
| checks the sign-in happened | it asks you | no | yes |
| several accounts on one site | one per browser profile | one profile per project folder | named profiles, side by side |
| runs without a visible window afterwards | no | yes | yes |
| remembers how to do the task | no | no | yes |
Which should you pick?
If you want Claude to help with whatever you're doing in your own browser right now, Claude in Chrome is the natural choice. It already has your sessions, and you watch it work.
If you want a task to run on its own, without your Chrome open and without touching your personal tabs, use a tool with its own profile. Playwright MCP is fine for one-off work. If it's a task you'll repeat, Dejo also remembers how to do it, so the next run is one call. I wrote about that in why your agent re-reads every website.
When a session expires
Sites end sessions on their own schedule, and none of these tools can stop that. With Claude in Chrome you'll see the login page yourself. With Playwright MCP the agent lands on a login page and has to notice. Dejo reports needs_login so the agent asks you to sign in again; the saved route carries on after that.
FAQ
Can Claude log in to websites?
Yes. Claude in Chrome uses the sign-ins you already have in your own Chrome. Browser tools like Playwright MCP and Dejo keep a browser profile, so you sign in once in their window and the session stays. In all three, you do the actual sign-in yourself.
Is it safe to give Claude my password?
Avoid typing passwords into the chat: whatever you type there is part of the conversation the model reads. Sign in yourself in the browser window instead. If an automation must fill a password form, keep the password in an environment variable or a local file that the tool reads at run time.
Does Claude Code remember my login between sessions?
Claude Code itself doesn't keep website logins. The browser tool does: Claude in Chrome uses your Chrome's own sessions, and Playwright MCP and Dejo keep a persistent browser profile, so you stay signed in across new chats.
Can Claude sign in with Google or SSO for me?
It shouldn't, and the good tools are built so it doesn't. Claude in Chrome pauses at a login page and asks you to handle it. Dejo opens a window for you to sign in and never automates a Google or SSO button.