> 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.3.0.md). # Browser Extension Version 18.3.0 In Preview on November 6, 2026 ## Overview Browser Extension 18.3.0 introduces several new features, including granular control over when the autofill suggestions popup appears, with three settings to choose from (All Suggestions, Matches Only, and Show on Click). It also adds PAM record rotation status visibility, a resizable autofill prompt with built-in search and filtering and the ability to search for passkeys and folders directly within the extension. {% hint style="info" %} Currently in [preview](/release-notes/browser-extensions/browser-extension/preview-release.md). {% endhint %} ## New Features ### Passkey Search We have added the ability to easily search and filter through your passkeys. When you have four or more passkeys associated with a site, a search field will be displayed for passkey searches. The results will appear as you type based on full or partial matches.

### Folder Search When creating or editing a record, the folder selector now allows you to search through all folders within your vault. The results will appear as you type based on full or partial matches.

### Expand Autofill Suggestions When an autofill field has three or more matching records, you can now expand the suggestion popup by clicking the **expansion arrow**, then use search and filtering to find the entry you are looking for quickly.

### PAM Record Rotation Details You can now view PAM record rotation information, including the rotation schedule and current status, directly in the record detail view.

### Autofill Suggestions Settings You can now choose how Keeper autofill suggestions appear when you filling login fields. By default, Keeper will automatically suggest all matching records and the option to create a new login record (if no match exists). For example, if there's a record match on a site, a popup will appear with autofill suggestions. If you are at a site with no corresponding record match, you will receive a popup with an option to create a new vault record. Two new settings now give you more granular control over this behavior: * **Matches Only:** Autofill suggestions appear when matching records exist, however, you must click the Keeper icon to create a new login record. * **Show on Click:** You must click the Keeper icon to view autofill suggestions (even when matching records exist) and to create a new login record. You can access the Autofill Suggestions menu from **Settings > KeeperFill Tool**.

## Improvements ### Phishing Protection Response Options When Keeper’s AI-Powered Phishing Protection flags a suspicious site, you can now choose from several responses: * Ignore this Warning — Keeper won't warn you about the site again * Disable Keeper on This Site — Keeper is disabled on the site until changed in Settings * Report Incorrect Warning — Keeper will walk you through taking a screenshot of the site and providing details to Keeper about the issue (e.g. the site was incorrectly flagged as suspicious).

Suspicious Website Detection Response Options

* **BE-8107:** Address record Country combo box with filter for improved UX. * **BE-7849:** Improved default auto-generated name of new vault records. ## Bug Fixes * **BE-5399:** Fixed "Disable Hover Locks" enforcement * **BE-7319:** OneLogin prompt to save disappears after login * **BE-7785:** Autofill suggestion sort order not synced across devices, prioritizes unused records * **BE-7875:** Password generator history navigation with tab key stuck on eye icon on Firefox * **BE-8098:** Password Generator fails to reflect characters changes * **BE-8100:** Record dropdown failing in Change Password flow when multiple records exist for a site * **BE-8116:** Copy URL button in tooltip window copies record URL instead of record UID deep link * **BE-8131:** Classic Folder toolbar window record view shows parent shared folder instead of Nested Subfolder * **BE-8146:** Tab key does not move focus to Next button on extension login screen, keyboard navigation broken for accessibility users * **BE-8157:** Unable to keyboard navigate to the filter bar on the new autofill UI * **BE-8173:** Navigating back in settings causes a scroll to top of window * **BE-8189:** Context menu "Fill Expiration Date" does not fill split Month/Year select fields on credit card forms * **BE-8220:** Change Password flow resets if user misclicks the Keeper Lock when prompted to fill a new password * **BE-8226:** Keeper lock and fill tool appears on Gmail search bar * **BE-8279:** Autofill does not fill PayPal login page on first load * **BE-8316:** Extension blocks the YubiKey prompt when attempting to log in to the console --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.keeper.io/release-notes/browser-extensions/browser-extension/browser-extension-version-18.3.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.