Sign-ins and Saved Keys
How Foxl signs in to a website for you with a sign-in kept in a vault on your computer, and the one list of the keys, tokens and sign-ins you gave Foxl there
When a task needs you to sign in to a website, Foxl asks in the chat and keeps what you type in a vault on your computer. Settings > Connect > Integrations then lists the keys, tokens and sign-ins you gave Foxl on that computer, in one place, with where each one is kept.
Signing in to a website from a chat
When Foxl's own browser reaches a site's sign-in page during a task, Foxl does not ask for your password in a message. It shows a Sign in to (site) card in the chat instead:
- Email or username and Password, and, if you like, Add a 2FA setup key: the key the site showed when you turned on two-step sign-in, from which Foxl makes the codes.
- Save and continue saves them in the vault on your computer, and Foxl types them in for you on that site only, and only on its secure (https) sign-in page. Foxl's AI never sees what you type: the model is told only that a sign-in was saved, with a shortened username.
- I forgot my password tells Foxl to open the site's own reset page. I'll sign in myself hands you the page instead (see When a step is yours). Not now leaves it for later.
The card waits up to 10 minutes. When the site sends you a code to sign in, a (site) verification code card asks for it; the code is typed in only on that site and is not kept.
Before Foxl signs in to a site again with a saved sign-in, it asks, even with auto-approve on, unless you saved that sign-in in a card in the same chat in the last 30 minutes. Choose Always allow for the site and it signs in there without asking; the site's entry under Added by Foxl in Settings > Connect > Integrations then says Signs in without asking, and Ask every time there takes it back.
From your phone or app.foxl.ai the card appears too, and what you type in it is sent only in requests sealed with the key that device shares with your computer (the relay forwards them without it). When that connection is not ready, nothing is sent.
Where the card does not appear:
- Banks, payment services and government sites. A site on the Web Access blocked list is never signed in to; Foxl tells you to sign in yourself.
- Your own Chrome. The card signs in only in Foxl's own browser, not in your Chrome through the extension.
- With Save memories off (Settings > Memory), because the card registers the site under Added by Foxl, and on a tool profile without the web tools (Minimal or Default; Full is the default).
- On a Claude Pro/Max or Gemini CLI sign-in, or the on-device model, which do not carry Foxl's own sign-in tools.
The vault
Each sign-in is kept beside the site's entry in Foxl's folder on your computer
(~/.foxl/integrations/), every value encrypted on its own with a key that your operating
system holds:
| Computer | Where the vault's key is |
|---|---|
| macOS | Your login keychain, as Foxl Vault key |
| Windows | Windows' own data protection (DPAPI) for your user account |
| Linux | The Secret Service (GNOME Keyring or KWallet) |
On a Linux computer with no Secret Service, the key is kept in a file in Foxl's folder instead, and Foxl says so; it never moves the key to a file because the system store failed. While your Mac's login keychain is locked, the vault cannot be used until you unlock it.
What this protects: a copy of Foxl's folder (a backup, a synced folder, a lost disk) carries the sign-ins only in encrypted form, another user account on the computer cannot read them, and Foxl's relay, Foxl's servers and your model provider never receive the key or a readable value. What it does not: the card says that Foxl's tools that can run commands on this computer can also read the sign-ins saved here, and so can any other program running as you.
A sign-in leaves the vault when you remove it from the list below, or when you Remove the site's entry under Added by Foxl, which deletes the entry, its notes and its saved sign-in (see Sites and APIs Foxl remembers).
Saved keys and sign-ins
Settings > Connect > Integrations has a Saved keys and sign-ins section that lists the keys, tokens and sign-ins you gave Foxl on this computer: a website sign-in, a model API key, a transcription key, a connected account (Microsoft 365, Slack, Google), a skill secret, a channel's bot token and a custom tool's key. Each row says what it is for and where it is kept:
| Where it is kept | What is there |
|---|---|
| In the vault on this computer | Website sign-ins |
| Encrypted on this computer | Model and transcription keys, skill secrets, the Microsoft 365, Slack and Google sign-ins, and an MCP server's own sign-in |
| Saved on this computer, not encrypted | A channel's bot token, and a key kept in a custom tool's or an MCP server's settings |
No value is ever shown, and nothing in the list can show one.
- Remove deletes a key or sign-in where that is all it takes, after you confirm: anything that used it stops working. For Microsoft 365, Slack and Google it is that account's Disconnect. Slack and Google are also asked to revoke Foxl's access; Microsoft has no such request, so Foxl deletes its copy of the sign-in and its permission stays in your Microsoft account until you remove it there.
- Open, on a channel or a custom tool, takes you to its own page, because removing its token alone would stop it working. Change or remove it there.
On a phone or app.foxl.ai the list appears only when your device can reach your computer over its encrypted connection, and stays hidden otherwise, as it does with a version of Foxl on your computer that predates the list.
The key that encrypts the "Encrypted on this computer" rows is still kept in a file in Foxl's folder. Foxl also keeps a copy of it in your system's own secret store where there is one (on a Mac, Foxl key for saved API keys and sign-ins in Keychain Access), so that a later version can stop keeping it in a file. Nothing changes in how Foxl uses it. See Security.