> 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/jp/browser/safari-extension/older/safari-extension.md).

# Safari Extension Version 14.13.0

## Bug Fixes

* **Fixed:** The "Open in Vault" action located in the the record detail view of the Safari extension, incorrectly directs users to the desktop app instead of the Web Vault.
* **Fixed:** Following an SSO login to the Web Vault, the users domain is not retained by the Safari extension, prompting the user to enter their Master password at the extension login screen.
* **Fixed:** User email addresses are not saving in the Safari extension when they log into Keeper through the Web Vault.
* **Fixed:** The Safari extension "Create an Account" button is unresponsive and fails to direct the user to the Keeper Desktop App.


---

# 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/jp/browser/safari-extension/older/safari-extension.md?ask=<question>&goal=<endgoal>
```

`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.
