> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/browser-extensions/browser-extension/browser-extension-version-18.2.0.md). # Browser Extension Version 18.2.0 In Preview on September 23, 2026 ## Overview Keeper Browser Extension version 18.2.0 introduces a **Hide Keeper** feature which allows you to pause Keeper for a specific site or domain, an opt-in approach to a redesigned autofill prompt and an AI-Powered Phishing Protection. This release also includes onboarding reminders for new Enterprise users and various bug fixes. {% hint style="info" %} Currently in [preview](/release-notes/browser-extensions/browser-extension/preview-release.md). {% endhint %} ## New Features ### **Hide Keeper** Sometimes you don't want the Keeper Browser Extension to autofill or show suggestions on a particular website — for example, when you're filling out a long form manually or browsing a site where autofill gets in the way. This feature allows you to effectively have a pause-for-a-visit / site-pause to temporarily silence the Keeper Browser Extension on any domain with a single click. **What it Does** * Hides all Keeper Browser Extension autofill popups, autofill suggestions, and KeeperLock icons on the paused site * Keeps the extension toolbar icon active so you can still open your vault or resume at any time * Works on sites already saved in your vault *and* sites you haven't saved yet {% hint style="info" %} Hiding Keeper on a site applies to the entire domain (e.g., all pages on [example.com](http://example.com/)), not just the current URL. Your hide/restore preferences are remembered locally in your browser until you change them. {% endhint %} **How it Works** Click the **Keeper lock icon** and from the overflow menu (three vertical dots), select **Hide Keeper on this site**.

Alternatively, right-click on any autofill field and select **Hide Keeper on this Site** from the Keeper context menu

**How to Restore Keeper** If you would like to resume Keeper's functionality on a site, click the **Restore** button at the top of the extension toolbar. Alternatively, within the extension **Settings** menu, select **Hidden Sites >** **Restore** next to the site's domain name. Keeper's autofill and suggestions functionally for that site will immediately return to normal. ### AI-Powered Phishing Protection (Opt-In) Keeper's AI-powered Phishing Protection uses a zero-knowledge local AI engine to protect you against potential phishing sites. If you encounter a suspicious site, you can block it. You retain full control of your blocked sites list and can restore access at any time. Keeper's Phishing Protection is entirely optional and disabled by default. **How to Enable & Manage Phishing Protection** Enable Phishing Protection from **Settings > Blocked Sites** and toggle "Phishing Protection" on. Here you can also view and add sites where Keeper autofill is disabled or restore previously blocked sites.

Manage Phishing Protection
(Add/Restore Domains)

**How it Works** When a suspicious website is detected, Keeper notifies you that the site may be trying to steal your credentials. You can view details about what Keeper detected, disable Keeper on that site, or dismiss the warning. If you dismiss it, Keeper won't alert you about that site again.

Detected patterns commonly associated with fake sites designed to steal your information: * Suspicious IP address * Login details hidden in URL * Look-alike characters in domain * Brand name on unofficial domain * Password requested by site * Unusual link structure

### **Autofill Prompt Redesign (Opt-In)** The Keeper Browser Extension has been updated to make autofilling credentials faster and more intuitive, with smarter suggestions appearing inline as you interact with forms and greater control over how your saved information is applied. Our new UI also includes a change in the detection model from 'page-level' to 'field-level'. To make the introduction gradual, we have provided an opt-in option, as we continue to refine field-level detection for even greater accuracy. By default, you'll still have the traditional UI and logic. To turn on the new UI and logic, go to **Settings > KeeperFill Tool** and toggle "Enable New Autofill Prompt" on.

#### What's New **Inline Autofill Recommendations**\ The Keeper Browser Extension now displays autofill suggestions directly beneath form fields as you interact with them — no more hunting through pop-ups or menus. When you click into or tab to a login, address, or payment field, Keeper shows matching credentials from your vault in a compact list positioned just below the field. Click any item to autofill the entire form instantly.

**Smart Search as You Type**\ Start typing in a field and the suggestions list narrows in real-time, filtering your vault entries to match what you're entering.

**Multiple Credential Visibility** \ If you have more than one login saved for a site, all matching entries appear in a scrollable list sorted by favorites first, then recently used, then alphabetical. Use the inline search to find the right one quickly. **Granular Control of Autofill**\ Click the expand arrow on any suggestion to see all fields in that record. From there you can: * Autofill only specific fields * Copy individual values (username, password, etc.) to your clipboard using the copy icon ### New User Setup Reminders Enterprise users now receive a prompt during sign-in to websites reminding them to activate Keeper and complete setup using their company email address.

## Improvements * **BE-8018:** Clipboard Settings — Add "Expire Immediately" option to reflect Admin Console Clipboard Expiration enforcement policy. This setting will effectively prevent your data from entering the clipboard at all (you can still use the autofill feature to manually or automatically autofill). ## Bug Fixes * **BE-7855:** Record disappears from autofill and extension after account switch * **BE-7852:** Incorrect matching credit cards/addresses after re-logins in new form filler * **BE-7799:** Incorrect Create New Record prompt * **BE-7794:** Multiple confirmation modals appear when filling payment card and address records via new form-fill prompt redesign * **BE-7733:** Shared folder is not removed from vault after owner deletion when no other folders exist * **BE-7711:** Address, payment card, and secure note records not displaying as expected in landscape mode * **BE-7660:** SSO Connect Duo 2FA method buttons gray out after selection * **BE-7576:** Select Folder Location resets after clicking away from toolbar window * **BE-7565:** "Report Issue" text for Snapshot Preview Page design issue * **BE-7344:** Password generator history navigation with tab key stuck on eye icon * **BE-7340:** Accessibility tab does not function as expected in default password manager flow * **BE-7264:** Recent sort fails to update after viewing record in toolbar window * **BE-7955**: Addressed security finding related to cross-origin navigation during checkout flows (payment and address records) while confirmation dialog is in a pending state * **BE-7956**: During HTTP Basic Auth autofill scenarios, only offer credentials that match the origin of the request (e.g. http\:// authorization only offered if the record URL uses http\:// as opposed to https\://) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.keeper.io/release-notes/browser-extensions/browser-extension/browser-extension-version-18.2.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.