An AI agent that remembers its own passwords
Tell an agent to sign up for a tool and, if it can do that at all, it chooses a password somewhere in the middle of the conversation — and the conversation is not a place to keep one. Close the tab and the password is gone with it, along with the only way back into the account it just created.
A clone with its own desktop has somewhere to put it instead: a credential store on its own machine, separate from anything it says in chat, that both the clone and you can read back later.
A store, not a sentence in a transcript
When a MyClawn clone signs up for something, it saves the account with a small tool on its own desktop — omni-secret — rather than leaving the password sitting in whatever it happened to type. The file lives outside its working directory, at permissions only it (and you, through the dashboard) can read, so a stray file listing or a careless grep -r over its project doesn't spray passwords into a transcript you're reading.
The next time the clone needs to log back in — tomorrow, next week, mid-task — it reads the password back from the store. That only works at all because the machine persists between sessions, the same requirement behind staying logged in in the first place.
| A chat assistant | A clone with a desktop | |
|---|---|---|
| Where a new password goes | A message in the conversation | A credential store on its own machine |
| Log back in next week | Ask it again, hope it's in context | It reads the store back itself |
| Can you see what it saved? | Only by scrolling the chat | Yes — the same list, in your dashboard |
| File permissions | N/A | 0600, outside the working directory |
Why the clone can read passwords back
This is a password manager the agent actually uses, not a vault only a human opens — and that is deliberate. An agent that signs up for a tool and then can never log back in has not really signed up for anything. The store exists so the clone can act again tomorrow the way it did today, the same reason a person keeps their own passwords somewhere they can get to.
Seeing what it saved
The same argument that put sent mail and calendar events in your dashboard applies here, harder: a password the clone holds and you cannot see would be a trap, since it's your account, not the clone's. Open the "Accounts your clone made" panel and it lists every site, username and password the clone has saved — hidden behind a click so it doesn't sit exposed on screen, with a copy button for when you need it. Nothing new; it's the same store the clone itself reads from, shown to the account owner.
What's not enabled yet
Stated plainly: the dashboard panel shows the accounts and passwords the clone saved — it does not show or generate two-factor codes. The clone can hold a 2FA seed and produce the current 6-digit code for its own use when it needs to get past a second prompt, but that code isn't surfaced to you anywhere today. If a site's second factor needs to land in your hands instead, that's a moment to take over the screen yourself, not something the dashboard hands you.
What it's good for
- An account the clone created for a tool it needed, that you can still get into after it moves on to something else
- A single place to see every login a clone has created in your name, instead of piecing it together from chat history
- Not re-entering a password every session, the same reason your own browser remembers one
How to try it
Signing up is free and takes about thirty seconds — no install, no card. A clone with its own machine and password store starts at $19/month; the tier table is on the homepage.
Related
- An AI agent that can log into websites
- How to give an AI agent its own email address
- An AI agent with persistent memory
Questions people ask
Can I see the passwords my clone has saved?
Yes. Open the "Accounts your clone made" panel in your dashboard — it lists every site, username and password it has saved, hidden behind a click, with a copy button.
Does the dashboard show two-factor codes too?
No. The clone can hold a 2FA seed and generate the current code for its own use, but that code isn’t surfaced in the dashboard today — if you need it, take over the screen at that moment.
Where are the passwords actually stored?
In a file on the clone’s own desktop, outside its working directory, readable only by it and by you through the dashboard — not in the chat conversation.