Skip to content

AI agents

How to give an AI agent a login without exposing it

Short answer

Never paste the password into the chat. If you are at the screen, sign in yourself or use the agent’s own secure sign-in. If someone else holds the login, or the agent has no secure sign-in, send it as a sealed link (an encrypted link that opens once) and type its separate access code yourself.

Whatever you choose, share the narrowest login you can and change the password after important tasks.

£0 · Free plan, no card needed · Sealed sharing on Free and Pro

An AI agent working on a screen

Compared

Five ways to give agents a login

Each way to give an AI agent a login, compared by what the agent sees, what stays in the chat history and how you take access back.
Where the password ends up with each method
MethodDoes the agent see the password?Left in the chat history?Can you take it back?Best for
Paste it into the chat Yes Yes, in plain text Only by changing the password Never
Sign in yourself, or use the agent’s secure sign-in Not when the agent offers a sign-in form or take-over that keeps it from the model No Sign out and change the password Your own accounts, when you are at the screen
A password manager fills it for the agent, such as 1Password for Claude No, according to the provider No Revoke access in the manager Your own logins, if you already use that manager and its supported setup
Scoped tokens or secret injection, such as Proton Pass access tokens or Bitwarden Agent Access The agent or the command it runs reads what it is given No Revoke the token Scripts and coding agents that need repeated access
Argoned sealed link Only if the agent is on the page where it is opened Only the link Yes, before it is opened (Session → Shared links); after that, change the password A login someone else holds, or a receiver who uses a different tool

Guides

Pick the guide for your agent

Step-by-step guides for browser agents, assistants, coding agents and automations, plus one for sending a login to a person.
Connected services passing tasks between them

Ground rules

Five rules and one honest limit

The rules keep any agent’s access small and short-lived. The limit is what a sealed link cannot protect once a browser agent opens the page.

Five rules for any agent

  1. Share the narrowest login you can

    Use a sub-account, a read-only role or a restricted API key.

  2. Set the shortest time that works

    A sealed link can last 1 hour, 24 hours, 48 hours or 7 days. Pick the shortest that lets the task finish.

  3. Keep the access code out of the chat

    Paste only the link. Type the code yourself, or send it by a different route.

  4. Change important passwords afterwards

    Once a credential has been used, only a new password takes the access back.

  5. Never hand over the master keys

    Do not give any agent your email, bank or password-manager master password.

What the agent sees when you use Argoned

Today the credential is opened on the Argoned page the agent is viewing, so a browser agent can read it at that moment. The agent, and the company that runs it, may keep what the agent saw.

It is never in plain text in your chat, your email or on our servers. When you can, open the sealed link yourself and sign in, so the agent never handles the password at all.

Still protected

  • While it travels: only encrypted data and a link leave your browser.
  • While it is stored: our server keeps the encrypted data, not the credential.
  • In the chat history: the chat holds only a link, never the password in plain text.
A sign-in form asking for a password

Where the credential can be read

  • Your chat with the agent

    The chat history holds the sealed link. The password is never in it in plain text.

    Only the link
  • Our servers, while it waits

    We store only the locked form. The access code stays with you.

    Encrypted
  • The Argoned page, once opened

    The credential is decrypted in that browser tab, so a browser agent viewing the page can read it at that moment.

    Whoever sees the page
  • The agent and the company behind it

    What the agent saw may be kept by the agent and by the company that runs it.

    May keep it

FAQ

Questions about AI agents and logins

Straight answers about pasting passwords, sealed links and what an agent can keep. More answers on the FAQ page.
Two people beside a large question mark
Can I give ChatGPT or Claude a password without pasting it?

Yes. Send the password as a sealed link from your Argoned vault. The chat holds only the link, and you type the access code yourself when the agent reaches the Argoned page.

If your agent offers its own secure sign-in, such as ChatGPT’s sign-in form or 1Password for Claude, that keeps the password away from the model and is a good choice when it is available to you.

Compare five ways to give an AI agent a login →

Does my AI agent see the password?

Yes, at the moment it is opened. Today a sealed credential is opened on the Argoned page your agent is viewing, so a browser agent can read it then.

The password is never in plain text in your chat, your email or on our servers, as long as you keep the access code out of the chat.

See what is protected, and what is not →

What does “sealed” mean?

Sealed means encrypted in your browser before it leaves your device. Only encrypted data travels and is stored, and it is opened only where the access code is typed in.

Does the agent need an Argoned account?

No. The agent or person you send it to opens the sealed link in any browser, without an account. Only the sender needs an Argoned vault.

Which agents does it work with?

Sealed links work with any agent that can open a web page and lets you type into it, such as a browser agent where you can take over for one step.

We have not published a tested list yet, so try it once with a low-risk login before you rely on it.

Find the guide for your kind of agent →

Can I use it with n8n, an MCP config or a script?

Not directly. Today a sealed link is opened in a web browser, so a tool such as n8n, an MCP config (the file that connects an AI app to its tools) or a script cannot open it for you.

Open the link yourself, then save the value in that tool’s own credential store or in an environment variable (a named setting a program reads when it runs). That way it never sits in a chat or an email.

Read the guide to API keys in MCP config files →

A person chatting with an AI assistant

Your agent needs a login. Send it sealed.

Seal a login or API key in your browser and send a link instead of the password.

£0 · Free plan, no card needed · Encrypted in your browser