Sign-ins and Saved Keys

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 > Tools > 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 chatCopy Anchor Link

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 means later, not no (below).

The card waits until you answer it (10 minutes at most with Settings > Safety > Time out unanswered requests on). 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. When you saved a 2FA setup key for the site, Foxl makes the code from it and types it in without the card.

Not now waits. In your own chat, Not now keeps the card in the chat, waiting, for up to 12 hours: Foxl carries on with what does not need the sign-in, and Sign in now (Add the key now on a key card) opens the card again. Once you save the sign-in or key, Foxl picks the task back up in that chat and signs in. With check-ins on, the next one names the sign-in that waits. A card you leave unanswered waits for you too (with Time out unanswered requests on it ends after its 10 minutes), a verification code card does not wait, and in a schedule, a channel run or a subagent Not now is a no.

After you save:

• Added (site) to Integrations. When the sign-in or key you save adds the site to Integrations, a line under the card says so, and tapping it opens that entry (a card you save after choosing Not now does not show the line yet).
• Sign in to (site) again. When a site refuses a saved sign-in, the card that asks for it is titled that way, and until you enter it again Foxl asks for it instead of typing in the one the site refused.
• A chat shows one sign-in card per site at a time.
• On a site that asks for the username on one page and the password on the next, Foxl types each on its own page. It does not type a saved username into a page with no sign-in field, such as a search box.
• When Foxl types a saved sign-in or a verification code and the page stays put (for example, the site says the code was wrong), the screenshots Foxl's AI takes of that page show those fields empty until the page changes. What you see on the page is unchanged.

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, while the Web Access filter is on. A site on the Web Access blocked list (the filter is off until you turn it on), or one you told Foxl never to sign in to (below), is never signed in to and never asked for a password. With the filter off, such a site saves and uses a sign-in like any other. If the task needs that page, Foxl offers to hand you its browser so you sign in there yourself (see When a step is yours); with the Web Access filter on, its browser does not open the site, and Foxl tells you to sign in there yourself.
• Your own Chrome. The card signs in only in Foxl's own browser. While the Chrome extension is connected and you are at your computer, a site's sign-in page in your Chrome is yours to fill in: Foxl asks you to sign in in that tab. A site the extension could not work, a site Foxl already has your sign-in for, a message from your phone or app.foxl.ai, two minutes away from your Mac, or a watch waiting to sign in brings the card back (see Which one Foxl uses).
• 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.

Signing in with a saved sign-inCopy Anchor Link

Foxl signs in to a site with its saved sign-in without asking, and a line in the chat says so: Signed in to (site) with your saved sign-in. Don't use it again on that line removes the saved sign-in at once, with Undo to put it back, and the next task that needs the site asks for it with the card. Schedules and subagents use your saved sign-ins the same way, and so does a page watch: when a site signs it out, it signs in again by itself and says so in its chat (see Watches).

The first time, that line also asks once, in the chat and on your phone: Use your saved sign-ins without asking from now on?, with Just do it and Ask me first. Nothing waits for the answer: it sets the switches below, and the line does not ask again.

When the sign-in page is on another site, such as a single sign-on page, Foxl asks first, once for that site: Use your (name) sign-in on (site)?, in the chat and on your phone. It waits for your answer, and nothing is typed until you give it. Sign in signs in and remembers the site, so it is not asked again; Don't use it on (site) remembers that too, and Foxl does not type that sign-in there again. If you named that site yourself in your message, and Foxl has not read a web page, a mail or another tool's answer in that chat, it signs in there right away instead, and the line in the chat names the site: Signed in to (site) with your (name) sign-in, with Don't use it again. A schedule, a channel thread or a page watch always asks on another site.

If a site says a saved password is wrong, Foxl asks you for it again with the card and goes on from there.

With Ask me first, both switches in Settings > Safety > Saved sign-ins are on. Change either one there at any time:

• Ask before Foxl uses a saved sign-in. Foxl asks before it signs in with a saved sign-in, even with auto-approve on, unless you saved that sign-in in a card in the same chat in the last 30 minutes, and every verification code is asked for in a card. A page watch asks with its sign-in card, and goes on once you save it there. Choose Always allow for the site and it signs in there without asking; the site's entry under Added by Foxl in Settings > Tools > Integrations then says Signs in without asking, and Ask every time there takes it back.
• Ask before using a saved sign-in on another site. Foxl asks Use your (name) sign-in on (site)? before it signs in on another site, a site you named included, and remembers your answer for that site.

A phone can turn either one on; only the Foxl window on your computer can turn it off again.

Never sign in to a siteCopy Anchor Link

Say it in one of your own chats ("never sign in to coupang.com"), and Foxl adds the site to the Web Access blocked list at once, without asking. A line under the reply says Foxl will not sign in to coupang.com, and its Undo takes the site off the list again. From then on Foxl no longer asks for that site's sign-in, types one there or sends a saved key to it, and with the Web Access filter on its browser does not open the site at all. A sign-in you saved for the site before stays in Settings > Tools > Integrations until you remove it there, and Foxl's browser may still be signed in to the site from before: Remove on that entry deletes both.

Settings > Web Access lists these sites under Sites Foxl never signs in to. Remove one there and Foxl can ask for its sign-in again. A chat can only add a site; a schedule, a channel run or a subagent cannot.

A site's entry in IntegrationsCopy Anchor Link

A site Foxl added under Added by Foxl in Settings > Tools > Integrations shows its saved sign-in when you open it: the Account (partly hidden), what is Saved (the username, the password, a 2FA key), when Foxl Last used it, and its latest saves and uses under Activity. Add a 2FA key adds a setup key there. Other sites lists the other sites where that sign-in may or may not be used (your answer when asked, or a site you named for it), each with Forget, so Foxl asks about that site again next time. No value is shown.

Ask Foxl in a chat which sites have a saved sign-in, and it lists them with when each was last used.

The vaultCopy Anchor Link

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:

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-insCopy Anchor Link

Settings > Tools > 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:

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.