# Logged-In Browser for AI Agents Source: https://metadock.app/logged-in-browser-for-ai Logged-in browsers for AI agents # Give your AI agent a browser that is already logged in. Log in once by hand, with your own password and 2FA. MetaDock keeps that session in the profile on your machine, so Claude, Cursor or the built-in assistant can work inside your dashboards, CRMs and webmail without being given your password. [Try Pro free](https://metadock.app/download) Color-coded MetaDock profiles, each keeping its own cookies, storage and logins 5 automation protocols on ProEverything runs on your machineOne-click workspace restore You log in, the agent works ## How do I let an AI agent use a site I am logged in to? Sign in by hand in a MetaDock profile, the same way you would in any browser. The agent then opens a browser in that profile over MCP and finds the session already there. Log in by handProfiles stored locallyStill logged in tomorrow ### Your password stays with you You type it yourself. MetaDock never passes it to the agent, and the password vault is not exposed over MCP or any other API. Keep the agent out of a profile while you type a password in it. ### Profiles stored on your machine Cookies, storage and logins are stored in the profile on your own disk, and MetaDock does not sync them to any MetaDock server. An agent you connect can read the pages, cookies and storage of the profiles it opens, and your AI app may send what it reads to its model provider, so open the agent only in the profiles it needs. ### One profile per account Keep work, personal and client accounts in separate profiles, each with its own cookies, storage, cache and extensions, and give the agent only the one it needs. ### Still logged in tomorrow Profiles and the workspace around them are saved, so the next run starts signed in for as long as the site keeps your session. ### You see every page it opens The agent works in a visible panel in your layout, so you know which account it is in and what it is doing. Why MetaDock ## How is this different from a fresh or cloud browser? Every way of logging an agent in has a catch. ### The problem Pasting a password into a prompt, or into a script the agent runs. A fresh automation browser that asks you to sign in again on every run. Cloud browsers, where your session lives on someone else's servers. Sessions that are gone by the next run, so tomorrow starts at the login page again. How is this different from a fresh or cloud browser? Feature MetaDock Fresh automation profile or cloud browser Who logs in You, by hand, in a visible browser A script, or cookies copied in Password given to the agent No When the login is scripted Where the session lives Stored in the profile on your machine; readable by the agent you connect A temporary profile, or the provider's servers After a restart Still logged in, for as long as the site keeps the session Depends on how the profile is stored Steam reviews ## What people are saying > “Brilliant software. Main use case for me is the ability to resize windows that can't usually be resized. I'm able to do almost as much on 2 monitors now as I could on 3.” [Pendegg](https://steamcommunity.com/profiles/76561198799621262/recommended/2520820/)Steam user 37 hrs > “Very interesting application, great for productivity. This has fast become a tool in my tool box.” [slimpickins4444](https://steamcommunity.com/profiles/76561199210957897/recommended/2520820/)Steam user 10 hrs All quotes are from pseudonymous Steam reviewers. [Verify on Steam](https://steamcommunity.com/app/2520820/reviews/). Reviews curated and re-checked against the live page as of 2026-10-17. FAQ ## Logins and AI agents Not from MetaDock. You type your password yourself, and the password vault is not exposed over MCP or any other API. The agent can read the pages it opens, like any browser automation, so open it only in the profiles it needs. Complete it by hand when you log in. The site decides how long the session lasts; while it lasts, the agent usually works inside it without another 2FA prompt. Each time MetaDock starts, a new AI app has to ask before it connects: Allow Once (one request), Allow for this session, or Deny. Other sessions of an app you allowed are not asked again until MetaDock restarts, and turning on Allow All Connections skips the prompt. Revoke any app in the API, Automation & AI settings. Most sites that work in Microsoft Edge, because each MetaDock browser runs on Microsoft's Edge WebView2 engine. A few sites restrict embedded browsers. Use it within each site's terms. You are. MetaDock gives the agent a browser and shows you what it does, but it does not check or block the agent's decisions, and an agent can act faster than you can step in. Use agents only in accounts and on sites whose terms allow automation, and see the EULA for the full terms. ## Trial and guarantees ### 14-day free trial, no signup Download it and start a 14-day free trial in the app. No account, no email, no card. Then keep Pro or carry on free. ### Cancel anytime Pro renews automatically until you cancel, and you can cancel from the billing portal at any time to stop every future charge. ### Local-first data Multi-monitor layouts, profiles, and browsing data stored locally. No cloud sync. ## Log in once. Let the agent do the rest. Free, with 14 days of MetaDock Pro to start. No account, no email, no card. Windows 10/11. [Try Pro free](https://metadock.app/download) - 14-day free trial - No account or email - No credit card ## You may also be interested in... Other jobs MetaDock does for you and your AI agents [### Run several agents at once Each Claude Code or Cursor session in its own browser profile. Learn more](https://metadock.app/parallel-ai-agents)[### Watch the agent and take over By default every browser it drives is visible. Click in whenever you choose. Learn more](https://metadock.app/human-in-the-loop)[### Set up MCP One-line setup for Claude Code, Claude Desktop, Cursor, VS Code and more. Learn more](https://metadock.app/mcp) Claude, Cursor, Microsoft Edge, WebView2 and Windows are trademarks of their respective owners. MetaDock is not affiliated with, sponsored by, or endorsed by any of them. Comparisons reflect publicly available information on the date given and may change. ## FAQ ### Does the agent see my passwords? Not from MetaDock. You type your password yourself, and the password vault is not exposed over MCP or any other API. The agent can read the pages it opens, like any browser automation, so open it only in the profiles it needs. ### What about two-factor authentication? Complete it by hand when you log in. The site decides how long the session lasts; while it lasts, the agent usually works inside it without another 2FA prompt. ### Can the agent use my accounts without asking me? Each time MetaDock starts, a new AI app has to ask before it connects: Allow Once (one request), Allow for this session, or Deny. Other sessions of an app you allowed are not asked again until MetaDock restarts, and turning on Allow All Connections skips the prompt. Revoke any app in the API, Automation & AI settings. ### Which sites does this work with? Most sites that work in Microsoft Edge, because each MetaDock browser runs on Microsoft's Edge WebView2 engine. A few sites restrict embedded browsers. Use it within each site's terms. ### Who is responsible for what the agent does? You are. MetaDock gives the agent a browser and shows you what it does, but it does not check or block the agent's decisions, and an agent can act faster than you can step in. Use agents only in accounts and on sites whose terms allow automation, and see the EULA for the full terms.