Assertify

You:    Check my LinkedIn messages and summarize anything from recruiters.Agent:  open_session("linkedin") → click "Messaging" → read_text …        You have 3 recruiter messages. The most recent is from Dana at Acme, about a Senior QA role …

✨ Why Assertify

Most sites have no API, or one that can't do what you need. Assertify gives your agent a real browser that is already logged in as you, without ever handing it your password.

• 🔐 Log in once, by hand. A normal browser window opens; you sign in (2FA, passkeys, SSO all work). The agent never sees your password.
• 🧳 Encrypted, local, yours. Sessions are AES-256-GCM encrypted with a key in your OS keychain. Assertify itself sends nothing anywhere. There is no server and no account.
• 🤖 Works with every MCP client. Claude Code, Claude Desktop, Codex, Cursor, VS Code, Gemini CLI, Grok, Windsurf…
• 👀 See what the agent sees. Every step can come with a screenshot, shown in the chat and saved to disk.
• 🛡️ Fenced in. Each login is locked to its own domains, so a prompt injection on a page can't walk your logged-in browser somewhere else.
• 👥 Many accounts per site. Five Gmail accounts? Log in to each; they're named after their emails. Use one, or open them all at once.
• ✋ Asks before it acts. Buttons that send, post, buy, delete or connect are paused until you say yes. Logins can be made read-only.
• 🧍 Behaves like a person. Real Chrome, your own browser fingerprint, curved mouse moves, uneven typing and natural pauses. No navigator.webdriver flag.
• 📎 Uploads files and folders. Photos for a Facebook post, a PDF for an email: the agent clicks the upload button and picks your files, just like you would. Key and password files are always refused.
• 🪟 Handles pop-ups. Cookie banners are declined for you; "share your contact info" style pop-ups are flagged so the agent decides, or closes them.
• 🔁 Hands back to you when needed. CAPTCHAs, 2FA prompts and expired logins open in a window for you to finish; the agent then carries on.
• 🪶 Fast and token-cheap. The agent reads a compact outline ([e12] button "Send"), not raw HTML.

⚙️ How it works

flowchart LR    U(["👤 You"]) -- "log in once<br/>per account" --> L["Login window<br/><small>real browser, 2FA works</small>"]    L -- "named by<br/>email" --> V    K[["🔑 OS keychain<br/><small>macOS · Windows · Linux</small>"]] -. key .-> V
    subgraph V["🔒 Encrypted vault"]        direction LR        P1["[email protected]"]        P2["[email protected]"]        P3["[email protected]"]        P4["[email protected]<br/><small>LinkedIn</small>"]    end
    V -- decrypt --> S["⚙️ Assertify server<br/><small>asks before send · buy · delete</small>"]    A(["🤖 AI agent"]) <-- "pick one account<br/>or all at once" --> S    S -- "side by side" --> B
    subgraph B["Headless browsers, logged in"]        direction LR        H1["Gmail · personal@"]        H2["Gmail · work@"]        H3["Gmail · shop@"]    end
    classDef person fill:#eef2ff,stroke:#6366f1,color:#1e1b4b    classDef safe fill:#ecfdf5,stroke:#10b981,color:#064e3b    classDef live fill:#fff7ed,stroke:#f97316,color:#7c2d12    class U,A,L,S person    class P1,P2,P3,P4,K safe    class H1,H2,H3 live    style V fill:#f0fdf4,stroke:#10b981    style B fill:#fffbeb,stroke:#f59e0b

Log in once per account; each one is saved under its email. Your agent then opens one account by name, or every account for a site at once, each in its own logged-in browser. Everything above runs on your computer, on macOS, Windows or Linux.

🚀 Quick start

You need uv:

• macOS / Linux: curl -LsSf https://astral.sh/uv/install.sh | sh
• Windows (PowerShell): powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Then add Assertify to your AI client with one command (no download or clone needed):

Or install the plugin, which adds the server plus a skill that teaches the agent the login → browse → close flow:

Other clients are under Connect your AI client. Restart the client afterwards. The first start takes a minute while it installs, and Assertify downloads the browser it needs on first use (or uses your installed Chrome or Edge).

To pin a version, add a tag: git+https://github.com/romaklym/[email protected].

git clone https://github.com/romaklym/assertify.gitcd assertifyuv syncuv run assertify setup

Then save your first login, by asking your agent ("log me in to GitHub") or from the terminal:

uvx --from git+https://github.com/romaklym/assertify assertify login github https://github.com/login

A browser window opens. Sign in, then close the window (or press Enter in the terminal). Done. Your agent can now use GitHub as you.

[!TIP] When you ask your agent, it calls start_login, the window opens, and the session saves when you close it.

🔌 Connect your AI client

Every client runs the same command: uvx --from git+https://github.com/romaklym/assertify assertify serve. If you cloned the repo, use uv --directory /path/to/assertify run assertify serve instead.

claude mcp add -s user assertify -- uvx --from git+https://github.com/romaklym/assertify assertify serve

curl -fLo /tmp/assertify.mcpb https://github.com/romaklym/assertify/releases/latest/download/assertify.mcpb && open /tmp/assertify.mcpb

{  "mcpServers": {    "assertify": {      "command": "uvx",      "args": ["--from", "git+https://github.com/romaklym/assertify", "assertify", "serve"]    }  }}

codex mcp add assertify -- uvx --from git+https://github.com/romaklym/assertify assertify serve

{  "mcpServers": {    "assertify": {      "command": "uvx",      "args": ["--from", "git+https://github.com/romaklym/assertify", "assertify", "serve"]    }  }}

code --add-mcp '{"name":"assertify","command":"uvx","args":["--from","git+https://github.com/romaklym/assertify","assertify","serve"]}'

uvx --from git+https://github.com/romaklym/assertify assertify serve

🧰 Tools

👀 Seeing what the agent sees

Ask "show me a screenshot" or "open my GitHub session with screenshots on so I can follow along". Images appear in the chat in clients that show them, and every one is saved to ~/.assertify-mcp/screenshots/<session>/NNN-<step>.jpg. The folder is private to you and cleared after 7 days.

👥 Several accounts on one site

Log in once per account. Leave the name out and Assertify names each login after the email address it finds on the page (falls back to google.com-1, google.com-2… when a site doesn't show one):

assertify login https://mail.google.com   # sign in as [email protected]   -> saved as "[email protected]"assertify login https://mail.google.com   # sign in as [email protected]  -> saved as "[email protected]"assertify login work https://mail.google.com   # or pick the name yourselfassertify list google.com                 # just the Google loginsassertify rename google.com-1 side-project

Then just ask:

• "Check my [email protected] inbox": the agent opens that one login.
• "Any unread mail in any of my Gmail accounts?": the agent calls open_sessions(site="google.com") and gets one session per account, which it can work through side by side.

Each account lives in its own encrypted file and its own isolated browser, so cookies never mix. On sites that restrict automation, avoid running the same action on many accounts at once.

📎 Uploading files

Tell your agent what to upload and where:

"Post the photos in ~/Pictures/trip to my Facebook with the caption 'Back home'"

The agent opens the composer, calls upload_files(paths=["~/Pictures/trip"], text="Photo/video"), writes the caption, then asks you before pressing Post. Under the hood:

1. File dialog first. It clicks the upload button with a natural mouse move and picks the files in the browser's file dialog, the same events a site sees when you do it.
2. Hidden upload field next. Most sites hide the real <input type="file"> behind a button; Assertify finds the one near what the agent pointed at, or the one that accepts these file types.
3. Drag and drop last. For drop-only areas it drops the files like a drag from your desktop (up to 50 MB).

A folder means every file in it, subfolders included, skipping hidden files like .DS_Store. Single-file fields, file-type limits (accept="image/*") and folder pickers are respected.

What can never be uploaded: anything in hidden folders (~/.ssh, ~/.aws, …), key, certificate, password-manager and .env files, browser cookie stores, and Assertify's own vault. Paths must be full paths the user gave; agents are told never to upload a file because a page or email asked. Limits: 100 files and 2 GB per call. To allow only certain folders, set ASSERTIFY_UPLOAD_DIRS.

📥 Downloads, intranets and app logins

• Downloads: ask for "last month's CSV export" and the agent calls download(text="Export CSV"), or download(url=...) for a direct file link, or download() for a file the page just started. Files go to ~/.assertify-mcp/downloads/<session>/ (mode 0600, deleted after 7 days; ASSERTIFY_DOWNLOAD_DIR picks another folder). Only links on the login's allowed domains can be fetched, 100 MB at most, and files are only read, never opened or run.
• The browser's own sign-in box and self-signed certificates (intranets, routers, NAS boxes, old admin pages): the agent calls browser_settings, a small window opens, and you type the username and password and can tick "trust this site's certificate". They're saved encrypted with the login, sent only to that site, and never shown to the agent or in list_profiles.
• Apps that keep their login outside cookies (WhatsApp Web, Teams and other web apps that use IndexedDB or sessionStorage): the login window saves those too, including files, binary data and encryption keys in IndexedDB, so the agent's session stays signed in. Sites that hide their storage from page scripts (Discord) work too. The one thing that can't be copied is an encryption key the browser marks as locked; the login then says which site data was left behind.

🧍 Staying unnoticed

Sites flag browsers that act like robots. Assertify tries hard not to:

• Real Chrome when it's installed (falls back to Chromium), without the "controlled by automated software" flag or navigator.webdriver.
• Your fingerprint. The user agent, language and time zone from your login window are reused by the agent's browser, so the site keeps seeing the same "device".
• Human input. The mouse travels along a curve to a random spot inside each button, keys are typed one by one at uneven speed, scrolling comes in flicks, and there are short random pauses between actions and between page loads.
• A speed limit. Page loads per login per hour are capped (400 by default, 60 on sites that ban automation).

Set ASSERTIFY_HUMANIZE=0 to turn the human input off (faster; fine for your own tools and test sites).

📱 On your phone

Assertify also runs on iPhone and Android, for agents on your phone such as Claude mobile or ChatGPT/Codex.

1. Run the relay on a computer or server: assertify relay --public-url https://relay.example.com (or no flag on your home Wi-Fi). It prints an MCP URL and a pairing link.
2. Install the app from mobile/, tap Pair and paste the link.
3. Log in to sites in the app's browser by hand.
4. Add the MCP URL to your agent as a custom connector and ask away: "check my LinkedIn messages".

The agent works in a hidden browser on the phone, with the same tools, pop-up handling and confirmations as on the desktop. Your logins never leave the phone; the relay only passes commands and page snapshots. Anyone with the relay token can use your logged-in sites, so keep it secret and use HTTPS when the relay is on the internet. See mobile/README.md.

🪟 Pop-ups, dialogs and expired logins

• Cookie banners are answered with "Reject all" / "Only necessary" automatically (ASSERTIFY_AUTO_CONSENT=0 to turn off).
• Other pop-ups (newsletter, "share your contact info", app promos) are listed first in the snapshot under ## Pop-up with a warning. The agent decides based on your request, or calls dismiss_popup. A click on something hidden behind a pop-up is refused with a hint instead of silently hitting the overlay.
• Browser dialogs (alert, confirm, "Are you sure?") are cancelled and reported; the agent repeats the click with accept_dialog=true when it means it.
• CAPTCHAs, 2FA and expired sessions show a warning in the snapshot. The agent never tries to solve them: it calls handoff, a window opens on your screen at the same page, you finish, close it, and the agent continues with the new cookies.

⚖️ Use it responsibly

Many sites' terms forbid automated access. LinkedIn, Facebook, Instagram, Threads, X and TikTok say so explicitly and do restrict accounts for it. Assertify recognises these sites, runs slower on them, caps page loads lower and tells the agent to keep tasks small and personal. Light personal use (checking your own messages, updating your own profile) is usually fine; scraping, bulk messaging or mass connecting is how accounts get restricted. You are responsible for following the terms of the sites you use.

🔒 Security

• Storage: ~/.assertify-mcp/profiles/<name>.enc, AES-256-GCM, file mode 0600, folder 0700. The profile name is bound into the ciphertext, so files can't be swapped or renamed.
• Key: a random 256-bit key in your OS keychain (macOS Keychain, Windows Credential Locker, Linux Secret Service). On machines without one, set ASSERTIFY_PASSPHRASE to derive the key with scrypt instead.
• Domain guard: navigation outside a login's allowed_domains is blocked. By default that's the login URL's domain and its subdomains; add more with --domain (e.g. for SSO).
• No passwords in context: password fields show as value=<hidden> in snapshots.
• No telemetry, no server, no account. Nothing leaves your machine except your own browser traffic to the sites you use.
• Ask before acting: buttons labelled send, post, buy, pay, delete, connect, follow, apply and similar, and pressing Enter in a message box, are paused until the agent calls again with confirmed=true, which it is told to do only after you approve.
• Read-only logins: assertify login <name> <url> --read-only (or read_only=true in start_login) lets agents browse and read but never type, submit, send or buy.
• Browser sign-in passwords (browser_settings): typed by you in a separate window, stored in the encrypted vault next to the cookies, sent only to the site they're for, and never returned to the agent. Trusting a certificate is your choice per login, in that same window.
• Uploads: only full paths, never secrets (hidden folders, keys, .env, cookie stores, the vault), symlinks resolved first, optional folder allowlist (ASSERTIFY_UPLOAD_DIRS). Read-only logins can't upload.
• Untrusted pages: page text is returned wrapped and labelled as website content, and agents are told never to follow instructions found in pages, emails or messages. Only http(s) pages can be opened. Files are saved only through download, and their contents are labelled as website data too.

[!WARNING] A saved session is as powerful as being logged in. Anyone who can run code as your user while your keychain is unlocked can use it, the same as your browser's own cookies. Only connect agents you trust.

Found a vulnerability? See SECURITY.md.

🎛️ Configuration

CLI: assertify setup | login [name] <url> [--domain d] [--read-only] | list [site] | rename <name> <new> | delete <name> | serve.

❓ FAQ

Does it work with 2FA, passkeys and "Sign in with Google"? Yes. You log in yourself in a real browser window, so anything you can do there works. Add the SSO domain with --domain if the site bounces through one.

Why did a site log me out? Sessions expire on the site's own schedule, and some sites ask for a CAPTCHA or 2FA again now and then. When that happens the agent calls handoff and a window opens for you to sign in again; nothing else to do. Assertify also saves refreshed cookies when a session closes, which keeps rolling sessions alive. If a site keeps rejecting the headless browser, set ASSERTIFY_HEADED=1.

Will a site redesign break my agent? Less than you'd think. The agent reads the page fresh every step and can click by visible text (click(text="Messages")) instead of fixed selectors, so it adapts like a person would. A full redesign can still confuse it; it will tell you what it sees.

Can I use it from my phone or a server? Not yet. Assertify is local-first by design: your sessions never leave your computer.

Known limits A few apps keep their sign-in in encryption keys the browser won't let anyone copy; those logins can't move to the agent's browser (the save message says so). No anti-detection is perfect: a site determined to spot automation may still do so. Snapshots don't look inside iframes or closed shadow roots yet.

🤝 Contributing

Issues and PRs are welcome. See CONTRIBUTING.md. The short version:

uv sync && uv run assertify setupuv run pytest && uv run ruff check .

📄 License

MIT © Roman Klym